Fuxie - DK
Mar 1 2004, 11:53
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
moosetea
Mar 1 2004, 11:57
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.
Fuxie - DK
Mar 1 2004, 12:00
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?
moosetea
Mar 1 2004, 12:27
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.
Fuxie - DK
Mar 1 2004, 13:27
Do you mean the cryptkey.dat file??
That hasn't been changed since 18/9-03, so it's intact...
moosetea
Mar 1 2004, 14:07
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.
Fuxie - DK
Mar 1 2004, 14:51
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
moosetea
Mar 1 2004, 15:08
Try preferences.dat
Fuxie - DK
Mar 1 2004, 15:14
YES!!!! It works!!!
I changed both userhash.dat and preferences.dat.....
| QUOTE (Fuxie - DK @ Mar 1 2004, 12:00) |
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.. |
That's known trick of NTFS file system after BSOD. NTFS is faster and stable, but is less stable against BSOD.
| QUOTE (Fuxie - DK @ Mar 1 2004, 17:14) |
| I changed both userhash.dat and preferences.dat..... |
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.
moosetea
Mar 1 2004, 16:39
Indeed, but this couruption isnt good. It would lock most users out of credit due to inconsistancies between Public key and userhash.
Fuxie - DK
Mar 1 2004, 16:50
| QUOTE (Aw3 @ Mar 1 2004, 16:45) |
| QUOTE (Fuxie - DK @ Mar 1 2004, 12:00) | 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.. |
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....
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.