Embed Notice

@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.