Hello Jan, Thank you for your answer.
Op do 4 apr. 2019 om 12:40 schreef Jan Just Keijser <janj...@nikhef.nl>: > so the TLS cipher name includes names for both symmetric encryption and > symmetric authentication *separately* : with GCM ciphers you do both of > them in one go, but the TLS cipher still lists them separately. > I understand that, but since GCM already handles both encryption and authentication, I was wondering what the SHA-384 (which is not part of AES-GCM) was used for. Might it indicate the PRF used for key derivation? Are there perhaps two authentication tags used for the control channel (GHASH and SHA-384)? Also note that this cipher is the cipher used for the *control channel*, > not for the data channel and is the result of the "regular" TLS > negotiation that happens when the control channel is established. > Thanks, I was not fully aware that the data channel was negotiated separately from this cipher suite. Kind regards, Pieter
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
