On Wed, Sep 22, 2010 at 10:44 AM, Rob Withers reefedjib@gmail.com wrote:
Thanks for this, Denis. I will add it to the CryptoCore package tonight, after work.
Hey Rob? I have been meaning to reach out to you about "Crypto" and Squeak 4.2 integration. The Cryptography package has a long history and I am really averse to throwing all of that MC history out the window. I also cannot stand the slang name, "Crypto". May we _please_ re-integrate what you did for "Crypto" to the last MC version of the original package, "Cryptography"? That way we can preserve all of the history.
Second issue: So we now have SHA1, for exmaple, in three different packages. "Cryptography", "Crypto", and "System" (as SecureHashAlgorithm). Nicolas made some updates to the some of the other in-image cryptography-related classes just recently, and so those probably need to be folded into "Cryptography" as well.
- Chris
Hey Chris,
I am interested in seeing Cryptography make it into the Trunk. The idea put forth by Andreas, I believe, was to separate Core algorithms from Certificates. The work Denis and myself did these past two days builds dependencies between them (ASN1Stream support and PrivateKeyReader support). If we continue to split them, I will move ASN1 and the reader to Core.
First issue: naming. I really don't care which way we go. Someone tell me what name to give the packages. I think this is a conversation you and Andreas should have.
Second issue: To preserve the history, I believe the following must take place: a) don't split core and Certificates, b) copy the entire chain of Cryptography versions into the Trunk repository, effectively downgrading the Cryptography repository to holding 1) plugin code package, 2) SSH, 3) SSL, 4) SMIME, 5) other stuff. If we do split Certs from Core, and want to preserve history, we will need to remove Certificates from Cryptography and copy the Cryptography chain of versions to the Trunk repository. Personally, I would like to see both Core and Certificates in the Trunk, as it is not clear where to get Certificates otherwise. This would preserve the package Cryptography and we could move the history. Someone make a decision as to what goes into the Trunk and let me know. If you decide what should go then I would like immediate action so it doesn’t sit in the Inbox for months.
Third issue: I am unaware of the changes he has made. If you can provide me a changeset or mcz of his changes, I will integrate them into both Cryptography and Crypto.
Cheers, Rob
-------------------------------------------------- From: "Chris Muller" asqueaker@gmail.com Sent: Wednesday, September 22, 2010 12:51 PM To: "cryptography-list" cryptography@lists.squeakfoundation.org Subject: [Cryptography Team] Re: [squeak-dev] Crypto RSAWithSHA1 sign
On Wed, Sep 22, 2010 at 10:44 AM, Rob Withers reefedjib@gmail.com wrote:
Thanks for this, Denis. I will add it to the CryptoCore package tonight, after work.
Hey Rob? I have been meaning to reach out to you about "Crypto" and Squeak 4.2 integration. The Cryptography package has a long history and I am really averse to throwing all of that MC history out the window. I also cannot stand the slang name, "Crypto". May we _please_ re-integrate what you did for "Crypto" to the last MC version of the original package, "Cryptography"? That way we can preserve all of the history.
Second issue: So we now have SHA1, for exmaple, in three different packages. "Cryptography", "Crypto", and "System" (as SecureHashAlgorithm). Nicolas made some updates to the some of the other in-image cryptography-related classes just recently, and so those probably need to be folded into "Cryptography" as well.
- Chris
Cryptography mailing list Cryptography@lists.squeakfoundation.org http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/cryptography
cryptography@lists.squeakfoundation.org