Re: Secure way to pack sounds in python?
@7, yes, you would need to store it somewhere, but the golden rule is never hard-code cryptographic data in your program. As for IVs, no, you would not need to make them constant. IVs are supposed to be public; typically what I do is prepend the IV/Nonce to the start of my encrypted data since its easy to find there and then append it directly onto the IV. Then I read the IV in and then store that somewhere in memory. I'd highly recommend AWS KMS for your key storage if possible -- they have a really good guide on securing your data. If using them, your way is:
1) Write nonce to secured data file
2) Write encrypted key to data file immediately after IV
3) Write encrypted ciphertext
The process is the same for reading it back. Of course, you'll need to learn the AWS APIs, but they're very good for storing key material. There are others, of course, like HashiCorp Vault which can encrypt files and prevent you from even storing anything else but an appID and secret in your program/external network that can only encrypt and decrypt. Then you cythonize your crypto code and your good.
In the end someone will always break your security. The goal of crypto is not to prevent someone from breaking your crypto -- because that's not possible. The goal is to ensure that its as hard as possible, or so hard that its impractical with any kind of hardware known.
-- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
