-
Notifications
You must be signed in to change notification settings - Fork 103
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Verification of GCM tag failed: MAC check failed #1310
Comments
The new warnings in current master (1b4f36d):
|
With #1375 sporadic
Sometimes single
|
Also caught the bag in reverse scenario: checksum calculated by scapy_tls_ssl on abbreviated handshake is rejected by Tempesta, but accepted by Nginx+OpenSSL. Reproduces on tempesta-tech/tempesta-test#175 :
scapy_tls_ssl doesn't decrypt alerts, thus exact alert is not shown here. I also noticed two things: with the patch similar to one in the first one message (replace Tempesta with Nginx) everything is fine; due to the bug in fsm, Tempesta can read application data even if client Finished is not received and scapy_tls_ssl can receive valid responses from the server, i.e. key exchange is ok. |
(tintinweb/scapy-ssl_tls#163). RFC 5246 6.2.3.3 requires the explicit nonce (most usually sequence number) in the additional authenticated data (AAD), however crypto_data.sequence, used for the AAD creation in EAEADCryptoContainer, wasn't initialized with the explicit_nonce.
Current ScaPy-TLS handshake ran against Tempesta FW produces the warning:
However, if execute a test with following patch against
ak-737
branch as of data of the issue:agains Nginx with self signed certificates (just generated as described in the Wiki) with following config:
the test doesn't show the warning:
The text was updated successfully, but these errors were encountered: