Conversation

Notices

1. Embed this notice
   silverpill (silverpill@mitra.social)'s status on Thursday, 20-Feb-2025 02:57:24 JST silverpill

   @b0y Mitra backend seems to support pre-hashed signatures, but the frontend asks for legacy ones. I probably wanted to wait until instances upgrade before using pre-hashed by default, but then forgot about it :)
   Will fix this in the next release

   • Embed this notice
     silverpill (silverpill@mitra.social)'s status on Friday, 21-Feb-2025 04:25:30 JST silverpill

     in reply to

     @b0y The situation is more complicated than I thought. We use legacy signatures because they are compatible with cryptographic standards used in fediverse. Without the -l flag, minisign computes Blake2b-512 digest first, and the signs it. Fediverse applications use SHA-256, so the only way to make them interoperate with minisign is to use legacy format where signature is generated without hashing.

     A new type of identity proof can be added, but I am not sure about minisign because it is not user friendly. Ideally, it should be something with a GUI.