On Mon, Jan 14, 2002 at 01:55:53PM -0800, Eric Rescorla wrote:
> Adam Wosotowsky <[EMAIL PROTECTED]> writes:
> > If the clocks are within say 30 minutes of each other the SSL handshake
> > will go through without a hitch and communications will flow smoothly.
> > However, if the clock is set quite
Adam Wosotowsky <[EMAIL PROTECTED]> writes:
> On Mon, Jan 14, 2002 at 09:26:22AM -0800, Eric Rescorla wrote:
>
> > SSL does not require that the client and server have synchronized
> > clocks, except in the loose sense that a certificate verifier's
> > clock should have some relation to the real
On Mon, Jan 14, 2002 at 09:26:22AM -0800, Eric Rescorla wrote:
> SSL does not require that the client and server have synchronized
> clocks, except in the loose sense that a certificate verifier's
> clock should have some relation to the real time in order to avoid
> falsely evaluating expiry.
>
Adam Wosotowsky <[EMAIL PROTECTED]> writes:
> I've thrown this out to the list before but recieved no responses,
> so I'm going to do it again.
>
> SSL encryption seems to fail if there is too much skew between the
> clocks. I've read "5 minutes", but I think that it is longer than that
> (there
hello,
I've thrown this out to the list before but recieved no responses,
so I'm going to do it again.
SSL encryption seems to fail if there is too much skew between the
clocks. I've read "5 minutes", but I think that it is longer than that
(there _is_ a 5 minute timeout, but I do not think th
