-
Notifications
You must be signed in to change notification settings - Fork 13
Issues: PeculiarVentures/2key-ratchet
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Using 'unset-eval' in Content Security Policy throws the error
#52
opened Aug 31, 2022 by
oleh-starodubets
Implement verification of public keys meet are welformed before relying on them
security
#28
opened Apr 11, 2017 by
rmhrisk
Think about how we can randomize PreKey selection when initiating a session.
security
#27
opened Mar 5, 2017 by
rmhrisk
Think about how we ensure pre-keys are regenerated and re-resigned regularly
security
#26
opened Mar 5, 2017 by
rmhrisk
Update readme with example of specifying the dependencies
documentation
#22
opened Feb 6, 2017 by
rmhrisk
Consider making secp256r1/secp521r1 and sha256/sha512 configurable
enhancement
question
#19
opened Feb 5, 2017 by
rmhrisk
Validate the exchange key is a unique key and in appropriate group
enhancement
security
#7
opened Feb 4, 2017 by
rmhrisk
Review exchange key usage and ensure no risk, or design mitigation for key replay.
security
#6
opened Feb 4, 2017 by
rmhrisk
Do additional validation of ratchet data prior to use
best practices
security
#2
opened Feb 4, 2017 by
rmhrisk
Review use of 25519 specific constants given our use of secp256r1
security
#1
opened Feb 4, 2017 by
rmhrisk
ProTip!
Follow long discussions with comments:>50.