Re: [gnukeyring-discuss] Is there a Keyring Hotsync conduit?

[Walters, R. H, JR (Bob) <bob...@al...>]

Disregard - hotsync was not set up to backup system files. 

-----Original Message-----
From: Walters, Robert H, JR (Bob) 
Sent: Monday, March 01, 2010 9:48 AM
To: 'Jochen Hoenicke'; gnu...@li...
Subject: RE: [gnukeyring-discuss] Is there a Keyring Hotsync conduit?

Thanks for the reply Jochen. I guess that's what's confusing me. I've installed Keyring on my Palm and added a few entries. I've done multiple hotsyncs since then but the Keys-Gtkr.PDB file on my computer still has a June 17, 2008 date on it so it does not appear to be getting updated from the Palm to the computer.

Bob

-----Original Message-----
From: Jochen Hoenicke [mailto:hoe...@gm...]
Sent: Friday, February 26, 2010 3:32 AM
To: gnu...@li...
Cc: Walters, Robert H, JR (Bob)
Subject: Re: [gnukeyring-discuss] Is there a Keyring Hotsync conduit?

Hello,

2010/2/25 Walters, Robert H, JR (Bob) <bob...@al...>:
> Is there supposed to be a hotsync conduit that gets automatically gets 
> installed when I install Keyring?  I've got Palm OS v5.2.1 and Palm 
> Desktop
> 4.1.4 on a Windows XP machine with HotSync manager 4.1.0. I see 
> mention of hotsyncing but there wasn't a conduit that got installed 
> when I installed Keyring version 1.2.3.

There is no conduit installed.  We rely on the HotSync manager to do a regular backup of the encrypted database.

There are some "conduits" on the page http://gnukeyring.sf.net/conduits.html
Note that these are standalone programs that can read the encrypted database Keys-Gtkr.pdb and show/edit/convert the records.  There is no tight integration into the HotSync manager.  Also the editing functionality should be used with great care.  Never edit the database on both PC side and palm side independently.

Regarding version,I think both keyring-1.2.3 and keyring-2.0pre6 are reasonable stable.  I used the latter for the last few years.  I never did a release without the pre, though.

The new version keyring-2.x uses a new database format, which is not supported by all conduits on the above site. This new format fixes a few minor flaws of the old format.  None of them is critical, though.
See
http://gnukeyring.sourceforge.net/crypto.html#sect3
for details. Keyring-2 will happily upgrade databases from keyring-1.2.3, but there is no simple way back.

BTW, for keyring-2, don't use the Cipher "No", as it does not encrypt at all.  I want to remove it from the final release.  Also some of the conduits don't support AES-256 for legal reasons.  For example the US export version of the Java Runtime Environment only allows AES with
128 bit keys.  You can always change the encryption method (Cipher) by setting a new password.

Regards,
  Jochen