From: patchwork-bot+netdevbpf@kernel.org
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: davem@davemloft.net, kuba@kernel.org,
herbert@gondor.apana.org.au, netdev@vger.kernel.org
Subject: Re: [PATCH] xfrm: redact SA secret with lockdown confidentiality
Date: Sat, 12 Dec 2020 21:40:06 +0000 [thread overview]
Message-ID: <160780920694.16761.16740586954309280912.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201212085737.2101294-2-steffen.klassert@secunet.com>
Hello:
This patch was applied to netdev/net-next.git (refs/heads/master):
On Sat, 12 Dec 2020 09:57:37 +0100 you wrote:
> From: Antony Antony <antony.antony@secunet.com>
>
> redact XFRM SA secret in the netlink response to xfrm_get_sa()
> or dumpall sa.
> Enable lockdown, confidentiality mode, at boot or at run time.
>
> e.g. when enabled:
> cat /sys/kernel/security/lockdown
> none integrity [confidentiality]
>
> [...]
Here is the summary with links:
- xfrm: redact SA secret with lockdown confidentiality
https://git.kernel.org/netdev/net-next/c/c7a5899eb26e
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2020-12-12 21:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 8:57 pull request (net-next): ipsec-next 2020-12-12 Steffen Klassert
2020-12-12 8:57 ` [PATCH] xfrm: redact SA secret with lockdown confidentiality Steffen Klassert
2020-12-12 21:40 ` patchwork-bot+netdevbpf [this message]
2020-12-12 21:40 ` pull request (net-next): ipsec-next 2020-12-12 patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2020-07-28 15:47 [PATCH ipsec-next] xfrm: add /proc/sys/core/net/xfrm_redact_secret Antony Antony
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
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=160780920694.16761.16740586954309280912.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).