« Return to Thread: RFC: Consolidating the Cryptography library for a general release
Re: RFC: Consolidating the Cryptography library for a general release
by Rob Withers
::
Rate this Message:
Hi Philippe,
I hadn't realized that Configurations had been fixed in 3.9. They
were broken badly in 3.8. This would certainly be a solution to load
the various Crypto packages, and it would have the advantage of
allowing people to load a smaller subset for constrained devices.
I'll take you up on you offer to build a Configuration file for us.
Is it possible to nest one configuration inside of another? If I
build a SSL configuration, I would want to load the Cryptography
configuration with it. O is this what Universes will deliver to us.
Slightly confused.
Here is my in-order list of packages for the Cryptography Configuration:
Cryptography-Core
Cryptography-ARC2
Cryptography-RC4
Cryptography-MD4
Cryptography-MD5
Cryptography-SHA1
Cryptography-SHA256
Cryptography-DES
Cryptography-DSA
Cryptography-RSA
Cryptography-ElGamal
Cryptography-Rijndael
Cryptography-RandomAndPrime
Cryptography-ASN1
Cryptography-X509
Cryptography-PKCS12
Cryptography-Tests
cheers,
Rob
On Apr 21, 2007, at 8:55 AM, Philippe Marschall wrote:
> 2007/4/21, Robert Withers <reefedjib@...>:
>> This is a request for comment on consolidating the Cryptography
>> library for a general release. What I mean by that is consolidating
>> to a single Monticello package, that would allow users to one-click
>> load the basic library. Currently there is an implicit load order
>> which most users don't know. We still don't have Configuration
>> support so that isn't a solution right now.
>
> What's the problem there? If you can load it with Monticello it should
> be no problem to have a Configuration Map for it. I could even build
> you one. Just tell me what you want in and in which order.
>
> Cheers
> Philippe
>
>> If this idea is supported, I suggest we look at all the packages and
>> decide which are "in", then generate the Cryptography package with
>> these packages loaded.
>>
>> Those packages that are not included, like Cryptography-SMIME for
>> instance, should really be renamed to not have the Cryptography-
>> prefix. The old versions can be deleted to keep things clean.
>>
>> Those packages that are selected, and are determined to be complete,
>> could be deleted as independent packages and we would just rely on
>> them being in the consolidated package and develop there when
>> needed. After this first step is completed, we could reassign the
>> classes to a more compact categorization.
>>
>> Below is a list of the packages. Please vote and if your vote is
>> yes, what are your package recommendations as described below.
>>
>> Rob
>>
>> Packages:
>> Those with a '*' in front are my suggestions as to which is to be
>> included in Cryptography. Those with a '!' in front are my
>> suggestions as to which should be renamed away from Cryptography-.
>> Those with a '+++' are candidates for deletion, since they have been
>> superseded.
>>
>> * Cryptography-ARC2
>> * Cryptography-ASN1
>> * Cryptography-Core
>> * Cryptography-DES
>> * Cryptography-DSA
>> * Cryptography-ElGamal
>> * Cryptography-MD4
>> * Cryptography-MD5
>> * Cryptography-PKCS12
>> * Cryptography-RC4
>> * Cryptography-RSA
>> * Cryptography-RandomAndPrime
>> * Cryptography-Rijndael
>> * Cryptography-SHA1
>> * Cryptography-SHA256
>> ! Cryptography-SMIME
>> ! Cryptography-SSL
>> * Cryptography-Tests
>> * Cryptography-X509
>> +++Fortuna (this exists in RandomAndPrime)
>> ! Cryptography-MSCerts
>> +++Cryptography-TLS (this is superseded by SSL)
>> OpenPGP
>>
>> _______________________________________________
>> Cryptography mailing list
>> Cryptography@...
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/
>> cryptography
>>
> _______________________________________________
> Cryptography mailing list
> Cryptography@...
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/
> cryptography
_______________________________________________
Cryptography mailing list
Cryptography@...
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/cryptography
I hadn't realized that Configurations had been fixed in 3.9. They
were broken badly in 3.8. This would certainly be a solution to load
the various Crypto packages, and it would have the advantage of
allowing people to load a smaller subset for constrained devices.
I'll take you up on you offer to build a Configuration file for us.
Is it possible to nest one configuration inside of another? If I
build a SSL configuration, I would want to load the Cryptography
configuration with it. O is this what Universes will deliver to us.
Slightly confused.
Here is my in-order list of packages for the Cryptography Configuration:
Cryptography-Core
Cryptography-ARC2
Cryptography-RC4
Cryptography-MD4
Cryptography-MD5
Cryptography-SHA1
Cryptography-SHA256
Cryptography-DES
Cryptography-DSA
Cryptography-RSA
Cryptography-ElGamal
Cryptography-Rijndael
Cryptography-RandomAndPrime
Cryptography-ASN1
Cryptography-X509
Cryptography-PKCS12
Cryptography-Tests
cheers,
Rob
On Apr 21, 2007, at 8:55 AM, Philippe Marschall wrote:
> 2007/4/21, Robert Withers <reefedjib@...>:
>> This is a request for comment on consolidating the Cryptography
>> library for a general release. What I mean by that is consolidating
>> to a single Monticello package, that would allow users to one-click
>> load the basic library. Currently there is an implicit load order
>> which most users don't know. We still don't have Configuration
>> support so that isn't a solution right now.
>
> What's the problem there? If you can load it with Monticello it should
> be no problem to have a Configuration Map for it. I could even build
> you one. Just tell me what you want in and in which order.
>
> Cheers
> Philippe
>
>> If this idea is supported, I suggest we look at all the packages and
>> decide which are "in", then generate the Cryptography package with
>> these packages loaded.
>>
>> Those packages that are not included, like Cryptography-SMIME for
>> instance, should really be renamed to not have the Cryptography-
>> prefix. The old versions can be deleted to keep things clean.
>>
>> Those packages that are selected, and are determined to be complete,
>> could be deleted as independent packages and we would just rely on
>> them being in the consolidated package and develop there when
>> needed. After this first step is completed, we could reassign the
>> classes to a more compact categorization.
>>
>> Below is a list of the packages. Please vote and if your vote is
>> yes, what are your package recommendations as described below.
>>
>> Rob
>>
>> Packages:
>> Those with a '*' in front are my suggestions as to which is to be
>> included in Cryptography. Those with a '!' in front are my
>> suggestions as to which should be renamed away from Cryptography-.
>> Those with a '+++' are candidates for deletion, since they have been
>> superseded.
>>
>> * Cryptography-ARC2
>> * Cryptography-ASN1
>> * Cryptography-Core
>> * Cryptography-DES
>> * Cryptography-DSA
>> * Cryptography-ElGamal
>> * Cryptography-MD4
>> * Cryptography-MD5
>> * Cryptography-PKCS12
>> * Cryptography-RC4
>> * Cryptography-RSA
>> * Cryptography-RandomAndPrime
>> * Cryptography-Rijndael
>> * Cryptography-SHA1
>> * Cryptography-SHA256
>> ! Cryptography-SMIME
>> ! Cryptography-SSL
>> * Cryptography-Tests
>> * Cryptography-X509
>> +++Fortuna (this exists in RandomAndPrime)
>> ! Cryptography-MSCerts
>> +++Cryptography-TLS (this is superseded by SSL)
>> OpenPGP
>>
>> _______________________________________________
>> Cryptography mailing list
>> Cryptography@...
>> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/
>> cryptography
>>
> _______________________________________________
> Cryptography mailing list
> Cryptography@...
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/
> cryptography
_______________________________________________
Cryptography mailing list
Cryptography@...
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/cryptography
smime.p7s (3K) « Return to Thread: RFC: Consolidating the Cryptography library for a general release
| Free Forum Powered by Nabble | Forum Help |