-
-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ripemd160
checksum is listed in the supported checksums but does not work
#2516
Comments
I am not certain that the issue here is related to
I do not know why it would error out on the 2nd last element and the last element. Consider the following:
I am not sure if I should create a separate issue for this, but it seems like that the returned digests are incorrect (in length as well, e.g. the returned digest for SHA-1 should be 40 characters long):
seems to be an issue as well (mind you, |
You probably want to use just: >> checksum to-binary "foobar" 'sha1
== #{8843D7F92416211DE9EBB963FF4CE28125932878}
>> checksum "foobar" 'sha1
== #{8843D7F92416211DE9EBB963FF4CE28125932878} The But it looks that the >> checksum "foobar" 'ripemd160
** Script error: invalid argument: ripemd160
** Where: checksum
** Near: checksum "foobar" 'ripemd160 This is code to count all available checksums methods: >> foreach method system/catalog/checksums [print [method tab mold/flat try [checksum "foo" method]]]
adler32 42074437
crc24 5804686
crc32 -1938594527
tcp 39201
md4 #{0AC6700C491D70FB8650940B1CA1E4B2}
md5 #{ACBD18DB4CC2F85CEDEF654FCCC4A4D8}
sha1 #{0BEEC7B5EA3F0FDBC95D0DD47F3C5BC275DA8A33}
sha224 #{0808F64E60D58979FCB676C96EC938270DEA42445AEEFCD3A4E6F8DB}
sha256 #{2C26B46B68FFC68FF99B453C1D30413413422D706483BFA0F98A5E886266E7AE}
sha384 #{98C11FFDFDD540676B1A137CB1A22B2A70350C9A44171D6B1180C6BE5CBB2EE3F79D532C8A1DD9EF2E8E08E752A3BABB}
sha512 #{F7FBBA6E0636F890E56FBBF3283E524C6FA3204AE298382D624741D0DC6638326E282C41BE5E4254D8820772C5518A2C5A8C0C7F7EDA19594A7EB539453E1ED7}
ripemd160 make error! [code: 309 type: 'Script id: 'invalid-arg arg1: 'ripemd160 arg2: none arg3: none near: [checksum "foo" method] where: [checksum try print foreach]] |
Note that what you are doing is probably not what you expect: >> system/catalog/checksums/sha1
== sha224 ;<--- because it is next word after 'sha1 Which is like one use path on blocks.. similar to: >> b: [a 1] b/a
== 1 |
checksum
ripemd160
checksum is listed in the supported checksums but does not work
Version:
1st:
2nd:
Before the regression (although the length does not seem to be correct even in this version):
Version:
That said, I get an error when the hash is
ripemd160
:The text was updated successfully, but these errors were encountered: