TiddlerEncryptionPlugin is not quite what you are looking for, but, may do the job.
http://www.remotely-helpful.com/TiddlyWiki/TiddlerEncryptionPlugin.html The Tiddler contents is encrypted and tagged with a 'prompt'. You enter the password that corresponds to the prompt and the tiddler contents are decrypted. If a tiddler has a different prompt, then you can give it a different password. Settings include not caching the password, so every tiddler you want to see, you have to re-enter the password. Tiddlers are automatically encrypted, and a password prompted for, if you create a new tiddler with a prompt that has not had a password entered before. Basically, you simply give different prompts to different tiddlers and distribute the passwords appropriately. If someone does not have the password to a prompt, they cannot read the contents. Feel free to contact me for further details. ...Lyall Lyall at remotelyhelpful dot com On May 17, 3:03 am, "Mark S." <[email protected]> wrote: > GPG wants to flip around 1024 bit numbers. I suspect that is a bit > much to ask from a scripting language like js. And why the existing > encryption plugin uses a much simpler algorithm. > > Maybe something like TiddlyWeb could access gpg code on the local > server to do the heavy work of converting RSA and IDEA encrypted text > into plain text. But then how it would it send it? Maybe via a 128 bit > https/ssl channel. > > If you're not guarding state secrets, why not just use the existing > encryption plugin, and send the password to everyone that you want to > access it? PGP/GPG is neat, but its most useful when you don't have a > secure method of distributing password keys. If you have a method, > then maybe its just an extra layer of complexity. > > -- Mark > > On May 15, 1:22 am, 9600 <[email protected]> wrote: > > > Hello, > > > I'd like to be able to store root passwords and the like in a > > TiddlyWiki, and access to be controlled via GnuPG (PGP) keys. So end > > users would store their private keys locally and the sensitive data > > would be encrypted using the public keys of only those users you want > > to provide access to. > > > Ideally you would be able to cache all the public keys in the > > TiddlyWiki and thus when encrypting be able to simply select which > > users to give access to. However, you would of course not want to have > > the user's private key persisted in the TiddlyWiki, and just have this > > loaded when needed and remove from memory afterwards. > > > Whether the data is an element of a tiddler or a entire tiddler > > probably doesn't matter. > > > Other desires include: > > > - Being protected from scripting attacks and malicious plug-ins that > > would result in the private key being compromised. > > - Being suitable for deploying on top of TiddlyWeb. > > > Does anyone know if any work has been done to support this sort of use > > case? > > > Cheers, > > > Andrew --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" 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/TiddlyWiki?hl=en -~----------~----~----~----~------~----~------~--~---
