+1 on all points. Having a small, base-level support for various 
cryptographic functions is essential. A few packages also make it easier 
to scope for applications (instead of having to pick from two dozen 
packages). It will also help the code to be maintained since there will 
be more stakeholders.

Cheers,
   - Andreas

On 5/12/2011 1:32, Ron Teitelbaum wrote:
> Hi All,
>
> I think that works.  The basic separation from core and extra functionality
> is a good move.  3 packages is better than dozens.  I know that Andreas also
> made a SqueakSSL repository which is specifically for TLS/SSL.  That
> certainly works since it will get used there and fixed but it is also likely
> that SSL will bit rot here if everyone is focused there.  It might make
> sense to move our SSL and cert stuff to Andreas' repository (if there is
> anything still here that is needed by developers that doesn't exist there
> and Andreas wants it, or include his package here with the rest)  and focus
> on Core functions here?
>
> In general cleaning things up so that what we have posted works is a good
> idea.  If we can get things loaded by default, and have other things
> loadable in small understandable packages, then that works for me too.
>
> Other thoughts?
>
> Ron Teitelbaum
>
>> -----Original Message-----
>> From: squeak-dev-bounces at lists.squeakfoundation.org [mailto:squeak-
>> dev-bounces at lists.squeakfoundation.org] On Behalf Of Levente Uzonyi
>> Sent: Wednesday, May 11, 2011 5:49 PM
>> To: The general-purpose Squeak developers list
>> Subject: MD5 for Squeak (was: Re: [squeak-dev] Re: Some question
>> regarding portability)
>>
>> There was a plan to add the whole Cryptography package (split to three
>> packages) to the Trunk. Some older versions are waiting in the Inbox (see
>> CryptoCore, CryptoCerts and CryptoExtras). IIRC this process is stalled
>> because the proper renaming of the packages didn't happen (Cryptography
>> instead of Crypto). If the renaming is done, then Squeak will have a
> working
>> MD5 implementation out of the box.
>>
>> Another solution is to grab the MD5 implementation from WebClient (which
>> is probably the same as in Croquet, since it uses the CroquetPlugin if
>> available).
>>
>> What do you think?
>>
>>
>> Levente
>
>
>
>