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

Example(s) for "You should instead have a plan for handling when (not if) your cryptographic algorithms and protocols are broken."? #140

Open
TobiasWehrum opened this issue Aug 26, 2023 · 0 comments

Comments

@TobiasWehrum
Copy link

In "Applying Cryptography" -> "Humility Is Important in Cryptography", you write that:

You should instead have a plan for handling when (not if) your cryptographic algorithms and protocols are broken. Make sure all your co-developers learn of this plan so that they will not ruin it (e.g., if you run an OSS project, put this in the CONTRIBUTING.md or equivalent file).

Do you know of any projects that have a public file that can serve as an example for such a plan? The course mentions several times that you should "make sure you are prepared to replace" cryptographics algorithms and protocols, but it doesn't mention anywhere what potential strategies or problems could be, so a practical example might help here.

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

1 participant