[Glass] GRPlatform current secureHashFor: depends on the used String class

[Jerry Kott via Glass]

Marten,

this should be true on any platform. The hash is computed on a string of bit octets, IOW, binary values. The default encoding is probably going to be UTF-8, so the binary representation of the two string will be different, and therefore the hash. I don’t see any way around it other than forcing the default encoding to be UTF-16 which I don’t know how Grease handles in GLASS.

Jerry Kott
This message has been digitally signed.
PGP Fingerprint:
A9181736DD2F1B6CC7CF9E51AC8514F48C0979A5



> On 23-07-2018, at 5:26 AM, Marten Feldtmann via Glass <glass at lists.gemtalksystems.com> wrote:
> 
> I do not know, if this is an error - but I notice that secureHashFor: is based on the byte representation of the used string:
> 
> 
> 
> GRPlatform current secureHashFor: 'vorzimmer' = GRPlatform current secureHashFor: (Unicode16 withAll: 'vorzimmer' )
> 
> 
> 
> is false ....
> 
> _______________________________________________
> Glass mailing list
> Glass at lists.gemtalksystems.com
> http://lists.gemtalksystems.com/mailman/listinfo/glass

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20180723/0b92ec44/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 842 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20180723/0b92ec44/attachment.sig>