Skip to content
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

Security audit #42

Open
breznak opened this issue Feb 28, 2017 · 2 comments
Open

Security audit #42

breznak opened this issue Feb 28, 2017 · 2 comments

Comments

@breznak
Copy link

breznak commented Feb 28, 2017

For such sensitive app, it would be almost crucial to perform a security audit (once a semi-stable version is reached)

@dumblob
Copy link

dumblob commented Feb 28, 2017

As a good start, auditors shall refer to the "crypto heart" of this application and its threat model (look for the string mitiga to find out how they mitigate described attack vectors; some vectors might be though missing... thus the security audit).

@sirdarckcat
Copy link

The library received a few internal security reviews. The threat model posted above is a summary of the design level findings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants