Comment #18 on issue 6893 by bugdro...@chromium.org: Support SSL
renegotiation on Windows
http://code.google.com/p/chromium/issues/detail?id=6893
The following revision refers to this bug:
http://src.chromium.org/viewvc/chrome?view=rev&revision=12229
------------------------------------------------------------------------
r12229 | w...@chromium.org | 2009-03-20 16:17:06 -0700 (Fri, 20 Mar 2009) |
21 lines
Changed paths:
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/base/ssl_client_socket_win.cc?r1=12229&r2=12228
M
http://src.chromium.org/viewvc/chrome/trunk/src/net/base/ssl_client_socket_win.h?r1=12229&r2=12228
Implement SSL renegotiation.
In the Windows Schannel API, a server requests renegotiation
when DecryptMessage (decrypting received data) returns
SEC_I_RENEGOTIATE. We need to jump to the handshake
sequence, and when handshake completes, come back to reading
data.
I also cleaned up the code. I created the
SetNextStateForRead and FreeSendBuffer functions to share
common code, and made sure our handshake sequence is
completely equivalent to the handshake sequence in the
Platform SDK WebClient.c sample.
R=rvargas
BUG=6893
TEST=Visit these sites, which request SSL renegotiation:
https://secure.skandiabanken.se/Skbsecure/LoginInternet/SKBLoginInternet.aspx
https://secure.skandiabanken.no/SkbSecure/Authentication/Otp/Default.ashx
https://www.myopenid.com/signin_certificate
Review URL: http://codereview.chromium.org/42380
------------------------------------------------------------------------
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
