Re: [gnukeyring-discuss] Recovering from a backup snafu

[Ian S. <ian...@ni...>]

"Jochen Hoenicke" <Hoe...@In...> writes:

> On Thursday 02 June 2005 17:05, Ian Soboroff wrote:
>> 
>> My T2 suffered a bad crash, and I had to restore from backup.
>> Unfortunately, something seems to have gone awry in my keyring
>> database.
>> 
>> I can see all the records, but if I try to access one of them, Keyring
>> crashes. 
>
> Does it happen for all records, or only for one record?

All the ones I've tried.

>> I type in my password, and it validates (because if I have a 
>> typo it tells me that the password is wrong), but it crashes in
>> "MemoryMgr.c, Line:3645, NULL handle".  I have to pin-reset at this
>> point.
>
> The error message doesn't really help :(

That would be PalmOS.  I assume that some data corruption is causing
the decrypt routine to run off the end of the record into pointer lala
land.

>> If I install Keyring (and the libs) on freshly-hard-reset Palm, it
>> lets me create a new password and new records fine.  But if I restore
>> the Keys-Gtkr.pdb file, I get the error again.
>
> There is one known problem, which I currently don't fully
> understand. The HotSync Backup seems to merge the database from the
> Palm with that on the PC and apparently it can lead to a weird
> problem: If the password has been changed on the palm the old
> password verification hash is still kept on the PC.  After restoring
> from the backup it may happen that only the old password is accepted
> as valid, but that password decrypts the entries to garbage.  I'm
> currently testing a small java program to remove the password
> verification hash from the database, see
> http://gnukeyring.sf.net/keyring-recover/
>
> Do you think this could be the problem, i.e. is keyring only accepting an
> old password?

I haven't changed the password, and I'm using pilot-xfer under Linux
rather than Palm Desktop, so I don't think that's the problem.

Reading the contents of the jarfile at the above URL, it looks like
your just working at the Palm record level.  Perhaps your Java app
could be extended to decrypt the data given the password?  If so it
could probably give me more informative error messages than Keyring
can.

Ian