mirror of
https://codeberg.org/fediverse/fep.git
synced 2026-08-08 13:35:51 +00:00
FEP-521a: Add "Security considerations" section (#731)
The proposal was finalized, but this is a non-breaking change. New requirements are not introduced. Resolves https://codeberg.org/fediverse/fep/issues/710 Reviewed-on: https://codeberg.org/fediverse/fep/pulls/731 Co-authored-by: silverpill <silverpill@firemail.cc> Co-committed-by: silverpill <silverpill@firemail.cc>
This commit is contained in:
@@ -80,6 +80,15 @@ An actor MAY have no associated public keys.
|
||||
}
|
||||
```
|
||||
|
||||
## Security considerations
|
||||
|
||||
Each actor is expected to have a different secret key.
|
||||
|
||||
To prevent [side-channel attacks](https://en.wikipedia.org/wiki/Side-channel_attack), secret keys need to be stored in binary form. If stored as text, they need to be decoded using a constant-time algorithm.
|
||||
|
||||
> [!WARNING]
|
||||
> [Controlled Identifiers][Multikey] specification requires implementers to use the `base-58-btc` alphabet for multibase-encoded secret keys. This practice is discouraged because available implementations of Base58 decode algorithm [may not be constant-time](https://github.com/w3c/cid/issues/162).
|
||||
|
||||
## Test vectors
|
||||
|
||||
See [fep-521a.feature](./fep-521a.feature)
|
||||
|
||||
Reference in New Issue
Block a user