[PYTHON-CRYPTO] Requirements

[PC Drew]

--On Friday, February 16, 2001 10:29 AM +0100 Michael Ströder <michael at STROEDER.COM> wrote:

> PC Drew wrote:
>>
>> > If new implementation modules are installed the system administrator
>> > has to manually tweak this registry. One could imagine that new
>> > implementation modules register themselves by appending their class
>> > names to the lists of algorithms they implement. (Note: Using
>> > .append() as default installation method means add to *end of list*
>> > => lowest priority!)
>>
>> This really scares me.  The idea of having other people install their
>> code into our module without us knowing it.  What I'd rather do is have
>> people submit their implementation to us and have us integrate it into
>> the overall package.
>
> 1. I'm not keen on maintaining a crypto lib.
> 2. The idea behind the dynamic crypto API is to enable people to
> integrate their implementations without getting other people
> involved at all.
>
> Ciao, Michael.

I agree with #2, but disagree with #1.  Here's how I see it: we create a kick ass API that allows for all kinds of crypto implementation in an easy, 
well thought out manner.  That's part 1.  Part 2 is actually implimenting that.  I'd like to see this API go one step further: to actually have a big 
module to download that would have all of this functionality in it.  Maybe that's a seperate topic and seperate task, but that's what I'd like to do once we establish the API.

Anyone else interested?

--
PC Drew

  Be nice or I'll replace you with a very
  small shell script.