[PYTHON-CRYPTO] Requirements

[Jeremy Hylton]

>>>>> "MS" == Michael  Ströder <michael at STROEDER.COM>> writes:

  MS> Dan Parisien wrote:
  >>
  >> > >   # MD5 implementations
  >> > >   '(0 2 262 1 10 1 3 2)' : [
  >> > >     Python.hash.MD5,
  >> > >   ],
  >> > >
  >> > >   # SHA1 implementations
  >> > >   '(1 3 14 3 2 26)' : [
  >> > >     Python.hash.SHA1,
  >> > >   ],
  >> > >
  >> > >   # Asymmetric ciphers
  >> > >
  >> > >   # RSA implementations
  >> > >   '(2 5 8 1 1)' : [ ],
  [...]
  >> > > - Is anybody scared by OIDs at all? Do all required
  >> > >   components
  >> > > (algorithms, prng, key stores, protocols) have OIDs assigned?
  >> > > (Likely not.)
  >> >
  >> > I am.  I'd rather go with aliases than with OIDs.  Other
  >> > opinions?
  >>
  >> Agreed. Aliases are better, but we are going to run into the
  >> problem of having to document them to solve 'rijndael' / 'aes'...

  MS> No problem to add additional support for aliases. But the
  MS> registry itself should be OID-based. If the registry is based on
  MS> aliases we have to maintain a name space.

OIDs make sense to me, though I'd rather not see them as Python
strings.  Rather, something like OID(2, 5, 8, 1, 1).  

SPKI provides a module with a bunch of standard OIDs already defined,
which can be used as aliases.

algid.py:
    oid_dsa = asn1.OID((1, 2, 840, 10040, 4, 1))
    oid_dsa_sha1 = asn1.OID((1, 2, 840, 10040, 4, 3))
    oid_md5 = asn1.OID((1, 2, 840, 113549, 2, 5))

usercode:
    algid.oid_md5

Jeremy