![]() ![]() ![]() I am indifferent to the RSA OAEP implementation that will be used for decryption (Go, Java, Python, openssl. Implementations change, new libraries, functions & new versions of programming language runtimes are used, etc. Since different ciphertexts are generated for the same plaintext, is there a guarantee that I will be able to decrypt these RSA OAEP ciphertexts in the future ?.Sending data over the network and I should not treat them the same,īut for my personal use case I want to use them for P.S: I understand that RSA and AES have different use cases when it comes to ![]() I am more confident with using AES because if you supply the same symmetric key and the same initialization vector you will always get the same ciphertext. I read some similar questions on stack overflow that say that RSA OAEP adds padding to ensure that a different ciphertext is generated for the same plaintext for security purposes. I generated a public/private key pair with 4096 bits. Rsa.DecryptOAEP(sha256.New(), rng, rsaPrivatekey, ciphertext, nil) I am using RSA OAEP in Go (Golang): rsa.EncryptOAEP(sha256.New(), rng, rsaPublickey, plaintext, nil) My goal is to encrypt some strings and store them in a database. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |