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
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Nheko Reborn
Olm
Commits
884ad024
Commit
884ad024
authored
8 years ago
by
Mark Haines
Browse files
Options
Downloads
Patches
Plain Diff
Spelling
parent
092bf880
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
docs/megolm.rst
+2
-2
2 additions, 2 deletions
docs/megolm.rst
with
2 additions
and
2 deletions
docs/megolm.rst
+
2
−
2
View file @
884ad024
...
...
@@ -281,8 +281,8 @@ A message can be decrypted successfully multiple times. This means that an
attacker can re-send a copy of an old message, and the recipient will treat it
as a new message.
To mitigate this it is recomende
n
d that applications track the ratchet indic
i
es
they have rec
i
eved and that they reject messages with a ratchet index that
To mitigate this it is recom
m
ended that applications track the ratchet indices
they have rece
i
ved and that they reject messages with a ratchet index that
they have already decrypted.
Lack of Transcript Consistency
...
...
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
register
or
sign in
to comment