Re:How HTTPS Stops Attackers: What Every Web Dev Should Know
by oakenshield on Thursday July 25, 2013 @04:42AM
(#6101488)
Speed is one concern but far from the main reason. You couldn't use a typical-length RSA key to encrypt a large chunk of data because there's a max input size for any given RSA key size. Standard block/stream cipher modes of operation are defined only for symmetric key ciphers.
[ Parent
| on HN ]
Re:How HTTPS Stops Attackers: What Every Web Dev Should Know
by dspillett on Thursday July 25, 2013 @05:34AM
(#6101619)
You can certainly use RSA as a block cypher, you are just limited in the size of the blocks.
Re:How HTTPS Stops Attackers: What Every Web Dev Should Know
by YZF on Thursday July 25, 2013 @01:23PM
(#6103586)
The max input size is for one message. It's effectively the "block size" for RSA. You can send multiple messages using a single RSA key (and in fact pretty much everyone does that, otherwise you'd need a new public key for every message). RSA is a complete crypto system, you don't need any additional ciphers. You do need randomiziation (e.g. random padding).
Re:How HTTPS Stops Attackers: What Every Web Dev Should Know
by YZF on Saturday July 27, 2013 @01:50AM
(#6112009)
For the sake of completeness, one such construction where RSA is used as a cipher is OAEP (Optimal Asymmetric Encryption Padding). Beyond being slow it has some other inefficiencies but that's another story.