Support for the `blake3` hash algorithm in `hash` calculation
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 23.6k
- Forks
- 2.6k
- Avg merge
- 6d 7h
- Merged PRs (30d)
- 14
Description
Thanks you for this incredible tool 🙂
Feature request
What new feature do you want?
Support for the blake3 hash algorithm.
Typically, be able to use this for example :
SELECT path,blake3 FROM hash WHERE path LIKE '/usr/local/bin/%';
How is this new feature useful?
This would improve performance of osquery when calculating hashes. blake3 is considerably faster than blake2, sha256 and md5
How can this be implemented?
libgcrypt doesn't support blake3 so I guess it would require to use the official C implementation.
Osquery could also at least supports blake2 which is supported by libgcrypt.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing osquery's existing hash calculation entry point and its libgcrypt integration, then compare the official BLAKE3 C implementation with the current approach. Done means the hash table supports the blake3 column and the example SELECT query returns calculated values; the issue does not name a specific file or test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, cpp
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100