Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
O
Olm
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Nheko Reborn
Olm
Commits
27f5c25f
Commit
27f5c25f
authored
Jun 18, 2019
by
Matthew Hodgson
Browse files
Options
Downloads
Patches
Plain Diff
incorporate review from vdh & luca
parent
f8abaf9e
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/megolm.md
+17
-16
17 additions, 16 deletions
docs/megolm.md
with
17 additions
and
16 deletions
docs/megolm.md
+
17
−
16
View file @
27f5c25f
...
...
@@ -271,12 +271,13 @@ future research.
(also called 'future secrecy' or 'post-compromise security') is the property
that if current private keys are compromised, an attacker cannot decrypt
future messages in a given session. In other words, when looking
**backwards**
in
to the past
at a compromise
, messages sent since the compromise
will be
secret.
**backwards**
in
time
at a compromise
which has already happened,
**current**
messages are still
secret.
By itself, Megolm does not posess this property: once the key to a Megolm
session is compromised, the attacker can decrypt any future messages sent via
that session.
By itself, Megolm does not possess this property: once the key to a Megolm
session is compromised, the attacker can decrypt any message that was
encrypted using a key derived from the compromised key or any following
ratchet values.
In order to mitigate this, the application should ensure that Megolm sessions
are not used indefinitely. Instead it should periodically start a new session,
...
...
@@ -288,17 +289,17 @@ with new keys shared over a secure channel.
### Partial Forward Secrecy
[
Forward secrecy
](
https://intensecrypto.org/public/lec_08_hash_functions_part2.html#sec-forward-and-backward-secrecy
)
is the property that if the current private keys are compromised, an attacker
cannot decrypt
*past*
messages in a given session (unless past private keys
a
re retained). 'Perfect forward secrecy' means that no past keys are retained.
'Par
tial f
orward secrecy' means that some past key data may be retained. In
other words, when looking
**forwards**
into the future at a potential
compromise, messages sent prior to the compromise will be secret.
I
n
Megolm, each recipient maintains a record of the ratchet value which allows them to
decrypt
any
messages
sent in the session after the corresponding point in
the
co
nversation. If this value is compromised, an attacker can similarly decrypt
those past messages
.
(also called 'perfect forward secrecy') is the property that if the current
private keys are compromised, an attacker cannot decrypt
*past*
messages in
a
given session. In other words, when looking
**forwards**
in time towards a
poten
tial f
uture compromise,
**current**
messages will be secret.
In Megolm, each recipient maintains a record of the ratchet value which allows
them to decrypt any messages sent in the session after the corresponding point
i
n
the conversation. If this value is compromised, an attacker can similarly
decrypt
past
messages
which were encrypted by a key derived from
the
co
mpromised key or any following ratchet values. This gives 'partial'
forrward secrecy
.
To mitigate this issue, the application should offer the user the option to
discard historical conversations, by winding forward any stored ratchet values,
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
sign in
to comment