From: David Howells <dhowells@redhat.com>
To: "Jan Sebastian Götte" <linux@jaseg.de>
Cc: dhowells@redhat.com, Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <baoquan.he@linux.dev>,
Mike Rapoport <rppt@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
Dave Young <ruirui.yang@linux.dev>,
Jarkko Sakkinen <jarkko@kernel.org>,
Paul Moore <paul@paul-moore.com>,
James Morris <jmorris@namei.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Mimi Zohar <zohar@linux.ibm.com>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
Rob Herring <robh@kernel.org>,
Saravana Kannan <saravanak@kernel.org>,
Coiby Xu <coxu@redhat.com>,
"devicetree@vger.kernel.org"@kvack.org,
"linux-kernel@vger.kernel.org"@kvack.org,
"kexec@lists.infradead.org"@kvack.org,
"keyrings@vger.kernel.org"@kvack.org,
"linux-mm@kvack.org"@kvack.org,
"linux-security-module@vger.kernel.org"@kvack.org,
"linux-integrity@vger.kernel.org"@kvack.org
Subject: Re: [PATCH 4/4] security/keys: zeroize key payloads before kdump
Date: Fri, 31 Jul 2026 23:50:11 +0100 [thread overview]
Message-ID: <2259835.1785538211@warthog.procyon.org.uk> (raw)
In-Reply-To: <20260731154608.153258-5-linux@jaseg.de>
I've no particular objection to this, though I'd prefer the name 'wipe' to
'zeroize'.
You should also wipe fscrypt, tls, rxrpc*, ceph and cifs spnego type keys and
maybe asymmetric type keys.
David
next prev parent reply other threads:[~2026-07-31 22:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-31 15:46 [PATCH 0/4] CRASH_ZEROIZE: Wipe secrets before kdump Jan Sebastian Götte
2026-07-31 15:46 ` [PATCH 1/4] of/kexec: fix typo in comment (usable-memory-range) Jan Sebastian Götte
2026-07-31 15:46 ` [PATCH 2/4] kexec: add CRASH_ZEROIZE to wipe secrets before kdump Jan Sebastian Götte
2026-08-05 4:19 ` sashiko-bot
2026-07-31 15:46 ` [PATCH 3/4] mm/secretmem: zeroize secret pages " Jan Sebastian Götte
2026-08-05 4:26 ` sashiko-bot
2026-07-31 15:46 ` [PATCH 4/4] security/keys: zeroize key payloads " Jan Sebastian Götte
2026-07-31 22:50 ` David Howells [this message]
2026-08-05 4:29 ` sashiko-bot
2026-08-01 14:03 ` [PATCH 0/4] CRASH_ZEROIZE: Wipe secrets " Baoquan He
2026-08-01 16:31 ` Jan Sebastian Götte
2026-08-02 5:08 ` Dave Young
2026-08-02 10:20 ` Jan Sebastian Götte
2026-08-03 12:12 ` Dave Young
2026-08-03 12:54 ` Jan Sebastian Götte
2026-08-03 9:59 ` David Howells
2026-08-03 12:00 ` Dave Young
-- strict thread matches above, loose matches on Subject: below --
2026-07-31 16:27 Jan Sebastian Götte
2026-07-31 16:27 ` [PATCH 4/4] security/keys: zeroize key payloads " Jan Sebastian Götte
2026-07-31 16:45 ` sashiko-bot
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=2259835.1785538211@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc="devicetree@vger.kernel.org"@kvack.org \
--cc="kexec@lists.infradead.org"@kvack.org \
--cc="keyrings@vger.kernel.org"@kvack.org \
--cc="linux-integrity@vger.kernel.org"@kvack.org \
--cc="linux-kernel@vger.kernel.org"@kvack.org \
--cc="linux-mm@kvack.org"@kvack.org \
--cc="linux-security-module@vger.kernel.org"@kvack.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=akpm@linux-foundation.org \
--cc=baoquan.he@linux.dev \
--cc=coxu@redhat.com \
--cc=jarkko@kernel.org \
--cc=jmorris@namei.org \
--cc=linux@jaseg.de \
--cc=pasha.tatashin@soleen.com \
--cc=paul@paul-moore.com \
--cc=pratyush@kernel.org \
--cc=robh@kernel.org \
--cc=rppt@kernel.org \
--cc=ruirui.yang@linux.dev \
--cc=saravanak@kernel.org \
--cc=serge@hallyn.com \
--cc=zohar@linux.ibm.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.