As an addendum, the client who requested this feature found this link to an equivalent feature written in Ruby. Seems to me this could be done client side (presuming there is some sort of cryptology library available for javascript) but it could also be done as a python process. Will do more research and get back to the group.
Vincent On Jul 31, 2:01 pm, cobwebsmasher <[EMAIL PROTECTED]> wrote: > This is something I hadn't thought would be useful, as I think there are > plenty of workarounds to get a similar effect, but I wanted to know what the > group thought of this idea: > > Encryptable Wiki pages that can only be unlocked by either a specific > password and/or a specific username/password combination. > > Client wants a place to store usernames/passwords, but doesn't want to store > it on a wiki as you could work around the wiki to get the information. I've > suggested just placing a zip file with a password as an attachment on the > wiki, but he really wants this notion of an encryptable wiki --- it's stored > in the database encrypted so that only users with a specific password can > read what it's saying. > > I guess you could rig up an AJAX DOM sweep that took a given document through > some form of reversible encryption, but I have no idea how secure one can > make any reversible encryption scheme if, at the end of the day, a password > is involved. > > Thoughts on the idea and possible implementation? > > Thanks, > > Vincent > > --------------------------------- > Got a little couch potato? > Check out fun summer activities for kids. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~----------~----~----~----~------~----~------~--~---
