All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodolfo Giometti <giometti@enneenne.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Eric Biggers <ebiggers@kernel.org>,
	linux-crypto@vger.kernel.org,
	"David S . Miller" <davem@davemloft.net>,
	keyrings@vger.kernel.org, David Howells <dhowells@redhat.com>,
	Lukas Wunner <lukas@wunner.de>,
	Ignat Korchagin <ignat@cloudflare.com>
Subject: Re: [V1 0/4] User API for KPP
Date: Tue, 16 Sep 2025 10:22:45 +0200	[thread overview]
Message-ID: <fc1459db-2ce7-4e99-9f5b-e8ebd599f5bc@enneenne.com> (raw)
In-Reply-To: <aMjjPV21x2M_Joi1@gondor.apana.org.au>

On 16/09/25 06:10, Herbert Xu wrote:
> On Mon, Sep 15, 2025 at 05:47:56PM +0200, Rodolfo Giometti wrote:
>>
>> The main purpose of using this implementation is to be able to use the
>> kernel's trusted keys as private keys. Trusted keys are protected by a TPM
>> or other hardware device, and being able to generate private keys that can
>> only be (de)encapsulated within them is (IMHO) a very useful and secure
>> mechanism for storing a private key.
> 
> If the issue is key management then you should be working with
> David Howell on creating an interface that sits on top of the
> keyring subsystem.
> 
> The Crypto API doesn't care about keys.

No, the problem concerns the use of the Linux keyring (specifically, trusted 
keys and other hardware-managed keys) with cryptographic algorithms.

 From a security standpoint, AF_ALG and keyctl's trusted keys are a perfect 
match to manage secure encryption and decryption, so why not do the same with 
KPP operations (or other cryptographic operations)?

I know there might be issues with allowing user space to use this interface, but:

1) I think this mechanism can get its best when implemented in hardware, and

2) (hey!) we're developers who know what they're doing! :)

This patch series is just a sample of the improvements I'd like to make on this 
front. Please tell me if you don't intend to add these mechanisms to the kernel 
at all, or if I have any chances, so I can decide whether to proceed or stop here.

Ciao,

Rodolfo

-- 
GNU/Linux Solutions                  e-mail: giometti@enneenne.com
Linux Device Driver                          giometti@linux.it
Embedded Systems                     phone:  +39 349 2432127
UNIX programming

  reply	other threads:[~2025-09-16  8:25 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-15  8:40 [V1 0/4] User API for KPP Rodolfo Giometti
2025-09-15  8:40 ` [V1 1/4] crypto ecdh.h: set key memory region as const Rodolfo Giometti
2025-09-16  6:50   ` kernel test robot
2025-09-16 17:19   ` kernel test robot
2025-09-15  8:40 ` [V1 2/4] crypto kpp.h: add new method set_secret_raw in struct kpp_alg Rodolfo Giometti
2025-09-15  8:40 ` [V1 3/4] crypto ecdh.c: define the ECDH set_secret_raw method Rodolfo Giometti
2025-09-15 14:46   ` kernel test robot
2025-09-15  8:40 ` [V1 4/4] crypto: add user-space interface for KPP algorithms Rodolfo Giometti
2025-09-15 14:50 ` [V1 0/4] User API for KPP Eric Biggers
2025-09-15 15:47   ` Rodolfo Giometti
2025-09-16  4:10     ` Herbert Xu
2025-09-16  8:22       ` Rodolfo Giometti [this message]
2025-09-16 10:21         ` Ignat Korchagin
2025-09-16 11:21           ` Rodolfo Giometti
2025-09-16 11:56             ` Ignat Korchagin
2025-09-16 12:33               ` Rodolfo Giometti
2025-09-16 12:43                 ` Ignat Korchagin
2025-09-16 13:07                   ` Rodolfo Giometti
2025-09-16 19:03                 ` Simo Sorce

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=fc1459db-2ce7-4e99-9f5b-e8ebd599f5bc@enneenne.com \
    --to=giometti@enneenne.com \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=ebiggers@kernel.org \
    --cc=herbert@gondor.apana.org.au \
    --cc=ignat@cloudflare.com \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=lukas@wunner.de \
    /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.