[PYTHON-CRYPTO] not pseudo code anymore!

PC Drew drewpc at COLORADO.EDU
Tue Feb 13 16:27:13 CET 2001


Quoting Bryan Mongeau <bryan at EEVOLVED.COM>:

> On Monday 12 February 2001 23:43, you wrote:
> > I took Dan's pseudo code and turned it into python code.  Let me know
> what
> > I did wrong and what should be changed.  Sometime tomorrow I'll also
> write
> > up the goals and post it on the same site.
> >
>
> Excellent initiative! Looks tight + nice doc strings! :)
>
> Only two small issues got caught in my brain sieve, pertaining to
> AsymmetricBase:
>
> 1 - __init__,encrypt and decrypt all accept an "_algorithm" parameter.
> This
> is somewhat confusing to me. If child classes inherit from
> AsymmetricBase,
> aren't they necessarily implementing an algorithm? Would child classes
> always
> set "_algorithm" to their algorithm? If so, isn't that redundant?
>

Yeah, for some reason I got it stuck in my head that this is where we'd need
that, but we won't need it until we get a little higher up.  For instance, when
you ssh somewhere the RSA stuff just encrypts your symmetric session key.  Your
actual session is encrypted using IDEA or Blowfish or something.  I'm
dumb...I've changed it and uploaded the changes.

> 2- sign and verify. It would seems that these methods could actually use
> an
> "_algorithm"  parameter due to the fact that signing and verification
> can be
> conducted many ways using a given keypair. Examples: DSA, Nyberg-Ruppel
> and
> Massy-Omura. Oh, and the verify docstring needs to be changed
> (copy/paste
> from sign method? :)
>

fixed that too :)


> Regards,
> --
> <==================================>
> Bryan Mongeau
> Lead Developer, Director
> eEvolved Real-Time Technologies Inc.
> http://www.eevolved.com
> <==================================>
>
> "Imagination is more important than knowledge."-- Einstein
>



--
PC Drew





More information about the python-crypto mailing list