public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
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>,
	Ilya Lesokhin <ilyal@mellanox•com>
Subject: [PATCH net 0/3] tls: don't leave keys in kernel memory
Date: Wed,  5 Sep 2018 15:21:42 +0200	[thread overview]
Message-ID: <cover.1536152698.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.

Sabrina Dubroca (3):
  tls: don't copy the key out of tls12_crypto_info_aes_gcm_128
  tls: clear key material from kernel memory when do_tls_setsockopt_conf
    fails
  tls: zero the crypto information from tls_context before freeing

 include/net/tls.h  |  1 +
 net/tls/tls_main.c | 16 +++++++++++++---
 net/tls/tls_sw.c   |  5 +----
 3 files changed, 15 insertions(+), 7 deletions(-)

-- 
2.18.0

             reply	other threads:[~2018-09-05 17:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-05 13:21 Sabrina Dubroca [this message]
2018-09-05 13:21 ` [PATCH net 1/3] tls: don't copy the key out of tls12_crypto_info_aes_gcm_128 Sabrina Dubroca
2018-09-05 13:21 ` [PATCH net 2/3] tls: clear key material from kernel memory when do_tls_setsockopt_conf fails Sabrina Dubroca
2018-09-05 13:53   ` Boris Pismenny
2018-09-06  7:49     ` Sabrina Dubroca
2018-09-05 13:21 ` [PATCH net 3/3] tls: zero the crypto information from tls_context before freeing Sabrina Dubroca
2018-09-05 13:48   ` Vakul Garg
2018-09-06  7:42     ` Sabrina Dubroca

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.1536152698.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=ilyal@mellanox$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    /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