# MP's fabulous hash function, and its family

This proposal stems from a recent discussion in the forum of The Most Serene Republic, and consists of a readaptation of an older idea of Stan's to the task at hand^{i}.

The item here contemplated is then an algorithmic, rather than algebraic, hash function. It consists of three elements and four operations, which we proceed to define :

**Elements** of the fabulous hash function :

- One element is the message to be hashed, M, which is a field of bits of unspecified length.
- Another element is the so called state machine, S, which starts as one null bit and grows to an unspecified length.
- The last element is the result of the hashing, R, which is a field of bits of user-specified length.

**Operations** of the fabulous hash function :

- One operation is the bit flip, let it be called
**flip**. This operation consists of toggling one specified bit of either S or R. - Another operation is the inversion, let it be called
**invert**. This operation consists of toggling all the bits of either S or R. - A third operation is the flipping of a number of bits in either S or R, let it be called the
**screw**. This operation consists of taking the bit count of either S or R, iterating over that value, at each step multiplying the iterator with the current position in M, calculating the remainder of that product against the bit count of R or S respectively, and flipping the remainder-th bit in R or S respectively. A**half-screw**will take half (floor) the bit count of S or R instead. - The fourth operation is a shift of the state machine, call it
**expand**. This operation consists of adding one null bit at the end of S. - The last operation is a position rewind, call it a
**rewind**. This operation consists of decreasing our position in the message M by one, except in the case our position is already 0.

On this basis we can now proceed to define our function :

**I. The function starts** by allocating memory : one bit for S, and the size specified by the user for R. All allocated bits are zero.

**II. The function starts** at position 0 in M and iterates over each bit in M. These iterations are called steps. During each step, the function considers whether the position-th bit in M is 0 or 1, and executes a defined set of operations in either case. Once the operations have been executed, the position is incremented by one. Once the position is larger than the size of M, the function returns R as the hashed value of M.

So far we have defined a whole *class* of hash functions : the Fabulous Hash Function family. Numerous kinds and types could be devised on the basis described, and any willing operator of a numeric machine is certainly encouraged to do so for his own needs and uses.

Let us now consider the canonical example of a FHF : MP's own FHF. It goes like so :

- if the bit in M is 0,
**expand**and**screw**S in R. If the bit in R found at the position equal to the remainder of the division of our position in M by the size of R is 0- That bit in R is
**flipped**and we**rewind**. - else, that bit in R is
**flipped**and S is**inverted**.

- That bit in R is
- if the bit in M is 1,
**half-screw**S in R. If the bit in R found at the position equal to the remainder of the division of our position in M by the size of R is equal to the bit in S found at the position equal to the remainder of the division of our position in M by the size of S- We
**expand**and then**screw**R in S. - else, that bit in R is
**flipped**.

- We

**There are a number of important properties** to be underlined.

- The very last bit of M can produce significant change in R, potentially touching all its bits.
- The fabulous hash-function is message-size indifferent, being operable of messages of any size within the limitations of the hardware only.
- The fabulous hash-function outputs hashes of any arbitrary length equally well.
- It is not possible to say, on the basis of a hash, how much memory, or how much CPU was consumed to process the message.
- The cheapest way to calculate how much memory, or how much CPU will be needed to process a message is to process the message.
- Because the fabulous hash function does not use blocks, it does not require any kind of padding.

Diligent work by ben_vulpes and sina allows us no less than three canonical implementations to choose from : lisp, go, python.

———- Which is, exactly as he states it, to resolve the major weakness that the hash function can be written as an equation.
The fundamental, intrinsic and so far nor escaped weakness of all currently known hash functions is that a system of equations equal to the count of their possible outputs could be written ; and resolved. No, the usual obscurantism passing for "analysis" in the field does not resolve this problem anymore than sprinkling some truly strong holy water cures lesbianism. [↩]

Friday, 6 January 2017

> Once the position is larger than the size of M, the function returns R as the hashed value of M.

Why not waltz full-circle (modularly) around the underflow ?

i.e. nextpos

Friday, 6 January 2017

Because you gotta stop sometime.

Friday, 13 January 2017

Since alf decided to vaguely open the discussion in the log,

let me point out that I won't entertain discussions pertaining to this hash outside of comments here ; or else articles on blogs which have the capacity to pingback or something. Finding discussions in #trilema logs is already a hard enough problem ; no need to make it even harder for absolutely no reason through lazily misplacing there discussions that do have a natural genesis otherwise.

As to the subject of collision resistance : every hash function has collisions as a matter of definition : if the message M is 65 bits long and the hash result R is set to 64 bits, then there will be on average 2

^{64}= 18`446`744`073`709`551`616 collisions over the entire space, or about every other M will collidewith something. This results from elementary properties of numbers, you can't shove four apples in two boxes so that there's one apple per box.So : if R is not shorter than (most) M then the function is not a hashing function (I suspect USGtards would call it a "PRNG") ; if R is shorter than (some) M then there's going to be (some) collision going on. These are the definitions of our terms.

The problem of

findingcollisions is an entirely different kettle of fish.Should the length of R be set to one bit, then in a list of arbitrarily chosen Ms every other one would collide, on average, and irrespective of length. Finding collisions would require calculating slightly more than one hash (by a formula produced by l'Hospital, not going to go into detail here).

Should the length of R be set to something reasonable (which, for this hash, as opposed to any other, is very easy to do), and should the length of the message M not be known by the attacker, then the problem he faces consists of finding a message M' so that MPfhf(M) = MPfhf(M'). The brute force method to do this is to take as final S all numeric values from 0 to an arbitrary number T, and work backwards to a legal state. It is to be expected that some of these final values for S the attacker chooses will produce a legal final state (ie, with S = "0") after a finite number of steps. It is however also to be expected that some won't, and as far as I know there isn't currently a way known to establish whether the brute force hash inversor stops after a finite number of steps. (Then again this problem may in fact be mitigated by limiting the hash reverser to a number of steps chosen on the basis of assumptions wrt to the length of the message, as suggested by the examples given in the article).

In particular, should the length of M be known to the attacker as an upper bound (M is no longer than 64 bytes, say, or about 2% of this comment) then this method reduces to taking all values from 0 to 2

^{1024}and working backwards, for a total of 2^{1025}-1 tries. If the attacker knows the exact length of M, then the values to be taken are from 2^{2lM-1}to 2^{2lM}-1, or roughly speaking 2^{2lM}.The variance seen in practice, where a short 63 bit (8 characters) message required from a minimum of 231 to a maximum of 264 steps and ended with a S from a minimum size of 194 to a maximum size of 228 bits would suggest that assumptions to be made in reversing the hash can't be very narrow. That 228 to 194 bit differential in final S accounts for an immense numeric space, longer certainly than the entire strength of any and all hashing schemes currently in use.

It should also be pointed out that with each successive step, the possible message space doubles, so if the attacker is expecting to find a collision for a hash of a message that is precisely 64 bytes long then he is looking at 2

^{1024}distinct messages to be processed against the 2^{1025}machine states (because at every successive step, the message bit corresponding could be either 0 or 1). A nontrivial task as such.It would be very interesting to see a better-than-bruteforce attack described for this hashing scheme, and I strongly urge all cryptographers, of the actual as opposed to the commonly seen pretend kind, to set to work and make a name for themselves through presenting such an attack.

It would also be very interesting to see efficient hash and reverse-hash processes implemented, so actual timing (in both terms of microseconds and cycles) can be calculated. So far there's been a remarkable resistence to any sort of useful work doing on this front, notwithstanding that unlike most other activities, this is both approachable and

That is all.

Friday, 13 January 2017

This is a very good likbez re subj of hash collisions.

However, my own research has not turned up anything encouraging that would differentiate the current state of the art re: collision-resistance of any known hash algo, from the quite similarly pseudoscientifically alleged attack-resistance of any block ciphers. Exactly same arguments from "I find it confusing, therefore the enemy must be similarly confused", "let's mix it up! and again! and again!" and other claptrap in the same vein.

In so far as is known to me, no known hash algo has any (publicly known, various USG algos may well have nonpublic proofs of weakness...) actual scientific basis whatsoever. Nor are any statements that have been uttered regarding their collision resistance, supported by actual logic of whatever kind. (Wishful thinking, and "not broken yet!" are not logic.) The only thing that is easily turned up is the record of hash algos known to be broken (collisions known to have been found on demand at reasonable expense.) Which is not particularly useful.

Friday, 13 January 2017

This is fair, and I readily admit that I have no further basis to suspect the scheme described may be workable than "it feels this way to me". I know of no proper approach to the matter, which is why I've yet to do anymore than that myself.

It would be not at all an easy task to undertake defending the proposition that sha-512 say is any stronger than the above.

Friday, 13 January 2017

The only thing that I was able to establish with certainty is that if ~anyone~ knows of a basis to logically support the strength of even one yet-unbroken hash algo -- they aren't telling. And that discussing the subj with so-called "professional" cryptographers is an activity of strictly entomological interest.

Friday, 13 January 2017

Myeah. I don't see much path forward other than actually doing the basic work of implementation.

Wednesday, 1 March 2017

Should not flipping 2nd (0th, 1st, 2nd) bit of 010 result in 011, and is not remainder of 15 against 4 3?

Wednesday, 1 March 2017

Do you actually mean that

should in fact read

and that the rest of the operations are incorrect from there on ?

I'd say this is not the case, the bitcount of S is 3, and 10 % 3 = 1.

If you actually mean something else please give explicit difs, it's rather impossible to guess-follow otherwise.

Wednesday, 1 March 2017

Sorry, I'll try again.

Should read:

"2nd bit" being in the last position, as we zero-index (0th, 1st, 2nd).

And...

Should read:

As the bit-count of R is four; 15 mod 4 returns 3.

Wednesday, 1 March 2017

Ah right you are, seems I fucked it up.

Saturday, 10 June 2017

The spec was updated as per discussion in the logz.

Saturday, 10 June 2017

Saturday, 10 June 2017

Saturday, 10 June 2017

Thanx for posting!

Saturday, 10 June 2017

single threaded mpfhf-golang can provide a 32-bit mpfhf hash of GPLv2 in ~7m

http://wotpaste.cascadianhacker.com/pastes/nfTbm/?raw=true

Saturday, 10 June 2017

Sounds just about as it should be.

Saturday, 10 June 2017

In the article, footnote 2, it describes the screw going from 1 to the number of bits, but Sina's python implementation posted goes from 0 to number of bits - 1. Should one of these be corrected?

Saturday, 10 June 2017

Yes, the footnote. Basically we encountered some strange in terms of counterintuitive behaviour, which frankly is still being investigated because wtf.

Friday, 30 June 2017

The article was substantially edited today. I expect we have a mature item now, for which reason the title changed also.

Wednesday, 5 July 2017

The wording for the screw operation is slightly ambiguous. When you say "screw R in S", do you mean you are flipping bits of R or flipping bits of S?

Thursday, 6 July 2017

In S -- the first variable of the screw function provides indexing and the second gets operated on. (That's why they're ordered S, R and then R, S. Also that's why the word respectively is in there, this being the convention to avoid ordering ambiguities with a minimum of effort.)

Tuesday, 15 August 2017

A python implementation of the mpfhf and a reverse hash function to go with it.

http://archive.is/jmFMO

Tuesday, 15 August 2017

To quote his lordship vulpes, noice!

Thursday, 17 August 2017

An updated version of the reverse hash with a couple bug fixes:

http://archive.is/Wl893

The bugs:

1: the "show" function in the Register class was missing the comparison with the "_inverted" variable, so it would be wrong in any case where there was an odd number of inversions. I think I left that out when I originally wrote the mpfhf function because the R never gets inverted, and originally the function only returned the R value instead of this version which returns both the R and S values.

2: I added a check on the branches that involve expanding to make sure S would never be shrunk below a length of 0.

3: There is a special case where the rewind does not happen if we are on step 0, I added that to the "check" recursive function.

Further testing is welcome.

Thursday, 17 August 2017

Cool deal.

Friday, 18 August 2017

http://archive.is/cJNp3

Updated again, this time it should work!

Line 126 had the wrong logic after line:

def cyclecheck(m, oldbits, R, S, L):

- if R.val(m) == 1 and S.length() > 1 and S.val(-1) == 1:

+ if R.val(m) == 1 and S.length() > 1 and S.val(-1) == 0: