Progress® Telerik® Fiddler™ Classic Feedback Portal
Back to Feed
Request a Feature Report a Bug
Need More Info
Last Updated: 24 Dec 2023 03:00 by Eric
Nadia
Created on: 18 Nov 2023 05:19
Type: Bug Report
1
Win32 (SChannel) Native Error Code: 0x80090326 When access auth.btxo.cn

good morning 

i got error while capturing my app to auth.btxo.cn

=== Windows 10 64bit OS==

===Protocols I have enabled: <client>;ssl2;ssl3;tls1.0;tls1.1;tls1.2

====== Message from Fiddler v5.0.20211.51073  for .NET v4.6.1
HTTP/1.1 200 Connection Established
FiddlerGateway: Direct
Connection: close

fiddler.network.https> HTTPS handshake to 104.21.46.118 (for #17) failed. System.Security.Authentication.AuthenticationException A call to SSPI failed, see inner exception. < The message received was unexpected or badly formatted

Win32 (SChannel) Native Error Code: 0x80090326

 

Any help ??

Thank you

 

The fiddler response

A SSLv3-compatible ClientHello handshake was found. Fiddler extracted the parameters below.

Version: 3.3 (TLS/1.2)
Random: 65 58 47 1D 28 AB A2 68 50 33 C7 75 1E A4 8B F5 9D A6 FB A0 F9 D2 54 FA 93 D5 AE 78 E5 26 7D 89
"Time": 26/07/1985 15:35:49
SessionID: empty
Extensions: 
server_name auth.btxo.cn
status_request OCSP - Implicit Responder
supported_groups x25519 [0x1d], secp256r1 [0x17], secp384r1 [0x18]
ec_point_formats uncompressed [0x0]
signature_algs rsa_pss_rsae_sha256, rsa_pss_rsae_sha384, rsa_pss_rsae_sha512, rsa_pkcs1_sha256, rsa_pkcs1_sha384, rsa_pkcs1_sha1, ecdsa_secp256r1_sha256, ecdsa_secp384r1_sha384, ecdsa_sha1, dsa_sha1, rsa_pkcs1_sha512, ecdsa_secp521r1_sha512
SessionTicket empty
ALPN http/1.1
extended_master_secret empty
renegotiation_info 00
Ciphers: 
[C02C] TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
[C02B] TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
[C030] TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
[C02F] TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
[009F] TLS_DHE_RSA_WITH_AES_256_GCM_SHA384
[009E] TLS_DHE_RSA_WITH_AES_128_GCM_SHA256
[C024] TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384
[C023] TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256
[C028] TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384
[C027] TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
[C00A] TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
[C009] TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
[C014] TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
[C013] TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
[009D] TLS_RSA_WITH_AES_256_GCM_SHA384
[009C] TLS_RSA_WITH_AES_128_GCM_SHA256
[003D] TLS_RSA_WITH_AES_256_CBC_SHA256
[003C] TLS_RSA_WITH_AES_128_CBC_SHA256
[0035] TLS_RSA_WITH_AES_256_CBC_SHA
[002F] TLS_RSA_WITH_AES_128_CBC_SHA
[000A] SSL_RSA_WITH_3DES_EDE_SHA

Compression: 
[00] NO_COMPRESSION

2 comments
Eric
Posted on: 24 Dec 2023 03:00

You absolutely should NOT have ssl2 or ssl3 enabled in your options; this can definitely cause problems.

The error code you've shared is SEC_E_ILLEGAL_MESSAGE, which happens if the server returns a fatal alert in the handshake.

https://www.ssllabs.com/ssltest/analyze.html?d=auth.btxo.cn&s=104.21.86.227&latest supports TLS1.0 and higher. 

ADMIN
Nick Iliev
Posted on: 20 Nov 2023 10:46

Hello Nadia,

 

The request can't be tested through a browser due to the server returning non-browser requirements, so we can't investigate what might be causing the error message on your side (as we don't have access to the client that executes the request). That said, try to completely reset the Fiddler Classic certificates (through the Tools> Options > HTTPS > Actions > Reset Certificates option) and, if needed, reconfigure or change the client that executes the request.

As a side note, you can also test the request while using Fiddler Everywhere, which supports TLS 1.3 and HTTP/2 - it could be that the server is failing to negotiate the TLS handshake due to specific cipher requirements.

 

Regards,
Nick Iliev
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.

Create an account Log In
View
Type
Status