Page MenuHomeFreeBSD

[NEW PORT] security/highwayhash: Fast strong hash functions: SipHash/HighwayHash
ClosedPublic

Authored by ultima on Aug 12 2017, 4:32 AM.
Tags
None
Referenced Files
Unknown Object (File)
Mon, Mar 4, 3:46 PM
Unknown Object (File)
Feb 1 2024, 7:05 PM
Unknown Object (File)
Feb 1 2024, 4:27 PM
Unknown Object (File)
Jan 23 2024, 9:18 AM
Unknown Object (File)
Jan 15 2024, 4:28 PM
Unknown Object (File)
Jan 15 2024, 5:09 AM
Unknown Object (File)
Jan 14 2024, 12:42 AM
Unknown Object (File)
Dec 28 2023, 1:07 AM
Subscribers

Details

Summary

Strong (well-distributed and unpredictable) hashes:

  • Portable implementation of SipHash
  • HighwayHash, a 5x faster SIMD hash with security claims

WWW: https://github.com/google/highwayhash

PR\: 219232
Submitted by\: Yuri Victorovich (maintainer)
Reviewed by\: lifanov (mentor), matthew (mentor)
Approved by\: lifanov (mentor), matthew (mentor)
Differential Revision\: https://reviews.freebsd.org/DXXXXX

Test Plan

portlint:
looks fine.

poudriere:
103i386: is only for amd64 arm64 powerpc powerpc64, while you are running i386 (reason: Assembly is implemented only for specific architectures in highwayhash/tsc_timer.h)
103amd64
110i386: is only for amd64 arm64 powerpc powerpc64, while you are running i386 (reason: Assembly is implemented only for specific architectures in highwayhash/tsc_timer.h)
110amd64
12i386: is only for amd64 arm64 powerpc powerpc64, while you are running i386 (reason: Assembly is implemented only for specific architectures in highwayhash/tsc_timer.h)
12amd64

Diff Detail

Repository
rP FreeBSD ports repository
Lint
No Lint Coverage
Unit
No Test Coverage
Build Status
Buildable 11053
Build 11438: arc lint + arc unit

Event Timeline

security/highwayhash/Makefile
28–34

This is a bit messy, the maintainer has requested upstream to fix.

security/highwayhash/Makefile
28–34

It's good when port maintainers upstream FreeBSD related changes -- here it would be good to get the content from patch-highwayhash_os__specific.cc upstreamed as well. If a change has been submitted upstream, mentioning that in the commit message is a good thing to do.

However, none of that should hold up getting the update into the tree. Showing that thousands of people are already using a patch is very persuasive to the upstream projects.

  • Added comment and link to upstream issue
This revision is now accepted and ready to land.Aug 13 2017, 12:37 PM
This revision was automatically updated to reflect the committed changes.