Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262023AbTGGKNL (ORCPT ); Mon, 7 Jul 2003 06:13:11 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262165AbTGGKNL (ORCPT ); Mon, 7 Jul 2003 06:13:11 -0400 Received: from blackbird.intercode.com.au ([203.32.101.10]:28178 "EHLO blackbird.intercode.com.au") by vger.kernel.org with ESMTP id S262023AbTGGKNJ (ORCPT ); Mon, 7 Jul 2003 06:13:09 -0400 Date: Mon, 7 Jul 2003 20:27:15 +1000 (EST) From: James Morris To: Christoph Hellwig cc: Thomas Spatzier , Subject: Re: crypto API and IBM z990 hardware support In-Reply-To: <20030707081159.B1848@infradead.org> 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: 665 Lines: 21 On Mon, 7 Jul 2003, Christoph Hellwig wrote: > This sounds like the right way to do it. The question is just whether we > want to put that complicated policy into the kernel or into some userspace > helper. A userspace helper sounds interesting, as we also need a way to allow unprivileged users to invoke kernel crypto, which may require modules to be loaded. - 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/