s***@keemail.me
2017-03-31 15:53:17 UTC
I've been testing the new tls-crypt option and noticed a difference when connecting to the server.
With tls-auth enabled, if the defined algorithm for "auth" differs in client and server, the client can't successfully connect. Â "Initialization Sequence Completed" is never printed.
Now, with tls-crypt, if the defined algorithm for "auth" differs in client and server, the client connects just fine, "Initialization Sequence Completed" is printed but the server prints "Authenticate/Decrypt packet error: packet HMAC authentication failed".
The client also prints this message, if it receives data from the server.
The error itself is clear and expected, but why does the connection "succeed" with tls-crypt, whereas it doesn't complete with tls-auth?
Kind regards,
SaAtomic
With tls-auth enabled, if the defined algorithm for "auth" differs in client and server, the client can't successfully connect. Â "Initialization Sequence Completed" is never printed.
Now, with tls-crypt, if the defined algorithm for "auth" differs in client and server, the client connects just fine, "Initialization Sequence Completed" is printed but the server prints "Authenticate/Decrypt packet error: packet HMAC authentication failed".
The client also prints this message, if it receives data from the server.
The error itself is clear and expected, but why does the connection "succeed" with tls-crypt, whereas it doesn't complete with tls-auth?
Kind regards,
SaAtomic