Outline · [ Standard ] · Linear+ Lost userhash.dat

Hi....

My userhash.dat file was corrupted (along with ALL of my eMule setup)..

A new usershash has been generated..

The old was: 9D7EF41AD40ExxxxF80BA743B7136F0F
The new is: 90CBA8B4960Exxxx98D1FB6A11756F72

How do I get my OLD userhash back? The userhash.dat seems to be encrypted in some way..

EDIT: Hashes masked to avoid possible hashstealers

This post has been edited by Fuxie - DK: Mar 1 2004, 23:28

Well userhash is tied to your private. key If this was also corupted, changing back to your old userhash (using a hex edior) will cause your client to fail SUI.

This post has been edited by moosetea: Mar 1 2004, 11:58

EVERY .ini and .dat in my Config dir was zero'ed out..
Size was correct, but there was no contents..

I didn't realise this until I restarted eMule... The Backup dir was already overwritten also..

Are you telling me that I've lost ALL of my credits this way?

Yes, if you lost your private key.

As we use PKI to secure credits its a vital part of the process, and cannot be hacked/reversed. Your credits will be locked out on the remote pcs, but at least no-one can steal them.

Do you mean the cryptkey.dat file??

That hasn't been changed since 18/9-03, so it's intact...

Ok, good, you need to fix your userhash asap then, because your client will currently be failing SUI, as you have the incorrect userhash.

Your going to need a hex editor to make the change

try this app:
http://www.chmaas.handshake.de/delphi/free...xvi32/xvi32.htm

@devs : Just a thought but if we are derviving the userhash from the Md4 of the public key, why not do this everytime plus starts? If a clients userhash courupts in this way there client wont be authenticating properly and will eternally have slow download speeds.

This post has been edited by moosetea: Mar 1 2004, 14:10

I have no problem changing the userhash.dat file using the program you've described..
The new old hash (9D7EF41AD40ExxxxF80BA743B7136F0F) is written into the file.
But when I restart eMule, it reports 90CBA8B4960Exxxx98D1FB6A11756F72 as my userhash and writes this in the file..

EDIT: Hashes masked to avoid possible hashstealers

This post has been edited by Fuxie - DK: Mar 1 2004, 23:32

Try preferences.dat

YES!!!! It works!!!

I changed both userhash.dat and preferences.dat.....

That's known trick of NTFS file system after BSOD. NTFS is faster and stable, but is less stable against BSOD.

it's already over but i think it would have been enough to rename preferences.dat so that userhash is not taken from it and instead userhash.dat would take effect.

Indeed, but this couruption isnt good. It would lock most users out of credit due to inconsistancies between Public key and userhash.

That's known trick of NTFS file system after BSOD. NTFS is faster and stable, but is less stable against BSOD.

In all the time I've been running WinXP I've never had as much as a single BSOD....