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.

Sign up for GitHub

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

Jump to bottom

Add SHA-3 algorithm support to file integrity module #5345

Closed
andrewkroh opened this issue Oct 6, 2017 · 0 comments
Closed

Add SHA-3 algorithm support to file integrity module #5345

andrewkroh opened this issue Oct 6, 2017 · 0 comments
Labels
Auditbeat enhancement good first issue Indicates a good issue for first-time contributors Hacktoberfest

Comments

@andrewkroh
Copy link
Member

andrewkroh commented Oct 6, 2017 •
edited
Loading

The Auditbeat file integrity module currently has support for MD5, SHA-1, and SHA-2 algorithms. It would be simple to add support for the latest member of the Secure Hash Algorithm family - SHA-3. The algorithms are implemented in golang.org/x/crypto/sha3.
@andrewkroh andrewkroh changed the title Add sha3 algorithm support to file integrity module Add SHA-3 algorithm support to file integrity module Oct 6, 2017
@liketic liketic mentioned this issue Oct 6, 2017
Merged
@tsg tsg added the good first issue Indicates a good issue for first-time contributors label Oct 12, 2017
liketic added a commit to liketic/beats that referenced this issue Oct 13, 2017
@liketic
Support SHA3 hash algorithm family (elastic#5345)
bba5423
andrewkroh pushed a commit that referenced this issue Oct 13, 2017
@andrewkroh
Support SHA3 hash algorithm family (#5345) (#5346)
7737b57 
* Support SHA3 hash algorithm family (#5345)

* Add test for new hash types

* Update CHANGELOG.asciidoc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Auditbeat enhancement good first issue Indicates a good issue for first-time contributors Hacktoberfest
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@urso @tsg @exekias @andrewkroh