[Cryptography Team] Initial package factoring complete (was: Re: some more repository things)

Chris Muller chris at funkyobjects.org
Mon Oct 24 18:40:57 CEST 2005


> > Are you sure this is a safe thing to do?  My understanding is Monticello
> treats
> > the two-part category names as:
> >
> >   PackageName-Category name
> >
> Not if you start adding packages that are named 'Package-Name' ;)

>From this I gather your answer is "yes" this is what you want to do.  I suppose
you have a lot more confidence in the tools than I do.  I think we will get bit
by this someday, but I have nevertheless done what you want.  We now have all
separate algorithm packages.  However, I decided against Monticello prereqs;
one change to Base and you suddenly have to resave *eleven* packages, and we
all know how buggy prereqs are.  But I'll go any direction the team wants to on
this..

I follwed hmm's lead on removing ASN1Constants pool dictionary, it was causing
a load warning, but not sure whether it was needed or not.  I know nothing
about ASN1.  Further, I noticed some of the base-class extensions named
"decodeAsn1Der" were also used by DSA.  Therefore, ALL ASN1 extensions are in
the CryptographyBase package.  Someone who knows about ASN1 should clean this
up.

Remember, you need to load CryptographBase-cmm.3.mcz, NOT version 5.  Also,
Cryptography-Support is not needed.

After you load Base.3, then load each algorithm-specific package and, finally,
the Tests package.  15 of 18 of the tests pass, just as if I load Cryptography
0.3 from SqueakMap.

 - Chris


More information about the Cryptography mailing list