From: Petr Vorel <pvorel@suse.cz>
To: Nageswara Sastry <rnsastry@linux.ibm.com>
Cc: Yael Tiomkin <yaelt@google.com>,
ltp@lists.linux.it, zohar@linux.ibm.com,
linux-integrity@vger.kernel.org
Subject: Re: [PATCH v2] syscalls/keyctl09: test encrypted keys.
Date: Wed, 22 Dec 2021 10:10:28 +0100 [thread overview]
Message-ID: <YcLrhP62jewzFgqn@pevik> (raw)
In-Reply-To: <8c785afa-4564-d7ca-0bb8-34d5b5ca89bd@linux.ibm.com>
Hi all,
> On 21/12/21 4:18 pm, Petr Vorel wrote:
> > Hi Nageswara,
> > > On 21/12/21 8:07 am, Yael Tiomkin wrote:
> > > > Test that encrypted keys can be instantiated using
> > > > both user-provided decrypted data
> > > > (https://lore.kernel.org/linux-integrity/20211213192030.125091-1-yaelt@google.com/),
> > > > or kernel-generated numbers.
> > > > Signed-off-by: Yael Tiomkin <yaelt@google.com>
> > > Tested on ppc64le platform
> > I suppose it also fails on ppc64le when run more iterations.
> Tried with -i500, -i5000 and -i50000 also ... no failures were seen on
> ppc64le architecture.
> Summary:
> passed 500
> failed 0
> Summary:
> passed 5000
> failed 0
> Summary:
> passed 50000
> failed 0
Interesting, thx for info. It's either arch specific or specific to openSUSE
kernel on my laptop (~ 5.16.0-rc5) where I tested it. Testing on
various VM it works well (including openSUSE with latest kernel stable). It also
works on RPI 4 with openSUSE kernel.
Also it fails on 2 VMs with fips enabled: Debian testing (immediately) and SLES
15-SP4 (after 63 iterations - the same number as 5.16.0-rc5 on my laptop):
keyctl09.c:33: TBROK: Failed to instantiate encrypted key using payload decrypted data
but on my laptop I don't use fips.
Kind regards,
Petr
next prev parent reply other threads:[~2021-12-22 9:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-21 2:37 [PATCH v2] syscalls/keyctl09: test encrypted keys Yael Tiomkin
2021-12-21 9:01 ` Petr Vorel
2021-12-21 9:21 ` Nageswara Sastry
2021-12-21 10:48 ` Petr Vorel
2021-12-22 5:11 ` Nageswara Sastry
2021-12-22 9:10 ` Petr Vorel [this message]
2021-12-22 15:14 ` Eric Biggers
2021-12-22 15:33 ` Eric Biggers
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=YcLrhP62jewzFgqn@pevik \
--to=pvorel@suse.cz \
--cc=linux-integrity@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=rnsastry@linux.ibm.com \
--cc=yaelt@google.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 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).