better to reign in hell than serve in heaven (part 2)

i am writing (er, have written) a php interface to the memopad palm database, much like my calendar reads from a palm calendar database. it already supports viewing, editing, deleting, undeleting, and creating new memos.

to make it complete, though, it needs a coldsync conduit to merge records edited through the interface with those modified on my treo.

i've already been using it to replace all of the random text documents i have in ~/documents/ but the problem of encryption keeps whispering in my ear. i can encrypt the entire database file and use the web interface login password as the key, but it would need to be decrypted during a hotsync and that would require the key to be stored in plaintext somewhere on the server.

or i could keep the database encrypted and push it to the palm that way, but then it wouldn't be readable by the memo pad application, so that would have to be replaced...

i tried memo safe but it broke navigation by the 5-way button on the treo, so that's a huge problem. it also uses "the SAFER-SK public domain block-cipher" which i've never heard of.

the other is cryptopad which is gpl'd but doesn't seem to have any releases anywhere...