Skip to content
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

crypto.sha3: Support Keccak-256 and Keccak-512 #23057

Closed
1 of 2 tasks
syobocat opened this issue Dec 3, 2024 · 0 comments · Fixed by #23058
Closed
1 of 2 tasks

crypto.sha3: Support Keccak-256 and Keccak-512 #23057

syobocat opened this issue Dec 3, 2024 · 0 comments · Fixed by #23058

Comments

@syobocat
Copy link
Contributor

syobocat commented Dec 3, 2024

Describe the feature

Keccak-256 and Keccak-512 is basically same as SHA3-256 and SHA3-512, but uses 0x01 instead of 0x06 for padding.

Use Case

I need it to interact with some software that uses Keccak-256 for hashing.

Proposed Solution

No response

Other Information

No response

Acknowledgements

  • I may be able to implement this feature request
  • This feature might incur a breaking change

Version used

V 0.4.8 d3b5dbd

Environment details (OS name and version, etc.)

V full version: V 0.4.8 c4aaa2e.d3b5dbd
OS: macos, macOS, 15.1.1, 24B91
Processor: 8 cpus, 64bit, little endian, Apple M3

getwd: /Users/syobon/Git/asynchro
vexe: /Users/syobon/.v/v
vexe mtime: 2024-12-03 10:07:44

vroot: OK, value: /Users/syobon/.v
VMODULES: OK, value: /Users/syobon/.vmodules
VTMP: OK, value: /tmp/v_501

Git version: git version 2.39.5 (Apple Git-154)
Git vroot status: weekly.2024.39-563-gd3b5dbd5-dirty (1 commit(s) behind V master)
.git/config present: true

CC version: Apple clang version 16.0.0 (clang-1600.0.26.4)
emcc version: N/A
thirdparty/tcc status: thirdparty-macos-arm64 713692d4

Note

You can use the 👍 reaction to increase the issue's priority for developers.

Please note that only the 👍 reaction to the issue itself counts as a vote.
Other reactions and those to comments will not be taken into account.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant