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: Tue, 21 Dec 2021 11:48:04 +0100 [thread overview]
Message-ID: <YcGw5Lyo+hBEnlFD@pevik> (raw)
In-Reply-To: <aafb5351-a73a-dac3-b0fa-3faad707bafa@linux.ibm.com>
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.
./keyctl09 -i500
keyctl09.c:49: TPASS: Encrypted keys were successfully instantiated and read
keyctl09.c:49: TPASS: Encrypted keys were successfully instantiated and read
...
keyctl09.c:33: TFAIL: Failed to instantiate encrypted key using payload decrypted data
(It's always good to put higher number iterations.)
Kind regards,
Petr
WARNING: multiple messages have this Message-ID (diff)
From: Petr Vorel <pvorel@suse.cz>
To: Nageswara Sastry <rnsastry@linux.ibm.com>
Cc: linux-integrity@vger.kernel.org, Yael Tiomkin <yaelt@google.com>,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v2] syscalls/keyctl09: test encrypted keys.
Date: Tue, 21 Dec 2021 11:48:04 +0100 [thread overview]
Message-ID: <YcGw5Lyo+hBEnlFD@pevik> (raw)
In-Reply-To: <aafb5351-a73a-dac3-b0fa-3faad707bafa@linux.ibm.com>
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.
./keyctl09 -i500
keyctl09.c:49: TPASS: Encrypted keys were successfully instantiated and read
keyctl09.c:49: TPASS: Encrypted keys were successfully instantiated and read
...
keyctl09.c:33: TFAIL: Failed to instantiate encrypted key using payload decrypted data
(It's always good to put higher number iterations.)
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2021-12-21 10:48 UTC|newest]
Thread overview: 16+ 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 2:37 ` [LTP] " Yael Tiomkin via ltp
2021-12-21 9:01 ` Petr Vorel
2021-12-21 9:01 ` [LTP] " Petr Vorel
2021-12-21 9:21 ` Nageswara Sastry
2021-12-21 9:21 ` [LTP] " Nageswara Sastry
2021-12-21 10:48 ` Petr Vorel [this message]
2021-12-21 10:48 ` Petr Vorel
2021-12-22 5:11 ` Nageswara Sastry
2021-12-22 5:11 ` [LTP] " Nageswara Sastry
2021-12-22 9:10 ` Petr Vorel
2021-12-22 9:10 ` [LTP] " Petr Vorel
2021-12-22 15:14 ` Eric Biggers
2021-12-22 15:14 ` [LTP] " Eric Biggers
2021-12-22 15:33 ` Eric Biggers
2021-12-22 15:33 ` [LTP] " 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=YcGw5Lyo+hBEnlFD@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 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.