Check out the stickynote plugin. It has some support for encryption. I am not sure of its status at the moment though. It has been some time since I looked at it.
Chris On Mon, May 22, 2017 at 8:13 PM, Phaze <paranhasl...@gmail.com> wrote: > The absence of this feature is the only thing that is preventing me from > using leo as a password store > > It would be very cool if we could encrypt both the text and the structure > of nodes marked @encrypt and present a dialog box requesting the > key/password to decrypt and use the outline tree. The section in the > actual .leo file would need to be stored as encrypted text however as > simply having a password tacked on the node could be circumvented by > looking at the raw xml. > > Although it may not be state of the art, and is in many cases crackable > with patience, a Vigenère would be easy enough to implement. It would > also deter a casual snoop. > > If the option was also given to enforce the use of the leo users id as > part of the key/password it would also provide an additional level of > authentication/security. > > Just an idea > Paran > > > -- > You received this message because you are subscribed to the Google Groups > "leo-editor" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to leo-editor+unsubscr...@googlegroups.com. > To post to this group, send email to leo-editor@googlegroups.com. > Visit this group at https://groups.google.com/group/leo-editor. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
