Keyring suddenly did not recognize the password used to
unlock. Never changed it: followed advice in faq:
downloaded and installed 1.2.3 : still same
problem.This is bad.
Was there any unusual message? Or is it reacting normal
except for not accepting the password? Which version of
keyring did you use before?
If your backup of the keyring database doesn't work there's
a way to remove the broken password hash with an hex-editor
so that keyring accepts any passwords again (of course only
the right one will produce readable entries). Mail me
(hoenicke at users dot sourceforge dot net) for details.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Look in you palm directory for a file called Keys-Gtkr.pdb (the backup
of the keyring database and invoke the java program like this from the
command line (you need to have a Java JRE installed and in the
PATH):
java -jar keyring-recover.jar Keys-Gtkr.pdb Keys-Gtkr-Fixed.pdb
Then install Keys-Gtkr-Fixed.pdb to your palm.
Keyring will report on next invokation that the database got damaged
and will give you the chance to repair it. It will now accept any
password, but only with the correct password the records will be
readable. If you entered the wrong password you have to reinstall the
Keys-Gtkr-Fixed.pdb.
Please tell me if that works. I can't really test it here, as I have no
broken database.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
keyring v2.0 pre4 tested successfully with Palm OS v4
copied same database on Palm OS v 5.4 (T5) and NEVER
recognized pwd. I rebuilt the db several times with same
results.
Now I'm using keyring v 1.2.3 on T5 and it works fine.
Hope this helps
matteo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=18252
Was there any unusual message? Or is it reacting normal
except for not accepting the password? Which version of
keyring did you use before?
If your backup of the keyring database doesn't work there's
a way to remove the broken password hash with an hex-editor
so that keyring accepts any passwords again (of course only
the right one will produce readable entries). Mail me
(hoenicke at users dot sourceforge dot net) for details.
Logged In: NO
Had exactly the same problem and could not recover:very bad
indeed
Jean-luc
Logged In: NO
I get the same problem on Zire72 with PalmOS5.2 and
Prerelease4 (german).
Logged In: NO
I get the same problem on Zire72 with PalmOS5.2 and
Prerelease4 (german).
Logged In: YES
user_id=18252
For all who are hit by the bug in 1.2.3, I have written a Java
program, that should "repair" the keyring database. You
can download it at
http://gnukeyring.sourceforge.net/keyring-recover/
Look in you palm directory for a file called Keys-Gtkr.pdb (the backup
of the keyring database and invoke the java program like this from the
command line (you need to have a Java JRE installed and in the
PATH):
java -jar keyring-recover.jar Keys-Gtkr.pdb Keys-Gtkr-Fixed.pdb
Then install Keys-Gtkr-Fixed.pdb to your palm.
Keyring will report on next invokation that the database got damaged
and will give you the chance to repair it. It will now accept any
password, but only with the correct password the records will be
readable. If you entered the wrong password you have to reinstall the
Keys-Gtkr-Fixed.pdb.
Please tell me if that works. I can't really test it here, as I have no
broken database.
Logged In: YES
user_id=863343
keyring v2.0 pre4 tested successfully with Palm OS v4
copied same database on Palm OS v 5.4 (T5) and NEVER
recognized pwd. I rebuilt the db several times with same
results.
Now I'm using keyring v 1.2.3 on T5 and it works fine.
Hope this helps
matteo