Hey Ville and anyone else who wants to comment, I've written a simple addition to stickynotes.py which provides an encrypted body text function.
The advantage of using stickynotes is that the unencrypted content is never written in a leo file, no matter when you save the file. I had an older version of this code which en/decrypted body nodes in place, and if you decrypt and then save the decrypted text is saved to the drive. stickynotes provides the layer that avoids that problem. Of course it might still be written to a swap file, etc. etc., I would trust this approach with my credit card number and site login details, but not missile launch codes :-} It relies on the python-crypto module, but behaves politely if that's not available. Does anyone object to this being in the stickynotes.py plugin? It's not much code, but I wonder if it's Feeping Creaturism? Cheers -Terry
-- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
