All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: antony.antony@secunet.com
Cc: steffen.klassert@secunet.com, netdev@vger.kernel.org,
	herbert@gondor.apana.org.au, smueller@chronox.de,
	antony@phenome.org
Subject: Re: [PATCH ipsec-next v3] xfrm: add /proc/sys/core/net/xfrm_redact_secret
Date: Thu, 27 Aug 2020 13:20:10 -0700 (PDT)	[thread overview]
Message-ID: <20200827.132010.1826967607816087414.davem@davemloft.net> (raw)
In-Reply-To: <20200827201536.GB11789@moon.secunet.de>

From: Antony Antony <antony.antony@secunet.com>
Date: Thu, 27 Aug 2020 22:15:36 +0200

> If there is a way to set lockdown per net namespace it would be
> better than /proc/sys/core/net/xfrm_redact_secret.

Lockmode is a whole system attribute.

As should any facility that restricts access to keying information
stored inside of the kernel.

  reply	other threads:[~2020-08-27 20:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-28 15:47 [PATCH ipsec-next] xfrm: add /proc/sys/core/net/xfrm_redact_secret Antony Antony
2020-07-28 16:22 ` Herbert Xu
2020-07-28 18:36   ` Antony Antony
2020-07-28 19:09 ` Stephan Mueller
2020-08-20 10:53   ` Antony Antony
2020-08-20 12:04 ` [PATCH ipsec-next v2] " Antony Antony
2020-08-20 15:10   ` Jakub Kicinski
2020-08-20 15:14   ` Nicolas Dichtel
2020-08-20 18:35 ` [PATCH ipsec-next v3] " Antony Antony
2020-08-20 22:42   ` David Miller
2020-08-24  6:00     ` Antony Antony
2020-08-27 20:15       ` Antony Antony
2020-08-27 20:20         ` David Miller [this message]
2020-10-16 13:36 ` [PATCH] xfrm: redact SA secret with lockdown confidentiality Antony Antony
2020-10-31 10:49   ` Steffen Klassert
2020-11-17 16:46     ` Antony Antony
2020-11-17 16:47   ` [PATCH ipsec-next v5] " Antony Antony
2020-11-23  6:42     ` Steffen Klassert

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=20200827.132010.1826967607816087414.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=antony.antony@secunet.com \
    --cc=antony@phenome.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=smueller@chronox.de \
    --cc=steffen.klassert@secunet.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.