upleb.uk

Public git repos — served from a NIP-34 GRASP relay at git.upleb.uk

summaryrefslogtreecommitdiff
path: root/EE.md
diff options
context:
space:
mode:
Diffstat (limited to 'EE.md')
-rw-r--r--EE.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/EE.md b/EE.md
index 6b24e0d..090fa29 100644
--- a/EE.md
+++ b/EE.md
@@ -82,7 +82,7 @@ This is a concise overview of the security trade-offs and considerations of this
82 82
83### Forward Secrecy and Post-compromise Security 83### Forward Secrecy and Post-compromise Security
84 84
85- As per the MLS spec, keys are deleted as soon as they are used to encrypt or decrypt a message. This is usually handled by the MLS implementation library itself but attention needs to be paid by clients to ensure they're not storing secrets (expecially the [exporter secret](#group-events)) for longer than absolutely necessary. 85- As per the MLS spec, keys are deleted as soon as they are used to encrypt or decrypt a message. This is usually handled by the MLS implementation library itself but attention needs to be paid by clients to ensure they're not storing secrets (especially the [exporter secret](#group-events)) for longer than absolutely necessary.
86- This NIP maintains MLS forward secrecy and post-compromise security guarantees. You can read more about those in the MLS Architectural Overview section on [Forward Secrecy and Post-compromise Security](https://www.ietf.org/archive/id/draft-ietf-mls-architecture-15.html#name-forward-and-post-compromise). 86- This NIP maintains MLS forward secrecy and post-compromise security guarantees. You can read more about those in the MLS Architectural Overview section on [Forward Secrecy and Post-compromise Security](https://www.ietf.org/archive/id/draft-ietf-mls-architecture-15.html#name-forward-and-post-compromise).
87 87
88### Leakage of various keys 88### Leakage of various keys