Cryptography

cryptography@lists.squeakfoundation.org

364 discussions

Re: [Cryptography Team] [Vm-dev] Smalltalk code calling SHA2Plugin
by Chris Muller 21 Jul '20

21 Jul '20

Hi Levente, > > HashFunction newSHA256 > > > > instead of > > > > SHA256 new > > > > in order to take advantage of Levente's plugin. > > That is indeed some sort of a change but it only affects those who > compiled the SHA256Plugin themselves since that plugin wasn't shipped with > the VM. Ah, you're speaking about legacy code. I really hope we can include your plugin in future VM's. Are Eliot, *et al*, on board? > I decided against the practice of making #new return an instance of > another class than the receiver, as it was with the previous > implementation, because that makes it a lot harder for others to > understand the code. Hm. I sort of agree, although I guess *Factory* is a recognized pattern. To me, the issue is that writing "SHA256 new" , is a perfectly intuitive and obvious way to use it, but sticking out like a sore thumb as a *subversively-wrong-way* to-use-it. It'd be better if it threw an error, and even better than that if it just worked. I know you care about the *quantity* of methods in the image (as do I), how about *quality*? Can SHA256 #new be improved by doing essentially what HashFunction #newSHA256 does, and simply sending some alternative to new (i.e., basicNew initialize) to avoid the recursion? Above, you mentioned you decided against the practice, does that mean you're writing: SHA256 newSHA256 ? If not, how did you do it? Thanks again for this great work. - Chris On Sun, Jul 19, 2020 at 9:55 PM Levente Uzonyi <leves(a)caesar.elte.hu> wrote: > Hi Chris, > > On Sun, 19 Jul 2020, Chris Muller wrote: > > > Hi Robert and Levente, > > > > Yes, I *think* so! I'm just now getting up to speed after reading > > that epic thread between you and Levente (subject line: "SHA512 squeak > > implementation"). Thanks a ton to both of you, BTW, for this work! > > > > After loading > > > > ProCrypto-1-1-1 > > and ProCryptoTests-1-1-1, > > > > all 205 tests are passing, however, it took me a bit to realize I need > to use > > > > HashFunction newSHA256 > > > > instead of > > > > SHA256 new > > > > in order to take advantage of Levente's plugin. This is great, thanks > again! > > That is indeed some sort of a change but it only affects those who > compiled the SHA256Plugin themselves since that plugin wasn't shipped with > the VM. > I decided against the practice of making #new return an instance of > another class than the receiver, as it was with the previous > implementation, because that makes it a lot harder for others to > understand the code. > > > > > Quick side question: Is it okay to reuse a SHA256 instance, or should > > I just create a new one for each and every message to hash? > > All subinstances of HashFunction are reusable. The tests > (see HashFunctionTest) do exactly that. > > > Levente > > > > > Best, > > Chris > > > > > > On Sat, Jul 18, 2020 at 6:02 AM Robert Withers <robert.withers(a)pm.me> > wrote: > >> > >> Hey Chris, > >> > >> Did this approach fix your issues? > >> > >> Kindly, > >> rabbit > >> > >> On 7/13/20 11:46 PM, Robert wrote: > >> > >> Hi Chris, > >> > >> You should only need to run #3, which will load Registers. Hasher was > from before we integrated the code into ProCrypto-1-1-1. > >> > >> Installer as project: ‘Cryptography’; install: ‘ProCrypto-1-1-1’. > >> > >> Then to load tests run: > >> > >> Installer as project: ‘Cryptography’; install: ‘ProCryptoTests-1-1-1’. > >> > >> Let us know if any tests fail and we can look into it. > >> > >> Kindly, > >> Robert > >> > >> > >> On Mon, Jul 13, 2020 at 19:52, Chris Muller <asqueaker(a)gmail.com> > wrote: > >> > >> Hi Robert, hi Levente, > >> > >> I would like to utilize the latest crypto in my next project, would > >> you help me with the current proper way to configure my image, and my > >> vm with plugins? > >> > >> (image) > >> In going back through some recent messages on the mailing lists and > >> instructions on squeaksource.com, I came across these incantations as > >> current ways to load the image code: > >> > >> 1) Installer ss > >> project: 'Registers'; > >> install: 'Registers'; > >> project: 'Hasher'; > >> install: 'HAHasher-Core'; > >> install: 'HAHasher-Tests'. > >> > >> 2) Installer ss > >> project: 'Registers'; > >> install: 'Registers'; > >> project: 'Hasher'; > >> install: 'HAHasher'. > >> > >> 3) Installer ss project: 'Cryptography'; install: 'ProCrypto-1-1-1'. > >> > >> I like these one-click-for-everything scripts for crypto -- it > >> satisfies the good use-case of development and education, and also > >> knowing all what's available to Squeak in one glance. My app's build > >> script can cherry pick what it needs, but any advice on which starting > >> point above or otherwise is appreciated. > >> > >> (vm) > >> I put the SHA2Plugin.so from Roberts dropbox in the lib directory, > >> and it shows up as a "Loaded VM Module" in About Squeak. But, three > >> of the "WithPluginTest"'s are failing. My OS is linux_x64. I don't > >> know how to build Squeak or plugins from sources, but including it in > >> the standard precompiled vm would be so pertinent for Squeak today, > >> IMO. SHA256 is one of the ones I'm going to need, so would be nice to > >> have it work via plugin. I assume it's a lot faster? > >> > >> Thanks, > >> Chris > >> > >> On Tue, Mar 10, 2020 at 3:52 PM Levente Uzonyi <leves(a)caesar.elte.hu> > wrote: > >>> > >>> > >>> Hi Robert, > >>> > >>> With yesterday's help from Eliot and Nicolas, the SHA2Plugin is ready: > >>> http://squeaksource.com/Cryptography/CryptographyPlugins-ul.19.mcz > >>> The updated version of the image-side code is available in the Hasher > >>> repository. You can install it with: > >>> > >>> Installer ss > >>> project: 'Registers'; > >>> install: 'Registers'; > >>> project: 'Hasher'; > >>> install: 'HAHasher-Core'; > >>> install: 'HAHasher-Tests'. > >>> > >>> > >>> Levente > >>> > >>> > >>> On Tue, 10 Mar 2020, Levente Uzonyi wrote: > >>> > >>>> > >>>> Hi Robert, > >>>> > >>>> Please have a look at: > >>>> > http://lists.squeakfoundation.org/pipermail/squeak-dev/2020-March/207851.ht… > >>>> It answers all your questions. > >>>> > >>>> > >>>> Levente > >>>> > >>>> On Tue, 10 Mar 2020, Robert wrote: > >>>> > >>>>> Hi Levente, > >>>>> > >>>>> I got the SHA2Plugin built and deployed to my Crypto plugins folder. > Now I > >>>> am trying to figure out how to call it from SHA512. > >>>>> > >>>>> > https://www.dropbox.com/sh/yhv253rwrhq0q5p/AAB7PKP2KPiGpDnIyule2h_Ia?dl=0 > >>>>> > >>>>> [plugin] I looked at it and please understand I think the classes > you wrote > >>>> and the framework is really quite nice. I am thrilled we found > SHA512! It's > >>>> impressive that your one plugin can handle a number of hash functions! > >>>>> Now all I need is to find the code that calls the SHA2Plugin. > Levente, > >>>> would you share that code, please? > >>>>> > >>>>> Kindly, > >>>>> Robert > >>>>> > >>>>> > >>>> > >> > >> > >> > >

1 0

Re: [Cryptography Team] [Vm-dev] Smalltalk code calling SHA2Plugin
by Chris Muller 20 Jul '20

20 Jul '20

Hi Robert, hi Levente, I would like to utilize the latest crypto in my next project, would you help me with the current proper way to configure my image, and my vm with plugins? (image) In going back through some recent messages on the mailing lists and instructions on squeaksource.com, I came across these incantations as current ways to load the image code: 1) Installer ss project: 'Registers'; install: 'Registers'; project: 'Hasher'; install: 'HAHasher-Core'; install: 'HAHasher-Tests'. 2) Installer ss project: 'Registers'; install: 'Registers'; project: 'Hasher'; install: 'HAHasher'. 3) Installer ss project: 'Cryptography'; install: 'ProCrypto-1-1-1'. I like these one-click-for-everything scripts for crypto -- it satisfies the good use-case of development and education, and also knowing all what's available to Squeak in one glance. My app's build script can cherry pick what it needs, but any advice on which starting point above or otherwise is appreciated. (vm) I put the SHA2Plugin.so from Roberts dropbox in the lib directory, and it shows up as a "Loaded VM Module" in About Squeak. But, three of the "WithPluginTest"'s are failing. My OS is linux_x64. I don't know how to build Squeak or plugins from sources, but including it in the standard precompiled vm would be so pertinent for Squeak today, IMO. SHA256 is one of the ones I'm going to need, so would be nice to have it work via plugin. I assume it's a lot faster? Thanks, Chris On Tue, Mar 10, 2020 at 3:52 PM Levente Uzonyi <leves(a)caesar.elte.hu> wrote: > > > Hi Robert, > > With yesterday's help from Eliot and Nicolas, the SHA2Plugin is ready: > http://squeaksource.com/Cryptography/CryptographyPlugins-ul.19.mcz > The updated version of the image-side code is available in the Hasher > repository. You can install it with: > > Installer ss > project: 'Registers'; > install: 'Registers'; > project: 'Hasher'; > install: 'HAHasher-Core'; > install: 'HAHasher-Tests'. > > > Levente > > > On Tue, 10 Mar 2020, Levente Uzonyi wrote: > > > > > Hi Robert, > > > > Please have a look at: > > http://lists.squeakfoundation.org/pipermail/squeak-dev/2020-March/207851.ht… > > It answers all your questions. > > > > > > Levente > > > > On Tue, 10 Mar 2020, Robert wrote: > > > >> Hi Levente, > >> > >> I got the SHA2Plugin built and deployed to my Crypto plugins folder. Now I > > am trying to figure out how to call it from SHA512. > >> > >> https://www.dropbox.com/sh/yhv253rwrhq0q5p/AAB7PKP2KPiGpDnIyule2h_Ia?dl=0 > >> > >> [plugin] I looked at it and please understand I think the classes you wrote > > and the framework is really quite nice. I am thrilled we found SHA512! It's > > impressive that your one plugin can handle a number of hash functions! > >> Now all I need is to find the code that calls the SHA2Plugin. Levente, > > would you share that code, please? > >> > >> Kindly, > >> Robert > >> > >> > >

4 3

heads up, working on ASN1
by Robert Withers 26 Jun '20

26 Jun '20

Hey everyone! I hope y'all are all well as can be! I just wanted to float you a heads up that I am mucking about in ASN1, trying to use it as the encoding for PromisesRemote. In the process, I broke it. Looking at finding out the asn1 type for an ASN1WrapperConstructedType... Kindly, Rabbit

1 0

Re: [Cryptography Team] [squeak-dev] Undeclared 'nanos' in Cryptology extension to DateAndTime
by Robert Withers 29 May '20

29 May '20

Hey Ron, since you spent serious time in making our Cryptography project an official Crypto site, is there any possibility/usefulness in reporting this violation to the organization you achieved our legitimacy from? As the code has been ripped out and republished elsewhere, beyond our controls. K, r On 5/28/20 9:37 PM, Robert Withers wrote: > > On 5/28/20 7:40 PM, Levente Uzonyi wrote: >> On Thu, 28 May 2020, tim Rowledge wrote: >> >>>> On 2020-05-28, at 4:04 PM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: >>>> >>>> Uhh. Hmmm. Which version of that Blowfish code are you using? >>> The version included in the cryptology package on squeaksource, within the Cryptology-Ciphers package. Ron mentioned recently that we have to be very careful about where this stuff gets published. >>> >>> >>>> I think his version is here: >>>> http://www.smalltalkhub.com/#!/~Cryptography/Cryptography >>> Seems to be a more or less innaccessible site these days? I haven't been able to get to it in ages. >> It was announced to be shut down and replaced with a static site[1], but >> only on the Pharo list because who cares about other users. > How unfortunate. I wanted to comment on the insular nature of their > larceny. Cryptography can only be published in the squeak source > repository. A lot of work went into it. Add it to the list... > > K, r > >> I suppose the migration[2] was not successful. The website complains about >> jquery not being loaded. >> Anyway, with some url mangling, the listing is available here: >> http://www.smalltalkhub.com/mc/Cryptography/Cryptography/main >> >> >> Levente >> [1] http://forum.world.st/ANN-SmalltalkHub-Deprecation-Notice-td5114407.html >> [2] http://forum.world.st/ANN-Smalltalkhub-Readonly-Migration-tuesday-8hs-serve… >> >>> tim >>> -- >>> tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim >>> Hardware: The parts of a computer system that can be kicked.

2 3

Re: [Cryptography Team] Multi-Image Sista VM?
by Robert 29 Apr '20

29 Apr '20

I was thinking they’d Run Concurrently, of course. #SVS!!! K, r Sent from ProtonMail Mobile On Wed, Apr 29, 2020 at 14:43, Robert <robert.withers(a)pm.me> wrote: > I have not read about this anywhere I can remember. Would it be possible to run two images on one VM? > > Preggo, > > Robertotini > > Sent from ProtonMail Mobile

1 0

Re: [Cryptography Team] [Vm-dev] How to create headless VM without some primitives?
by Robert 29 Apr '20

29 Apr '20

It’s Right in the middle! Klaarrung? Sent from ProtonMail Mobile On Wed, Apr 29, 2020 at 14:36, Robert <robert.withers(a)pm.me> wrote: > Are you saying that I can can run my 64-bit Squeak.image running PTAPAS [1] on the Pharo headless VM?!?!?! Now that, my Ladies and Gentlemen, would constitute a profound shout-out to the Heritage [2]. Hey, goddammit, don’t you forget your Heritage!!! You gained a profound VM for Pharo [3]! Do you feel me? > > [1] PTAPAS - https://squeak.slack.com/archives/C02LC8AMS/p1587255601170900 > [2] Squeak - https://Squeak.org > [3] Cog Spur 64-bit Sista Multi, Malto, hi to hair, dost PI wisson calculiert, Schnell, Vielen Schnell!!! > > Vas ist deinem mackht Los Corison Stein, meinen Schatchzie? Do you feel me, now? > > ^,^ > > Sent from ProtonMail Mobile > > On Wed, Apr 29, 2020 at 13:57, Ben Coman <btc(a)openinworld.com> wrote: > >> On Tue, 14 Apr 2020 at 10:43, tim Rowledge <tim(a)rowledge.org> wrote: >> >>> >>> a) it's way past time we stopped opening a windows when it isn't needed. No window should be created until and unless the system actually writes to the display and calls for a display update. This would enable image-controlled headlessness. RISC OS was able to cope with it 25 years ago. >> >> Pharo is doing that, in their branch https://github.com/pharo-project/opensmalltalk-vm/tree/headless >> which IIUC is the branch being used to build all Pharo VM going forward. Once they've worked the bugs out of it, >> it might be worth pulling that back to evaluate for Squeak to use. >> >> cheers -ben

1 0

Re: [Cryptography Team] DoubleWordArray broken in Pharo
by Robert 28 Mar '20

28 Mar '20

I just rolled it all back. hashing-rww.24 and HashingTests-rww.2 are once again the latest versions. k, r On 3/28/20 12:14 PM, Levente Uzonyi wrote: > Hi Robert, > > Well, I just asked you not to do it. It's not worth it. > > > Levente > > On Sat, 28 Mar 2020, Robert wrote: > >> Hi Levente, >> >> Squeak... >> >> I went ahead and split off the plugin hashing code and loaded with and without in Squeak. #CryptoGreen. This loads it all. The specific versions for Squeak are below the Pharo section. Note: if you loaded the hashing plugins support then remove it the HashFunction class>>#newHash methods are ripped away by the >> plugin code. So if you load hashing plugins then remove it you will need to reload the CryptographyHashing package for green. >> >> Installer ss project: 'Cryptography'; install: 'ProCrypto-1-1-1'; install: 'ProCryptoTests-1-1-1'; install: 'SSLLoader'. >> >> Pharo... >> >> Here is a script to load all packages in Pharo, without Hashing plugins support. Unfortunately there are many errors: red and yellow. :( Crypto used to run on Pharo. Sad. >> >> Gofer new squeaksource: 'Registers'; package: 'Registers-Core'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyCore'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyHashing'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyASN1'; load. Gofer new >> squeaksource: 'Cryptography'; package: 'CryptographyRandom'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyCiphers'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographySignatures'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyKeyExchange'; load. Gofer >> new squeaksource: 'Cryptography'; package: 'CryptographyArchive'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyX509'; load. Gofer new squeaksource: 'Registers'; package: 'Registers-Tests'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyCoreTests'; load. Gofer new >> squeaksource: 'Cryptography'; package: 'CryptographyHashingTests'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyASN1Tests'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyRandomTests'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyCiphersTests'; >> load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographySignaturesTests'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyKeyExchangeTests'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyArchiveTests'; load. Gofer new squeaksource: 'Cryptography'; package: >> 'CryptographyX509Tests'; load. Gofer new squeaksource: 'Cryptography'; package: 'ThunkStack'; load. Gofer new squeaksource: 'Cryptography'; package: 'ParrotTalk'; load. >> >> Squeak versions... >> >> Here are the versions, in Squeak, without SSL: Installer ss project: 'Registers'; install: 'Registers-Core-ul.1'. Installer ss project: 'Cryptography'; install: 'CryptographyCore-ul.7'; install: 'CryptographyHashing-rww.26'; install: 'CryptographyHashingPluginSupport-rww.1'; install: >> 'CryptographyASN1-rww.7'; install: 'CryptographyRandom-ul.13'; install: 'CryptographyCiphers-rww.20'; install: 'CryptographySignatures-ul.17'; install: 'CryptographyKeyExchange-rww.14'; install: 'CryptographyArchive-ul.18'; install: 'CryptographyX509-ul.15'. Installer ss project: >> 'Registers'; install: 'Registers-Tests-ul.1'. Installer ss project: 'Cryptography'; install: 'CryptographyCoreTests-rww.1'; install: 'CryptographyHashingTests-rww.3'; install: 'CryptographyHashingPluginSupportTests-rww.1'; install: 'CryptographyASN1Tests-rww.1'; install: >> 'CryptographyRandomTests-rww.1'; install: 'CryptographyCiphersTests-rww.1'; install: 'CryptographySignaturesTests-rww.1'; install: 'CryptographyKeyExchangeTests-rww.1'; install: 'CryptographyArchiveTests-rww.1'; install: 'CryptographyX509Tests-rww.1'. Installer ss project: 'Cryptography'; >> install: 'ThunkStack-rww.12'; install: 'ParrotTalk-rww.48'. >> >> On 3/28/20 11:54 AM, Levente Uzonyi wrote: >> >> Hi Robert, >> >> Please don't mess up the code just because of Pharo. They'll eventually >> fix DoubleWordArray, but that doesn't mean the code will work at all on >> Pharo. >> >> Levente >> >> On Sat, 28 Mar 2020, Robert wrote: >> >> Hey Levente, >> >> In order to get Crypto running in Pharo, I will split the >> HashingPluginSupport code into a separate package, which Pharo will not >> load, but Squeak will. >> >> k, r >> >> On 3/28/20 10:26 AM, Robert wrote: >> >> On 3/28/20 10:16 AM, Levente Uzonyi wrote: >> >> Hi Robert, >> >> No, it's not a VM bug. My analysis I sent to you earlier is correct. It's >> that in Pharo DoubleWordArray is a variableWordSubclass instead of a >> variableDoubleWordSubclass. The latter is not available in Pharo. >> Here's the link to the issue they created based on my analysis you sent >> to them: https://github.com/pharo-project/pharo/issues/5956 >> >> Alright, I shared this analysis with Pharo's Discord channel. I must >> have missed the discussion of the #variableDoubleWordSubclass:. >> >> In theory, yes, it would be possible to rewrite SHA-512 and its related >> hash functions to avoid using DoubleWordArray, but I see no value in doing >> that. >> >> The value would be Crypto operational in Pharo. And all that follows >> from that (ParrotTalk, SSL, SSH, Signal, Raven). Is it possible for you >> to make these changes, please? I see this as more likely than Pharo >> accommodating #variableDoubleWordSubclass:. And other Smalltalks... >> >> k, r >> >> Pharo simply failed to properly integrate DoubleWordArray. It's there but >> it's disfunctional. Just wait until they fix it. >> >> >> Levente >> >> P.S.: This is pretty much off topic on squeak-dev. >> >> On Sat, 28 Mar 2020, Robert wrote: >> >> Hey Levente, >> >> I dug a little deeper into the Pharo issue with Cryptography and it IS a VM issue, I think. Primitive 61 is failing in DoubleWordArray>>#at:put:. Pharo seems totally uninterested in fixing this so I wanted to ask you, is there any way Cryptography can avoid reliance on DoubleWordArray? >> >> Kindly, >> Robert >> >> >> -- >> Kindly, >> Robert >> >> >> >> -- >> Kindly, >> Robert >> >> -- Kindly, Robert

1 0

Re: [Cryptography Team] DoubleWordArray broken in Pharo
by Robert 28 Mar '20

28 Mar '20

I had already done the work when I saw your post here. I may rewind. On 3/28/20 12:14 PM, Levente Uzonyi wrote: > Hi Robert, > > Well, I just asked you not to do it. It's not worth it. > > > Levente > > On Sat, 28 Mar 2020, Robert wrote: > >> Hi Levente, >> >> Squeak... >> >> I went ahead and split off the plugin hashing code and loaded with and without in Squeak. #CryptoGreen. This loads it all. The specific versions for Squeak are below the Pharo section. Note: if you loaded the hashing plugins support then remove it the HashFunction class>>#newHash methods are ripped away by the >> plugin code. So if you load hashing plugins then remove it you will need to reload the CryptographyHashing package for green. >> >> Installer ss project: 'Cryptography'; install: 'ProCrypto-1-1-1'; install: 'ProCryptoTests-1-1-1'; install: 'SSLLoader'. >> >> Pharo... >> >> Here is a script to load all packages in Pharo, without Hashing plugins support. Unfortunately there are many errors: red and yellow. :( Crypto used to run on Pharo. Sad. >> >> Gofer new squeaksource: 'Registers'; package: 'Registers-Core'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyCore'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyHashing'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyASN1'; load. Gofer new >> squeaksource: 'Cryptography'; package: 'CryptographyRandom'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyCiphers'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographySignatures'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyKeyExchange'; load. Gofer >> new squeaksource: 'Cryptography'; package: 'CryptographyArchive'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyX509'; load. Gofer new squeaksource: 'Registers'; package: 'Registers-Tests'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyCoreTests'; load. Gofer new >> squeaksource: 'Cryptography'; package: 'CryptographyHashingTests'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyASN1Tests'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyRandomTests'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyCiphersTests'; >> load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographySignaturesTests'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyKeyExchangeTests'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyArchiveTests'; load. Gofer new squeaksource: 'Cryptography'; package: >> 'CryptographyX509Tests'; load. Gofer new squeaksource: 'Cryptography'; package: 'ThunkStack'; load. Gofer new squeaksource: 'Cryptography'; package: 'ParrotTalk'; load. >> >> Squeak versions... >> >> Here are the versions, in Squeak, without SSL: Installer ss project: 'Registers'; install: 'Registers-Core-ul.1'. Installer ss project: 'Cryptography'; install: 'CryptographyCore-ul.7'; install: 'CryptographyHashing-rww.26'; install: 'CryptographyHashingPluginSupport-rww.1'; install: >> 'CryptographyASN1-rww.7'; install: 'CryptographyRandom-ul.13'; install: 'CryptographyCiphers-rww.20'; install: 'CryptographySignatures-ul.17'; install: 'CryptographyKeyExchange-rww.14'; install: 'CryptographyArchive-ul.18'; install: 'CryptographyX509-ul.15'. Installer ss project: >> 'Registers'; install: 'Registers-Tests-ul.1'. Installer ss project: 'Cryptography'; install: 'CryptographyCoreTests-rww.1'; install: 'CryptographyHashingTests-rww.3'; install: 'CryptographyHashingPluginSupportTests-rww.1'; install: 'CryptographyASN1Tests-rww.1'; install: >> 'CryptographyRandomTests-rww.1'; install: 'CryptographyCiphersTests-rww.1'; install: 'CryptographySignaturesTests-rww.1'; install: 'CryptographyKeyExchangeTests-rww.1'; install: 'CryptographyArchiveTests-rww.1'; install: 'CryptographyX509Tests-rww.1'. Installer ss project: 'Cryptography'; >> install: 'ThunkStack-rww.12'; install: 'ParrotTalk-rww.48'. >> >> On 3/28/20 11:54 AM, Levente Uzonyi wrote: >> >> Hi Robert, >> >> Please don't mess up the code just because of Pharo. They'll eventually >> fix DoubleWordArray, but that doesn't mean the code will work at all on >> Pharo. >> >> Levente >> >> On Sat, 28 Mar 2020, Robert wrote: >> >> Hey Levente, >> >> In order to get Crypto running in Pharo, I will split the >> HashingPluginSupport code into a separate package, which Pharo will not >> load, but Squeak will. >> >> k, r >> >> On 3/28/20 10:26 AM, Robert wrote: >> >> On 3/28/20 10:16 AM, Levente Uzonyi wrote: >> >> Hi Robert, >> >> No, it's not a VM bug. My analysis I sent to you earlier is correct. It's >> that in Pharo DoubleWordArray is a variableWordSubclass instead of a >> variableDoubleWordSubclass. The latter is not available in Pharo. >> Here's the link to the issue they created based on my analysis you sent >> to them: https://github.com/pharo-project/pharo/issues/5956 >> >> Alright, I shared this analysis with Pharo's Discord channel. I must >> have missed the discussion of the #variableDoubleWordSubclass:. >> >> In theory, yes, it would be possible to rewrite SHA-512 and its related >> hash functions to avoid using DoubleWordArray, but I see no value in doing >> that. >> >> The value would be Crypto operational in Pharo. And all that follows >> from that (ParrotTalk, SSL, SSH, Signal, Raven). Is it possible for you >> to make these changes, please? I see this as more likely than Pharo >> accommodating #variableDoubleWordSubclass:. And other Smalltalks... >> >> k, r >> >> Pharo simply failed to properly integrate DoubleWordArray. It's there but >> it's disfunctional. Just wait until they fix it. >> >> >> Levente >> >> P.S.: This is pretty much off topic on squeak-dev. >> >> On Sat, 28 Mar 2020, Robert wrote: >> >> Hey Levente, >> >> I dug a little deeper into the Pharo issue with Cryptography and it IS a VM issue, I think. Primitive 61 is failing in DoubleWordArray>>#at:put:. Pharo seems totally uninterested in fixing this so I wanted to ask you, is there any way Cryptography can avoid reliance on DoubleWordArray? >> >> Kindly, >> Robert >> >> >> -- >> Kindly, >> Robert >> >> >> >> -- >> Kindly, >> Robert >> >> -- Kindly, Robert

1 0

Re: [Cryptography Team] DoubleWordArray broken in Pharo
by Robert 28 Mar '20

28 Mar '20

Thanks, I'll try it out. On 3/28/20 12:12 PM, Levente Uzonyi wrote: > Hi Robert > > On Sat, 28 Mar 2020, Robert wrote: > >> On 3/28/20 10:16 AM, Levente Uzonyi wrote: >>> Hi Robert, >>> >>> No, it's not a VM bug. My analysis I sent to you earlier is correct. It's >>> that in Pharo DoubleWordArray is a variableWordSubclass instead of a >>> variableDoubleWordSubclass. The latter is not available in Pharo. >>> Here's the link to the issue they created based on my analysis you sent >>> to them: https://github.com/pharo-project/pharo/issues/5956 >> Alright, I shared this analysis with Pharo's Discord channel. I must >> have missed the discussion of the #variableDoubleWordSubclass:. >> >>> In theory, yes, it would be possible to rewrite SHA-512 and its related >>> hash functions to avoid using DoubleWordArray, but I see no value in doing >>> that. >> The value would be Crypto operational in Pharo. And all that follows > Fixing DoubleWordArray in Pharo alone won't make the packages operational. > Pharo is a moving target and it keeps breaking stuff all the time. > >> from that (ParrotTalk, SSL, SSH, Signal, Raven). Is it possible for you >> to make these changes, please? I see this as more likely than Pharo >> accommodating #variableDoubleWordSubclass:. And other Smalltalks... > I've attached a changeset. If you load it before the Cryptography > packages, CryptographyHashing will work in Pharo 8 and in the current > Pharo 9 alpha. Some tests will fail, because random strings are generated > with the Random class, which is different in Squeak and Pharo but still, > everything will work. > > > Levente > >> k, r >> >>> Pharo simply failed to properly integrate DoubleWordArray. It's there but >>> it's disfunctional. Just wait until they fix it. >>> >>> >>> Levente >>> >>> P.S.: This is pretty much off topic on squeak-dev. >>> >>> On Sat, 28 Mar 2020, Robert wrote: >>> >>>> Hey Levente, >>>> >>>> I dug a little deeper into the Pharo issue with Cryptography and it IS a VM issue, I think. Primitive 61 is failing in DoubleWordArray>>#at:put:. Pharo seems totally uninterested in fixing this so I wanted to ask you, is there any way Cryptography can avoid reliance on DoubleWordArray? >>>> >>>> Kindly, >>>> Robert >>>> >>>> >> -- >> Kindly, >> Robert >> >> > > -- Kindly, Robert

1 0

Re: [Cryptography Team] DoubleWordArray broken in Pharo
by Robert 28 Mar '20

28 Mar '20

Hi Levente, Squeak... I went ahead and split off the plugin hashing code and loaded with and without in Squeak. #CryptoGreen. This loads it all. The specific versions for Squeak are below the Pharo section. Note: if you loaded the hashing plugins support then remove it the HashFunction class>>#newHash methods are ripped away by the plugin code. So if you load hashing plugins then remove it you will need to reload the CryptographyHashing package for green. Installer ss project: 'Cryptography'; install: 'ProCrypto-1-1-1'; install: 'ProCryptoTests-1-1-1'; install: 'SSLLoader'. Pharo... Here is a script to load all packages in Pharo, without Hashing plugins support. Unfortunately there are many errors: red and yellow. :( Crypto used to run on Pharo. Sad. Gofer new squeaksource: 'Registers'; package: 'Registers-Core'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyCore'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyHashing'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyASN1'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyRandom'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyCiphers'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographySignatures'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyKeyExchange'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyArchive'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyX509'; load. Gofer new squeaksource: 'Registers'; package: 'Registers-Tests'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyCoreTests'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyHashingTests'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyASN1Tests'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyRandomTests'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyCiphersTests'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographySignaturesTests'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyKeyExchangeTests'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyArchiveTests'; load. Gofer new squeaksource: 'Cryptography'; package: 'CryptographyX509Tests'; load. Gofer new squeaksource: 'Cryptography'; package: 'ThunkStack'; load. Gofer new squeaksource: 'Cryptography'; package: 'ParrotTalk'; load. Squeak versions... Here are the versions, in Squeak, without SSL: Installer ss project: 'Registers'; install: 'Registers-Core-ul.1'. Installer ss project: 'Cryptography'; install: 'CryptographyCore-ul.7'; install: 'CryptographyHashing-rww.26'; install: 'CryptographyHashingPluginSupport-rww.1'; install: 'CryptographyASN1-rww.7'; install: 'CryptographyRandom-ul.13'; install: 'CryptographyCiphers-rww.20'; install: 'CryptographySignatures-ul.17'; install: 'CryptographyKeyExchange-rww.14'; install: 'CryptographyArchive-ul.18'; install: 'CryptographyX509-ul.15'. Installer ss project: 'Registers'; install: 'Registers-Tests-ul.1'. Installer ss project: 'Cryptography'; install: 'CryptographyCoreTests-rww.1'; install: 'CryptographyHashingTests-rww.3'; install: 'CryptographyHashingPluginSupportTests-rww.1'; install: 'CryptographyASN1Tests-rww.1'; install: 'CryptographyRandomTests-rww.1'; install: 'CryptographyCiphersTests-rww.1'; install: 'CryptographySignaturesTests-rww.1'; install: 'CryptographyKeyExchangeTests-rww.1'; install: 'CryptographyArchiveTests-rww.1'; install: 'CryptographyX509Tests-rww.1'. Installer ss project: 'Cryptography'; install: 'ThunkStack-rww.12'; install: 'ParrotTalk-rww.48'. On 3/28/20 11:54 AM, Levente Uzonyi wrote: > Hi Robert, > > Please don't mess up the code just because of Pharo. They'll eventually > fix DoubleWordArray, but that doesn't mean the code will work at all on > Pharo. > > Levente > > On Sat, 28 Mar 2020, Robert wrote: > >> Hey Levente, >> >> In order to get Crypto running in Pharo, I will split the >> HashingPluginSupport code into a separate package, which Pharo will not >> load, but Squeak will. >> >> k, r >> >> On 3/28/20 10:26 AM, Robert wrote: >> >>> On 3/28/20 10:16 AM, Levente Uzonyi wrote: >>> >>>> Hi Robert, >>>> >>>> No, it's not a VM bug. My analysis I sent to you earlier is correct. It's >>>> that in Pharo DoubleWordArray is a variableWordSubclass instead of a >>>> variableDoubleWordSubclass. The latter is not available in Pharo. >>>> Here's the link to the issue they created based on my analysis you sent >>>> to them: >>>> https://github.com/pharo-project/pharo/issues/5956 >>> >>> Alright, I shared this analysis with Pharo's Discord channel. I must >>> have missed the discussion of the #variableDoubleWordSubclass:. >>> >>>> In theory, yes, it would be possible to rewrite SHA-512 and its related >>>> hash functions to avoid using DoubleWordArray, but I see no value in doing >>>> that. >>> >>> The value would be Crypto operational in Pharo. And all that follows >>> from that (ParrotTalk, SSL, SSH, Signal, Raven). Is it possible for you >>> to make these changes, please? I see this as more likely than Pharo >>> accommodating #variableDoubleWordSubclass:. And other Smalltalks... >>> >>> k, r >>> >>>> Pharo simply failed to properly integrate DoubleWordArray. It's there but >>>> it's disfunctional. Just wait until they fix it. >>>> >>>> Levente >>>> >>>> P.S.: This is pretty much off topic on squeak-dev. >>>> >>>> On Sat, 28 Mar 2020, Robert wrote: >>>> >>>>> Hey Levente, >>>>> >>>>> I dug a little deeper into the Pharo issue with Cryptography and it IS a VM issue, I think. Primitive 61 is failing in DoubleWordArray>>#at:put:. Pharo seems totally uninterested in fixing this so I wanted to ask you, is there any way Cryptography can avoid reliance on DoubleWordArray? >>>>> >>>>> Kindly, >>>>> Robert >> >> -- >> Kindly, >> Robert -- Kindly, Robert

1 0

← Newer
1
...
4
5
6
7
8
9
10
...
37
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

Cryptography