5 byte seed key algo

[nmstec]

Basically I have an unhealthy obsession with figuring out everything, even when not needed or not in scope. And this one is driving me up the fucking wall.
Usual known information I wont go over in depth, we take the aes key hash, ignore first 2 chars, decode, and then use first 32 out of 44 bytes for the actual key calc. Great.

Question here being, does anyone know what the last 8 bytes are for?

Known factors:
after 32 bytes, we have 3 bytes with some form of marker, always 00 f5 00, fine, not really interesting. Is also the same throughout all 256 keys.
Next byte after that being the algo ID itself.
Theres plenty of references in the sa015 that is is a sha256hash of the password. However that seems to include ALL the data after the first 32 bytes

Gone through DPS source as much as I can, as well as sa015, and still fuck all reference to it.

[nmstec]

Update: Boring. Its a SHA256 of the first portion of the data. Just a verification. I failed to reload the project and recheck that I did from like 2 years ago.

[antus]

I deleted your image attachment as it contained keys. I am not comfortable with sharing the encryption keys on the site, but I will allow the discussion of how it works.

[nmstec]

To be fair those keys are not used, which is why I selected them. I can generate a few fake ones if you prefer?

[nailgg]

Update: Boring. Its a SHA256 of the first portion of the data. Just a verification. I failed to reload the project and recheck that I did from like 2 years ago.

Correct, but the count of the SHA256 operations will differ from seed to seed.

[andbel]

Saying 'hi' and subscribing

[nmstec]

Update: Boring. Its a SHA256 of the first portion of the data. Just a verification. I failed to reload the project and recheck that I did from like 2 years ago.

Correct, but the count of the SHA256 operations will differ from seed to seed.

Yeah the calculation I know of ages ago, I just wanted to figure out what the rest was for.