From: Sabrina Dubroca <sd@queasysnail•net>
To: netdev@vger•kernel.org
Cc: Sabrina Dubroca <sd@queasysnail•net>,
Aviad Yehezkel <aviadye@mellanox•com>,
Boris Pismenny <borisp@mellanox•com>,
Dave Watson <davejwatson@fb•com>, Vakul Garg <vakul.garg@nxp•com>
Subject: [PATCH net v2 0/3] tls: don't leave keys in kernel memory
Date: Wed, 12 Sep 2018 17:44:40 +0200 [thread overview]
Message-ID: <cover.1536766755.git.sd@queasysnail.net> (raw)
There are a few places where the RX/TX key for a TLS socket is copied
to kernel memory. This series clears those memory areas when they're no
longer needed.
v2: add union tls_crypto_context, following Vakul Garg's comment
swap patch 2 and 3, using new union in patch 3
Sabrina Dubroca (3):
tls: don't copy the key out of tls12_crypto_info_aes_gcm_128
tls: zero the crypto information from tls_context before freeing
tls: clear key material from kernel memory when do_tls_setsockopt_conf
fails
include/net/tls.h | 19 +++++++++----------
net/tls/tls_device.c | 6 +++---
net/tls/tls_device_fallback.c | 2 +-
net/tls/tls_main.c | 22 ++++++++++++++++------
net/tls/tls_sw.c | 13 +++++--------
5 files changed, 34 insertions(+), 28 deletions(-)
--
2.18.0
next reply other threads:[~2018-09-12 20:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 15:44 Sabrina Dubroca [this message]
2018-09-12 15:44 ` [PATCH net v2 1/3] tls: don't copy the key out of tls12_crypto_info_aes_gcm_128 Sabrina Dubroca
2018-09-12 15:44 ` [PATCH net v2 2/3] tls: zero the crypto information from tls_context before freeing Sabrina Dubroca
2018-09-12 15:44 ` [PATCH net v2 3/3] tls: clear key material from kernel memory when do_tls_setsockopt_conf fails Sabrina Dubroca
2018-09-13 19:04 ` [PATCH net v2 0/3] tls: don't leave keys in kernel memory David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1536766755.git.sd@queasysnail.net \
--to=sd@queasysnail$(echo .)net \
--cc=aviadye@mellanox$(echo .)com \
--cc=borisp@mellanox$(echo .)com \
--cc=davejwatson@fb$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=vakul.garg@nxp$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox