You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
my server use tls1.3 draft 18, i change supportedVersion to 0x7f12 , then test ,always get AEAD decrypt failed error , when i watch cloudflare/tls-tris, i found some difference:
when define CipherSuiteParams
your code :
typecipherSuitestruct {
iduint16// the lengths, in bytes, of the key material needed for each component.keyLenintmacLenintivLenintkafunc(versionuint16) keyAgreement// flags is a bitmask of the suite* values, above.flagsintcipherfunc(key, iv []byte, isReadbool) interface{}
macfunc(versionuint16, macKey []byte) macFunctionaeadfunc(key, fixedNonce []byte) cipher.AEAD
}
varcipherSuites= []*cipherSuite{
// TLS 1.3 ciphersuites specify only the AEAD and the HKDF hash.
{TLS_CHACHA20_POLY1305_SHA256, 32, 0, 12, nil, suiteTLS13, nil, nil, aeadChaCha20Poly1305},
{TLS_AES_128_GCM_SHA256, 16, 0, 4, nil, suiteTLS13, nil, nil, aeadAESGCM13},
{TLS_AES_256_GCM_SHA384, 32, 0, 4, nil, suiteTLS13|suiteSHA384, nil, nil, aeadAESGCM13},
TLS_AES_128_GCM_SHA256 and TLS_AES_256_GCM_SHA384 ivLen is 4。is your ivLen error?
The text was updated successfully, but these errors were encountered:
TLS_AES_128_GCM_SHA256 and TLS_AES_256_GCM_SHA384 ivLen is 4。is your ivLen error?
No, this is an issue in tris, TLS 1.3 needs 12 bytes nonce. In TLS 1.2 there is a 4-byte implicit nonce (derived from the master secret) and a 8 byte explicit nonce (taken from the record), at least for AES-GCM. Maybe that is where the confusion came from.
Perhaps you could give more details about your setup, what client and server implementation are you using?
my server use tls1.3 draft 18, i change
supportedVersion
to0x7f12
, then test ,always getAEAD decrypt failed
error , when i watch cloudflare/tls-tris, i found some difference:when define
CipherSuiteParams
your code :
cloudflare
define :TLS_AES_128_GCM_SHA256
andTLS_AES_256_GCM_SHA384
ivLen is 4。is yourivLen
error?The text was updated successfully, but these errors were encountered: