Skip to content
Home » Blog » Advice for Designing Cryptographic Software That is Misuse-Resistant

Advice for Designing Cryptographic Software That is Misuse-Resistant

One of the complaints that I have heard on this subreddit is that it is hard to design and implement cryptographic software that is misuse resistant–and I am not sure if that is harder than implementing cryptographic software that is secure.

When I asked similiar questions people admitted I can study libraries such as LibSodium as an easy-to-use crypto library.

What are the techniques to design such misuse-resistant crypto software–broken down into holistic steps?

I thank all in advance for all responses.

submitted by /u/fosres
[link] [comments]