Re: [gnukeyring-discuss] Re: a conduit for hotsync, but...

[Jochen H. <hoe...@gm...>]

Hello Eddie,

On Apr 6, 2005 5:44 PM, Eddie McCreary <li...@he...> wrote:
> I'm finally at the boring but important part of fixing bugs and
> writing docs, however I'll be out of town fri-mon so it will probably
> be one more week before I can release something.
> 
> One issue I could use help on, the keys are cached on the PDA in I
> believe a db called Keys-Gtkr-Temp.  

That was before 1.1.  The problem was that the database with the key (the snib)
was actually copied to the PC.  Now the snib is held in some more
secure place.

> If I change the master password on
> the desktop and sync, I will get an exception because on the palm the
> program is still using the cached password.  If I set my timeout
> preference to zero this isn't an issue.

Yes, this is a known problem. I think it isn't too serious, because
1. there is only a warning that data cannot be encrypted and garbage 
   is displayed.  As soon as one locks the database and unlocks again 
   everything is fine.
2. The problem only occurs if the database was unlocked when a new
   database with a new password is synced.

With the new format in keyring-2.0 the problem won't occur any more.

> Any ideas on how to for the software on the PDA to reset it's cache?

I'm not sure what you can do from the conduit site. Starting keyring with
sysAppLaunchCmdAlarmTriggered or sysAppLaunchCmdTimeChange
should eradicate the snib immediately.

Regards,
  Jochen

-- 
Jochen Hoenicke, University of Oldenburg, 26111 Oldenburg, Germany
Email: hoe...@in...  Tel: +49 441 798 3124