Re: Why are secure web pages are so !@#$%^&*()_ slow

Ben Laurie (ben@algroup.co.uk)
Thu, 14 Jan 1999 12:11:22 +0000

• Next message: Bruce Schneier: "Cypherpunk Porn movie"
• Previous message: Bruce Schneier: "Re: On the Construction of Pseudo-OTP"
• In reply to: Mok-Kong Shen: "Re: On the Construction of Pseudo-OTP"
• Next in thread: Bill Frantz: "Re: Why are secure web pages are so !@#$%^&*()_ slow"
• Reply: Bill Frantz: "Re: Why are secure web pages are so !@#$%^&*()_ slow"

James A. Donald wrote:
> It appears to me that you could cut this crap if whenever you
> registered with someone, whenever you subscribed to someone,
> your browser remembered their DH key, and their server
> remembered your DH key in the manner described by Schneier,
> chap 22, "Key exchange without exchanging keys.", thus
> eliminating all public key operations and all the preliminary
> operations needed to open a channel.

SSL uses "session IDs" for this purpose. However, the server does
actually have to implement them, and not time them out too quickly. They
make HTTPS pages nearly as quick as HTTP (after the first one).

Cheers,

Ben.

--
http://www.apache-ssl.org/ben.html
"My grandfather once told me that there are two kinds of people: those
who work and those who take the credit. He told me to try to be in the
first group; there was less competition there."
     - Indira Gandhi

• Next message: Bruce Schneier: "Cypherpunk Porn movie"
• Previous message: Bruce Schneier: "Re: On the Construction of Pseudo-OTP"
• In reply to: Mok-Kong Shen: "Re: On the Construction of Pseudo-OTP"
• Next in thread: Bill Frantz: "Re: Why are secure web pages are so !@#$%^&*()_ slow"
• Reply: Bill Frantz: "Re: Why are secure web pages are so !@#$%^&*()_ slow"