Re: Error SEC_E_ALGORITHM_MISMATCH from InitializeSecurityContext
- From: "Gianluca Varenni" <gianluca.varenni@xxxxxxxxxxxx>
- Date: Fri, 21 Apr 2006 08:04:48 -0700
"John Banes" <jabanes@xxxxxxxxxxxxxxxxxx> wrote in message
news:OjKTpGPZGHA.4760@xxxxxxxxxxxxxxxxxxxxxxx
This can happen when the client supports only TLS and the server only
supports SSL3. Because the cipher suite numbers used by SSL3 and TLS are
the same, the ClientHello message is slightly ambiguous in this case. You
should be able to see if my guess is right by looking at the version field
in the ServerHello messsage.
No, the server does support TLS1 (the version field in server Hello is
0x0301, i.e. TLS1.0)
Is it possible that the client certificate has some problems (don't ask me
which ones), but this problem is trapped by
InitializeSecurityContext (that uses it to generate the TLS record with the
client certificate) instead of AcquireCredentialsHandle (that basically
binds the client certificate with the Credential Handle)??
Have a nice day
GV
Regards,
John
"Gianluca Varenni" <gianluca.varenni@xxxxxxxxxxxx> wrote in message
news:uFACDTMZGHA.3972@xxxxxxxxxxxxxxxxxxxxxxx
Hi all.
I'm working on an authentication protocol based on TLS1, as an example
I'm starting using the sample Samples\Security\SSPI\SSL in the Platform
SDK.
The problem I'm encountering is that InitializeSecurityContext returns
SEC_E_ALGORITHM_MISMATCH when it receives the a TLS message from the
server containing these records
- Server Hello
- Certificate
- Certificate Request
- Server Hello Done
The Client Hello message announces that it supports
TLS_RSA_WITH_RC4_128_MD5 and TLS_RSA_RC4_128_SHA (null compression), and
the server (in the Server Hello record) agrees to use
TLS_RSA_WITH_RC4_128_MD5 (and null compression). This is whatI see this
sniffing the packets on the network.
What can cause this error?
Have a nice day
GV
.
- References:
- Error SEC_E_ALGORITHM_MISMATCH from InitializeSecurityContext
- From: Gianluca Varenni
- Re: Error SEC_E_ALGORITHM_MISMATCH from InitializeSecurityContext
- From: John Banes
- Error SEC_E_ALGORITHM_MISMATCH from InitializeSecurityContext
- Prev by Date: Re: Undocumented behavior with SetNamedSecurityInfo
- Next by Date: Re: "Attaching" a Key BLOB to a PCCERT_CONTTEXT and import the cer
- Previous by thread: Re: Error SEC_E_ALGORITHM_MISMATCH from InitializeSecurityContext
- Next by thread: Using AccessCheck() with MAXIMUM_ALLOWED and NULL Dacl
- Index(es):
Relevant Pages
|