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
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
cryptography@lists.squeakfoundation.org