Windows 10: QueryContextAttributes and DecryptMessage throwing error after successful handshake

QueryContextAttributes &hContext, SECPKG_ATTR_SIZES, &Sizes ;hContext is the lastest one, updated by acceptsecuritycontext . similarly , DecryptMessagephContext, &Message, 0, NULL; is throwing error :SEC_E_INVALID_HANDLE - A context handle that is not valid was specified in the phContext parameter.

:)

 

Intermittent problems with TLS handshake and being timed out

Check DNS settings for both network adapters. Your Wifi might be set to use a different DNS server.

Getting message when trying to connect - Windows 10 Forums

Option Two follow steps then pick a DNS server from the list in item 7. Personally I use CloudFlare DNS

EDIT: Reset router first as already suggested.

 

Schannel: clent end receiving a renegotiation token through DecryptMessage causes EncryptMessage to immediately fail with SEC_E_CONTEXT_EXPIRED (0x80090317)

I work on some internal communications libraries, and recently came across a problem recently with some of our unit tests involving Schannel and renegotiation. These unit tests exercise a state machine that recognizes a few states of the established security
context including "Authenticated", "RenegotiatePending" and "Renegotiate".

According to MSDN's articles on DecryptMessage and EncryptMessage, it is made clear that these methods can be called on separate threads concurrently with the same security context, though two instances of DecryptMessage or EncryptMessage may not be called
concurrently on separate threads when referring to the same security context. Renegotiation complicates matters by implying that, upon receipt of an alert token requesting renegotiation by the client from the server, the client must stop encrypting data to
send, perform the authentication handshake again, and then start up the encryption cycle again once that's all done. Renegotiation is detected on the client end by DecryptMessage, which emits an error SEC_I_RENEGOTIATE when that's what's going on. When we
get that error, we pause the encryption cycle occuring on its own thread, as mentioned before.

However, as soon as DecryptMessage emits SEC_I_RENEGOTIATE, before we have the chance to pause the encryption cycle, calls to EncryptMessage yield the error SEC_E_CONTEXT_EXPIRED. This is problematic, because constructed encrypted messages are generated
under a single security context.

The idea that we could wait until encryption was complete and pause the cycle to proceed with renegotiation tasks used to work until we installed updates within the last month. I'm running on Windows 10 and see the failure, and we've seen this on Windows
Server 2012 r2. I'm trying to collect more information.

Of course, if I lock the EncryptMessage and DecryptMessage to the same thread, there is no issue, as expected. This is difficult to implement in our current environment, which is heavily threaded.

Can anyone offer any suggestions, aside from a protocol re-do to support datagram fragmentation separated by renegotiation cycles? This really looks like a change in Schannel behavior.

[Moved from: Windows / Windows 10 / Network & internet]

 

Intermittent problems with TLS handshake and being timed out

Hi

I have a new Dell laptop running Windows 10 and Kaspersky.

When using MS Edge for Internet banking, I can sometimes connect straight through security and right through to statements. Other times I get the error code INET E CONNECTION TIMEOUT very quickly. There seems to be no rhyme nor reason when this will happen or how far into the bank site I get.

Using Mozilla Firefox, I get the same intermittent problem but this time it gets stuck on TLS handshake and just goes round and round.

I have just been successful in getting right through to statements at Lloyds on both browsers and have also ordered an item online successfully. So, I tried Halifax - no joy, now I get the error message or TLS handshake and on Firefox I can't even get Google, as it sticks on handshake for that site too.

All the rest of the computer is fine and I can run BBC I-player OK.

Any suggestions as to how to cure this would be welcome as it is very frustrating.

Thanks.