[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aae9bc89-ca34-400f-9c5e-44be1df2befa@gmail.com>
Date: Sat, 30 Mar 2024 21:38:05 -0500
From: Denis Kenzior <denkenz@...il.com>
To: Eric Biggers <ebiggers@...nel.org>,
James Bottomley <James.Bottomley@...senpartnership.com>
Cc: Zhang Yiqun <zhangyiqun@...tium.com.cn>, dhowells@...hat.com,
jarkko@...nel.org, corbet@....net, keyrings@...r.kernel.org,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-crypto@...r.kernel.org
Subject: Re: [PATCH] KEYS: Add ECDH support
Hi Eric,
>
> Amusingly, the existing KEYCTL_DH_* APIs, and the KEYCTL_ECDH_* APIs proposed by
> this patch, only operate on user keys that the process has READ access to. This
> means that the keys can be trivially extracted by a shell script running in your
> user session. That's *less* secure than using an isolated process...
>
I can see this being true for user or session keys, but I don't think this is
true of process or thread specific keys. At least I couldn't read any keys out
of a test app when I tried.
Regards,
-Denis
Powered by blists - more mailing lists