Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268248AbUIGQhr (ORCPT ); Tue, 7 Sep 2004 12:37:47 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268279AbUIGQhk (ORCPT ); Tue, 7 Sep 2004 12:37:40 -0400 Received: from mx1.redhat.com ([66.187.233.31]:15010 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S268248AbUIGQgM (ORCPT ); Tue, 7 Sep 2004 12:36:12 -0400 Date: Tue, 7 Sep 2004 12:36:03 -0400 (EDT) From: James Morris X-X-Sender: jmorris@thoron.boston.redhat.com To: Michal Ludvig cc: Andreas Happe , , Subject: Re: [cryptoapi/sysfs] display cipher details in sysfs In-Reply-To: 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: 1029 Lines: 35 On Mon, 6 Sep 2004, Michal Ludvig wrote: > I'd prefer to have the algorithms grouped by "type" ("cipher", "digest", > "compress")? Then the apps could easily see only the algos that thay are > interested in... This could be done with symlinks. Have a master algorithim directory, and symlinks to different views (e.g. 'ciphers'). > Few notes: > - - some algorithms allow only discrete set of keysizes (e.g. AES can do > 128b, 192b and 256b). Can we instead of min/max have a file 'keysize' with > either: > minsize-maxsize > or > size1,size2,size3 > ? > > - - ditto for blocksize? I don't think it's worth complicating the kernel code just to see that AES does in fact have the three key sizes required by the specification. - 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/