not recognizing my passphrase after moving from XP to Win7

Henry Hertz Hobbit hhhobbit at
Thu Jul 11 16:23:03 CEST 2013

On 07/08/2013 09:22 AM, Peter Lebbing wrote:
> On 07/07/13 21:53, Henry Hertz Hobbit wrote:
>> I did the same there but I do modify the random_seed file with hexedit for 
>> each key-ring which some people object to.  From my point of view that is far
>> better than just having each key-ring having the same random_seed file.
> As one of the people to object, let me repeat that you simply shouldn't copy the
> random_seed file to another system, but let it create its own. I agree that
> having each keyring start out with the same random_seed file is a bad situation,
> which is trivially avoided. Even removing it after the copying is less work than
> monkey-bashing the hex part of your keyboard in a hexeditor :).

I do NOT just copy it.  I hexedit it and randomly, not pseudo-randomly
replace some of the bytes (actually nibbles).  The reason why again
I when I omitted the random_seed file gnupg (1 or 2) would NOT just
create the file.  I imagine it would if I used the keys on Windows
for either signing or enciphering it may have created the random_seed
file but since I but I don't use them that way but only for verifying
detached signature files for what ever reason they never got created.

Whether you choose to believe my random chaging of nibbles in the
random_seed file (there is NO plan of what to change or even how
many and some of them may even get the same nibble with the change)
is up to you.  I am NOT telling this person to do the same thing.
In this case, since he copied the entire key ring I would advise
that he delete the random_seed file as a security measure.

But in the case of Windows 7 I didn't know where they keys should be
put so I created a dummy key after a GPG4WIN install.  After that
I copied over all of my files BUT the random_seed file in the
AppData\roaming\gnupg folder.

More information about the Gnupg-users mailing list