Skip to content

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.

Sign up for GitHub

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

20 Open 17 Closed
20 Open 17 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt click/return to exclude labels
or ⇧ click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Persisting cipher object
#53 opened Sep 7, 2022 by hermanchitra
Using 'unset-eval' in Content Security Policy throws the error
#52 opened Aug 31, 2022 by oleh-starodubets
@donskov
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
Create dist folder release
#24 opened Mar 4, 2017 by rmhrisk
createPreKeyBundle helper is needed enhancement
#23 opened Feb 8, 2017 by microshine
Update readme with example of specifying the dependencies documentation
#22 opened Feb 6, 2017 by rmhrisk
Add total size, including dependencies to readme documentation
#21 opened Feb 6, 2017 by rmhrisk
Consider making secp256r1/secp521r1 and sha256/sha512 configurable enhancement question
#19 opened Feb 5, 2017 by rmhrisk
Simplify calling semantics enhancement help wanted
#17 opened Feb 4, 2017 by rmhrisk
Need to implement a trust store enhancement
#12 opened Feb 4, 2017 by rmhrisk
Need to implement a session store enhancement security
#11 opened Feb 4, 2017 by rmhrisk
Review design of AsymRatchet::encrypt best practices
#8 opened Feb 4, 2017 by rmhrisk
Validate the exchange key is a unique key and in appropriate group enhancement security
#7 opened Feb 4, 2017 by rmhrisk
1
Review exchange key usage and ensure no risk, or design mitigation for key replay. security
#6 opened Feb 4, 2017 by rmhrisk
Add basic gh-pages demo page documentation release
#5 opened Feb 4, 2017 by rmhrisk
Add coveralls reporting best practices release
#3 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! Type g p on any issue or pull request to go back to the pull request listing page.