| commit | 2b0753add8a627bdfbadfb5ff91c97d1901a6e85 | [log] [tgz] |
|---|---|---|
| author | android-build-team Robot <android-build-team-robot@google.com> | Sat Apr 24 03:04:30 2021 +0000 |
| committer | android-build-team Robot <android-build-team-robot@google.com> | Sat Apr 24 03:04:30 2021 +0000 |
| tree | e2e393cd7adb04f018f30c8a34836270d7421276 | |
| parent | 8e850cdf9a9a7a68c9b244298e7677c4100af84c [diff] | |
| parent | 23714ed84501f0b908d036bb428ff1406dbbe29d [diff] |
Snap for 7310088 from 23714ed84501f0b908d036bb428ff1406dbbe29d to sc-d1-release Change-Id: Ieac4b4b6b6afc1aabdd04090616bb3af309c2fc0
AHash is the fastest, DOS resistant hash currently available in Rust. AHash is intended exclusively for use in in-memory hashmaps.
AHash's output is of high quality but aHash is not a cryptographically secure hash.
Because AHash is a keyed hash, each map will produce completely different hashes, which cannot be predicted without knowing the keys. This prevents DOS attacks where an attacker sends a large number of items whose hashes collide that get used as keys in a hashmap.
This also avoids accidentally quadratic behavior by reading from one map and writing to another.
AHash does not have a fixed standard for its output. This allows it to improve over time. For example, if any faster algorithm is found, aHash will be updated to incorporate the technique. Similarly, should any flaw in aHash's DOS resistance be found, aHash will be changed to correct the flaw.
Because it does not have a fixed standard, different computers or computers on versions of the code will observe different hash values. As such aHash not recommended for use other than in-memory maps. Specifically, aHash is not intended for network use or in applications which persist hashed values. (In these cases HighwayHash would be a better choice)
Additionally, aHash is not intended to be cryptographly secure and should not be used as a MAC, or anywhere which requires a cryptographically secure hash. (In these cases SHA-3 would be a better choice)
AHash is a drop in replacement for the default implementation of the Hasher trait. To construct a HashMap using aHash its hasher do the following:
use ahash::{AHasher, RandomState}; use std::collections::HashMap; let mut map: HashMap<i32, i32, RandomState> = HashMap::default(); map.insert(12, 34);
For convinence wrappers called AHashMap and AHashSet are also provided. These to the same thing with slightly less typing.
use ahash::AHashMap; let mut map: AHashMap<i32, i32> = AHashMap::new(); map.insert(12, 34); map.insert(56, 78);
The aHash package has the following flags:
std: This enables features which require the standard library. (On by default) This includes providing the utility classes AHashMap and AHashSet.compile-time-rng: Whenever possible aHash will seed hashers with random numbers using the getrandom crate. This is possible for OS targets which provide a source of randomness. (see the full list.) For OS targets without access to a random number generator, compile-time-rng provides an alternative. If getrandom is unavailable and compile-time-rng is enabled, aHash will generate random numbers at compile time and embed them in the binary. This allows for DOS resistance even if there is no random number generator available at runtime (assuming the compiled binary is not public). This makes the binary non-deterministic, unless getrandom is available for the target in which case the flag does nothing. (If non-determinism is a problem see constrandom's documentation)NOTE: If getrandom is unavailable and compile-time-rng is disabled aHash will fall back on using the numeric value of memory addresses as a source of randomness. This is somewhat strong if ALSR is turned on (it is by default) but for embedded platforms this will result in weak keys. As a result, it is recommended to use compile-time-rng anytime random numbers will not be available at runtime.
A full comparison with other hashing algorithms can be found here
For more a more representative performance comparison which includes the overhead of using a HashMap, see HashBrown's benchmarks as HashBrown now uses aHash as its hasher by default.
AHash passes the full SMHasher test suite.
The code to reproduce the result, and the full output are checked into the repo.
A separate FAQ document is maintained here. If you have questions not covered there, open an issue here.
Licensed under either of:
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.