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

Check compliance with crypto suite B #11

Open
fpoirotte opened this issue Nov 23, 2014 · 2 comments
Open

Check compliance with crypto suite B #11

fpoirotte opened this issue Nov 23, 2014 · 2 comments
Labels

Comments

@fpoirotte
Copy link
Owner

See http://www.rfc-editor.org/rfc/rfc6239.txt. The goal of this ticket is to determine whether Pssht could theoritically be compatible with crypto suite B.

I say theoretically since Pssht has never (and probably never will) be audited for full compliance.
Also, as a reminder, Pssht has not been made to be secure and probably cannot be made secure anyway, so if you're thinking of using it to handle confidential data, think again!

@fpoirotte fpoirotte changed the title Check compliance with suite B crypto suite Check compliance with crypto suite B Dec 1, 2014
@fpoirotte
Copy link
Owner Author

Depends on #27. Suite B compliance also requires that options be added in Pssht to restrict the lists of usable algorithms (for encryption/MAC/host keys/public keys/etc.).

@fpoirotte
Copy link
Owner Author

See https://tools.ietf.org/html/rfc6239 for some of the implications.
See also #27 & #34 for tickets that must first be resolved before we can tackle this issue.

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

No branches or pull requests

1 participant