referencesource VS smhasher

But to go deeper to .NET/CLR architecture is important too. Try to understand how it works inside. Use the source, Luke! https://source.dot.net/ https://referencesource.microsoft.com/ This source code vaults is not completed then try JetBrains dotPeek tool to look at any assembly source code.

(https://github.com/Microsoft/referencesource/blob/master/System.ServiceModel/System/ServiceModel/MessageSecurityVersion.cs; scroll down to inner classes)

List is an IList/IReadOnlyList; these interfaces do nothing that couldn't be done right inside the file itself.

https://referencesource.microsoft.com/#mscorlib/system/colle...

https://referencesource.microsoft.com/#mscorlib/system/colle...

Instead we have to go diving through the IList, which implements ICollection, which implements IEnumerable, which implements IEnumerable (again). Just because each interface is composed of another interface, doesn't mean you aren't using inheritance. You are effectively creating a custom inheritance tree through willy-nilly composition.

It is gratuitous to make this chain so deep, when the underlying code is just a handful of lines.

https://referencesource.microsoft.com/#mscorlib/system/colle...

https://referencesource.microsoft.com/#mscorlib/system/colle...

https://referencesource.microsoft.com/#mscorlib/system/colle...

----------------------------------------------------------------------------------------------------------------

The doc-strings are unnecessary. It's self-evident what most of the code does if you read it.

        // Returns an enumerator for this list with the given

The whole .net framework source code is online.

https://github.com/microsoft/referencesource/blob/master/System.Numerics/System/Numerics/Vector2.cs https://github.com/microsoft/referencesource/blob/master/System.Numerics/System/Numerics/Vector2_Intrinsics.cs

.net itself has arbitrary interfaces, ex https://github.com/microsoft/referencesource/blob/master/mscorlib/system/action.cs

Assuming if you are new to C# - start coding! And start reading https://learn.microsoft.com/en-us/dotnet/csharp/tour-of-csha...

If you are not new to C#, start building an application end-to-end/a classic n-tier application, right from using a database, Entity Framework, WebAPI, DTO, AutoMapper, and a front-end (your choice - Angular/React/Vue with TypeScript or better yet - Blazor).

You will not only understand & use dependency injection, reflection, LINQ, multi-threaded programming, generic programming, source-code generation, unit-testing - and much much more in a practical/real-world usage.

Peruse https://referencesource.microsoft.com/ once in a while.

Follow various team members of .NET Framework, C# team and the like on various social-media. https://mobile.twitter.com/i/lists/120961876

I am sure there will be who agree / disagree with the above approach and will provide more viewpoints for you to consider.

Enjoy - and strap yourself for an amazing journey or roller-coaster ride, however you want to call it!

Maybe from the source of FtpWebRequest it is possible to track what the default behaviour is.

The class is just a very limited dictionary, a library will be the same or better.

The algorithm passes all SMHasher quality tests and uses rounds of AES block cipher internally, so it is quite robust! For comparison XxH3, t1ha0 and many others don't pass SMHasher (while being slower).

Confirmed, I tested it. https://github.com/rurban/smhasher

There's lots of great hash functions out there: some are super fast, like xxhash and highly optimized, others are also super fast umash and based on interesting math ideas from finite fields^1, while maintaining high quality (according to SMHasher). Others are also fast and interesting (tabulation hash, that may sometimes be seemingly universal), one of the main originators of those ideas are Mikkel Thorup^2. Anyway, a couple of years ago I also tried my hand at building hashes and created a few that passed SMHasher (tifuhash ~ a floating point hash, beamsplitter - a seemingly-universal tabulation style hash, and this one discohash - a "more traditional" ARX-based design (addition rotation xor)^3 ).

0: https://github.com/rurban/smhasher/blob/master/xxh3.h

1: https://pvk.ca/Blog/2022/12/29/fixing-hashing-modulo-alpha-e...

2: https://arxiv.org/abs/1505.01523

3: https://eprint.iacr.org/2018/898.pdf https://crypto.polito.it/content/download/480/2850/file/docu...

4: https://en.wikipedia.org/wiki/BLAKE_(hash_function)

Discohash (posted here) is the fastest one I made, it's simple and doesn't rely on any arch-specific optimizations or vector instructions (AVX etc ~ tho I suppose...they could be added? I'm definitely no expert in them, I barely get away with doing the C/C++ implementations!)

The main mixing round function is:

  mix(const int A) {

ubsan, asan, valgrind tests are missing. some do offer symbolic verification of the algo, but not the implementations.

See my https://github.com/rurban/smhasher#crypto paragraph, and

The spinach story reminds me a lot on the false recommendation of siphash for hash table DDOS prevention. https://github.com/rurban/smhasher#security

The authors came up in their widely cited paper with a proper solution to spread the random hash seed into the inner loop, vastly enhancing its security by avoiding trivial hash collision attacks. But a secure, slow hash function can never prevent from normal hash seed attacks, when the random seed is known somehow. esp. with dynamic languages it's trivial to get the seed externally.

Other trivial countermeasures must be used then, which also don't make hash tables 10x slower, keeping them practical.

This is the best, most comprehensive hash test suite I know of: https://github.com/rurban/smhasher/

you might want to particularly look into murmur, spooky, and metrohash. I'm not exactly sure of what the tradeoffs involved are, or what your need is, but that site should serve as a good starting point at least.

Here is a good comparison table, as you can see, BLAKE can perform in secure way much faster than crc32, so my original point, - to use non weak hashes unless you really have a reason/requirement not to do so

smhasher is a great place to testing results for a massive number of hash algorithms.