cksum: Bring back blake3 algorithm#11316
Conversation
|
GNU testsuite comparison: |
This comment was marked as resolved.
This comment was marked as resolved.
b2d43e2 to
3387ee5
Compare
Merging this PR will degrade performance by 99.88%
Performance Changes
Comparing Footnotes
|
|
CodSpeed is invalid since it is based on a bunch of clap error. |
|
GNU testsuite comparison: |
72790dd to
45b28c6
Compare
|
GNU testsuite comparison: |
|
GNU testsuite comparison: |
1 similar comment
|
GNU testsuite comparison: |
AldanTanneo
left a comment
There was a problem hiding this comment.
If the length of blake3 is stored in bytes, it should validate that the input bit size is a multiple of 8, like in the blake2b implementation.
|
Any length support is coming from https://github.com/BLAKE3-team/BLAKE3 |
Your point? |
|
The existing |
Yes but the existing |
|
We should not divergent interfaces. So we should be same with the |
So matching the interface of a non GNU utility is more important that following the standard conventions for coreutils (always taking the length in bits)? |
|
Yes, Some people might have shebang compat wrapper (even it is very bad idea). |
|
To be honestly, I think we should just remove b3sum extenstons. We should not be interested in such wars. |
Ok so to explain my reasoning here:
For all these reasons, I think we should interpret the length in bits for blake3 rather than in bytes. |
I missed the case... |
Sorry I don't understand what you mean. What do you mean ? |
|
sorry. Please forget the comment which is not important. |
| (ak::Sha1, _) => Ok(Self::Sha1), | ||
| (ak::Blake3, _) => Ok(Self::Blake3), | ||
|
|
||
| (ak::Blake3, l) => Ok(Self::Blake3(l)), |
There was a problem hiding this comment.
the length is not validated here, but it is for the blake2b algo
|
Benchmark test fails because I re-enabled one. |
Fix #10002