Re: [cryptoapi/sysfs] display cipher details in sysfs

From: Michal Ludvig (michal_at_logix.cz)
Date: 09/29/04

  • Next message: James Bottomley: "Re: Core scsi layer crashes in 2.6.8.1" 
    Date:	Wed, 29 Sep 2004 16:13:25 +0200 (CEST)
To: Andreas Happe <andreashappe@flatline.ath.cx>

    On Wed, 29 Sep 2004, Andreas Happe wrote:

    > just took a glance at preferences for algorithms yesterday. came up with
    > the attached code (does compile, don't think that it will boot, just
    > attached to illustrade my thinkings).

    I'll give it a try and read something more about kobjects and ksets as
    well ;-)

    > I inserted a cra_family list into cra_alg which stores all algorithms
    > which share the same name but different module names. When selecting an
    > algorithm the preference is looked after (it should be made a writeable
    > sysfs attribute - would make runtime user selection of prefered
    > algorithm very intuitive).

    For now it could be a module option or even hardcoded in the .ko. It won't
    be user-writable anyway, only root-writable. And if root wouldn't want to
    use the most preferred module, he could simply not load it...

    The reason why I wanted the cra_preference is a situation where a given
    functionality is non-modular and compiled into the kernel and requires an
    algorithm thet in turn will have to be compiled in as well. Distributors
    would of course select the pure software implementation for this. But then
    you install a cryptocard - without preferences you couldn't load a module
    with driver for it.

    > Main problems are removal of algorithms (havn't covered that yet) and
    > the display of different algorithms with same names in sysfs as cra_name
    > is the name of the directory (not module_name(alg->cra_module)).
    >
    > Creating a hierarchie cra_alg <>- cra_implementation would be the most
    > clean solution. Just add a kset with the different cra_implementations
    > (which would contain a kobject, preference, module pointer) to any
    > given algorithm (which would contain all blocksize, blah data).

    Michal Ludvig 

    -- 
* A mouse is a device used to point at the xterm you want to type in.
* Personal homepage - http://www.logix.cz/michal
-
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/
  • Next message: James Bottomley: "Re: Core scsi layer crashes in 2.6.8.1"

    Relevant Pages

    • Re: a clueless bloke tells Xilinx to get a move on
      ... suggestions in this thread (including anonymous: incremental compile) ... have merit independent of whether Brannon does floorplanning. ... Map/Par/Bitgen to finish, I hereby petition Xilinx, Inc., to consider ... Bound algorithm instead. ...
      (comp.arch.fpga)
    • Re: Obfuscation and Salamander
      ... > exposed in its assemblies/builds? ... the compiler that a function should be compiled as x86 rather than IL, ... able to work out your algorithm. ... by compilers when they compile a class that use them. ...
      (microsoft.public.dotnet.faqs)
    • How to compile this?
      ... I would like to execute 'Algorithm 647' from the ACM Collected ... compile using the command: ... Suppose it is necessary to add the QSS ... one PROGRAM statement in the source file? ...
      (comp.lang.fortran)
    • Re: how to detect the compile is 32 bits or 64 bits?
      ... determined by whether you have a 32- or 64-bit platform. ... Suppose I have an algorithm, such as a cryptography algorithm, that ... but the chunk size differs for the two cases. ... available at compile time increases compiler optimization opportunities ...
      (comp.lang.c)
    • Re: Simple Algorithm
      ... Once you have the algorithm, ... int main ... compile, link it and let it run. ... Also think about ways to verify that the program is ...
      (comp.lang.cpp)