3 ms·
Hm. I don't buy the "implementation matters" argument. If AES-128-GCM is broken in a library or language that'd be a pretty big deal. Cipher implementations sho
by binwiederhier 7y ago
Hm. I don't buy the "implementation matters" argument. If AES-128-GCM is broken in a library or language that'd be a pretty big deal. Cipher implementations should be interoperable, otherwise you'd have a big problem.
Your other argument is totally valid. If a cipher becomes exploitable, you'd treat it the same way as you would with password hashes. You'd need to re-encrypt. password_hash() is designed to hash with today's best hash.
My question was mainly about the file format though. The encrypt/decrypt functions would be a simple perk that becomes possible if we had that.
Edit: encrypt->hash
- verdverm 7y agoBy broken, I don't mean incorrect, just poorly implemented and there for exploitable. This is true of libraries in the wild. File format is typically binary or blob. It's encrypted so you can't see or understand it's structure, only assume.