News for hackers. Stuff that matters.
Re:Overclocking SSL by illumin8 on Saturday October 30, 2010 @09:45PM (#1852255)
The problem is that even if you cache sessions, you still have to do the math to encrypt every packet. Encryption cost is a cube of key size. Please, contradict me. If you can, many cryptographers and mathematicians will thank you... :-)

Say what you will, but the difficulty of brute-forcing decryption is based on key length. You might be able to optimize the encryption using a certain length, but the key will still be vulnerable if it is only 1024 bit (as the article suggests).

Re:Overclocking SSL by lmz on Saturday October 30, 2010 @10:15PM (#1852298)
For SSL, aren't the individual packets encrypted with a symmetric cypher e.g. AES, RC4, 3DES, etc?
Re:Overclocking SSL by caf on Sunday October 31, 2010 @01:00AM (#1852523)
Yes, the data stream is encrypted using a symmetric cipher, as the linked article says. The overhead of this is trivial.

It's the key exchange at the start of a session that requires the server to perform expensive RSA operations, which is why session caching helps.