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

[Eddie M. <la...@he...>]

Jochen Hoenicke wrote:
> I would say, finish the one for version 1.2.3 first and then start supporting
> the new format.  Does the xml file store the data in encrypted form?  As I
> understand it the hotsync is noninteractive so you can't decrypt the data,
> right?
> 
> You should have a version flag in XML file to distinguish new and old format
> so you can support both.

Yes, it stores it as a base64 encoded version of encrypted portion of 
the record.

While technically it's possible to add dialogs during the sync process, 
it's not recommended as with network sync the user may be not access to 
the machine the hotsync process is running on.  And besides, I wouldn't 
want to save the data unencrypted anyway.

The only thing I'm need to figure out now is category syncing, the palm 
docs are bit unclear on it.  Record syncing is working great.

Then I need to finish my cmd line app that updates the xml file to 
support all the necessary functions; add/remove/edit categories, 
add/remove/edit records, change password, etc.  Most of the code is 
there, it's just coming up with a consistent option set and error checking.

I need to make an error checking/logging pass over the conduit too, so I 
should have a version stable enough for testing next week.

thanks,
Eddie
-- 
Eddie McCreary                  Outside of a dog, a book is a man's best
mailto:la...@he...       friend.  Inside of a dog, it's too dark
http://www.heorot.org           to read. -Groucho Marx