Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S265110AbUFVTio (ORCPT ); Tue, 22 Jun 2004 15:38:44 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S265672AbUFVTeS (ORCPT ); Tue, 22 Jun 2004 15:34:18 -0400 Received: from mx1.redhat.com ([66.187.233.31]:33155 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S265110AbUFVSI0 (ORCPT ); Tue, 22 Jun 2004 14:08:26 -0400 Date: Tue, 22 Jun 2004 14:08:08 -0400 (EDT) From: James Morris X-X-Sender: jmorris@thoron.boston.redhat.com To: David Howells cc: Joy Latten , , , , Subject: Re: RSA [patch #1] In-Reply-To: <18339.1087923439@redhat.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 826 Lines: 25 On Tue, 22 Jun 2004, David Howells wrote: > > > I think the way to manage keyrings is via a filesystem API, which > > different asymmetric crypto apps can register with. > > I'm not sure what you're thinking of exactly. Can you elaborate? Different kernel asymmetric crypto apps (e.g. module signature checker) will need to be able to manage independent keyrings, and a common filesystem API would be useful for this. e.g. during startup, some init script loads keyrings into the kernel via /proc/crypto/keyring/app/addkey - James -- James Morris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/