diff options
author | Sabrina Dubroca <sd@queasysnail.net> | 2018-01-16 16:04:28 +0100 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2018-01-17 16:16:04 -0500 |
commit | 6db959c82eb039a151d95a0f8b7dea643657327a (patch) | |
tree | 1004c0d1cbf18fa4ab30034bd6cd38205cc32e77 /drivers/opp/debugfs.c | |
parent | 877d17c79b66466942a836403773276e34fe3614 (diff) | |
download | linux-6db959c82eb039a151d95a0f8b7dea643657327a.tar.bz2 |
tls: reset crypto_info when do_tls_setsockopt_tx fails
The current code copies directly from userspace to ctx->crypto_send, but
doesn't always reinitialize it to 0 on failure. This causes any
subsequent attempt to use this setsockopt to fail because of the
TLS_CRYPTO_INFO_READY check, eventhough crypto_info is not actually
ready.
This should result in a correctly set up socket after the 3rd call, but
currently it does not:
size_t s = sizeof(struct tls12_crypto_info_aes_gcm_128);
struct tls12_crypto_info_aes_gcm_128 crypto_good = {
.info.version = TLS_1_2_VERSION,
.info.cipher_type = TLS_CIPHER_AES_GCM_128,
};
struct tls12_crypto_info_aes_gcm_128 crypto_bad_type = crypto_good;
crypto_bad_type.info.cipher_type = 42;
setsockopt(sock, SOL_TLS, TLS_TX, &crypto_bad_type, s);
setsockopt(sock, SOL_TLS, TLS_TX, &crypto_good, s - 1);
setsockopt(sock, SOL_TLS, TLS_TX, &crypto_good, s);
Fixes: 3c4d7559159b ("tls: kernel TLS support")
Signed-off-by: Sabrina Dubroca <sd@queasysnail.net>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/opp/debugfs.c')
0 files changed, 0 insertions, 0 deletions