Hi Terry, thanks for your answer, sure I have the crypto module on both sides.
Maybe it is an issue with the textual encoding of the key (ascii vs. utf or something like this). I have no access to the other host (ubuntu) until next year. So I cannot do too much tests until then. If I find out more on this issue, I will let you know if you dont' mind. I would also like to have a standalone version of this stickynoteenv plugin, I tried to extract the code to a non-leo program, but did not have success on this either. Would be cool if you store the "password"-nodes to a file, i.e. via @nosent or @file or @auto, and have a sn_enc.py program to convert this encrypted file to plain text for quick access to your secret stuff (in case leo is not running) Cheers, Karl. On 16 Dez., 17:02, Terry Brown <[email protected]> wrote: > On Fri, 16 Dec 2011 06:53:04 -0800 (PST) > > resi147 <[email protected]> wrote: > > But unfortunatly > > found those not being platform independant, in my case between mac > > (home) and linux (work). > > I was wondering what could be the reason, because those encryption > > mechansismn should > > not depend on the operating system > > I wrote Stickynoteenc, and as the docs. say it requires the > python-crypto module. As long as you have that module installed on > both machines I can't see why it would be incompatible either. On both > machines try: > > from Crypto.Cipher import AES > > in the python console. Does it work on both? > > I'd like (a) to use a python standard library alternative if there is > one, presumably I decided there wasn't when I wrote it, years ago, and > (b) to be able to encrypt trees, not just node content. Sometime. > Maybe. > > 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.
