Ethereum Pre-Sale extract SAFE hash (non-revealing private keys)
#6
So I spends the last fews days searching and coding and assuming.

I have finally find the padding at the end of the encseed (using an encseed created by me ) a72643507070707070707. The issue is that it's at the end of the encseed which is an issue because the seed is encrypted with aes cbc if I want to decrypt the last block I need the data of the n-1 block and to get this one I need n-2 and so on. 

Are the padding always at the full end of the decrypted text or there could "partial padding" ? 

I didn't find any way to decrypt the hash from left to right too ... 

I'm still wondering if there is a way to crypt both encseed and bkp(private key encoded) using a special algorithm. And even in case someone find the password it will still be encrypted by the new password I put. If you have any idea I take it Smile . 

Also I have took a good look at the 16300.c mode on hashcat and there is no padding check from what I saw and no entropy check too.

Was also looking to partially decode the bkp(private key encoded) to use half of it to create the pub key and then generate the public address and check for a match. But due to the SHA3 it should not work normally. 

One thing sad is that all this could have been avoided by a simple "encseed": at the beginning of the encrypted seed. I could have easily add early throwaway for all the decrypted seed who don't have this... but due to the fact a seed is purely random and I don't know any part of my seed it i can't verify the seed validity ... 

One of the only thing that could work is end is the "entropy" check but i'm not sure the real seed will be the one with the most entropy ? I spend a bit of time checking the entropy of some string and it seems to not work like this ... 

If anyone have any others ideas don't hesitate to reply Smile
Reply


Messages In This Thread
RE: Ethereum Pre-Sale extract SAFE hash (non-revealing private keys) - by hkbb345 - 06-11-2023, 03:34 PM