nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-22 16:35:52 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

Add clarification about not replacing nip 04

Browse Source
This commit is contained in:
Jon Staab 2023-12-20 11:35:12 -08:00
parent 732b0ce0a4
commit 2b78cc9304
1 changed files with 5 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
44.md
View File

@ -10,6 +10,10 @@ The NIP introduces a new data format for keypair-based encryption. This NIP is v
to allow multiple algorithm choices to exist simultaneously. This format may be used for to allow multiple algorithm choices to exist simultaneously. This format may be used for
many things, but MUST be used in the context of a signed event as described in NIP 01. many things, but MUST be used in the context of a signed event as described in NIP 01.
*Note*: this format DOES NOT define any `kind`s related to a new direct messaging standard,
only the encryption required to define one. It SHOULD NOT be used as a drop-in replacement
for NIP 04 payloads.
## Versions ## Versions
Currently defined encryption algorithms: Currently defined encryption algorithms:
@ -30,7 +34,7 @@ event. When applying this NIP to any use case, it's important to keep in mind yo
model and this NIP's limitations. For high-risk situations, users should chat in specialized E2EE model and this NIP's limitations. For high-risk situations, users should chat in specialized E2EE
messaging software and limit use of nostr to exchanging contacts. messaging software and limit use of nostr to exchanging contacts.
On its own, messages sent using this scheme has a number of important shortcomings: On its own, messages sent using this scheme have a number of important shortcomings:
- No deniability: it is possible to prove an event was signed by a particular key - No deniability: it is possible to prove an event was signed by a particular key
- No forward secrecy: when a key is compromised, it is possible to decrypt all previous conversations - No forward secrecy: when a key is compromised, it is possible to decrypt all previous conversations