<br><br><div><span class="gmail_quote">On 6/24/07, <b class="gmail_sendername">Sivakatirswami</b> <<a href="mailto:katir@hindu.org">katir@hindu.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Patrick R. Michaud wrote:<br>> On Wed, Jun 20, 2007 at 09:52:13AM -1000, Sivakatirswami wrote:<br>>> read and edit<br>>> passwords are not displayed... we only see four **** in each field<br>>> where we were expecting to view the actual passwords displayed.
<br>><br>> PmWiki doesn't have the cleartext passwords anywhere -- it<br>> only stores encrypted versions. </blockquote><div><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I see, hmmm, makes sense, you don't want to open a hole<br>to hack out passwords as clear text. OK understood, that<br>could be a serious problem. So, you just keep that door shut.<br><br>So then, obviously, admin is left with the manual task
<br>of tracking the passwords for each group and which users<br> have been given those passwords.<br><br>I would be interested in how other admins do this or if there<br>are any "best practices" recommendations...
<br><br>A simple text file on one's own box?<br>A protected page on the wiki?</blockquote><div><br>Good question -- I'd be interested in hearing what others do, too. I have an Admin wikigroup, which requires an admin password to read. One of its pages contains the following:
<br><br>(:table class=tabtable padding=5px:)<br>(:cell width=40%:)<br>Here's a list of groups on the site<br>(:pagelist fmt=group list=all group=-PmWiki,-Admin,-Site:)<br>(:cell width=60%:)<br>Maintain a manual list here of groups, pages and passwords
<br>* '''Site-wide''' admin=admin-levelpassword; read/edit/upload=user-levelpassword<br>* Group [[ExampleGroup1(.HomePage)]] read=firstpasswordexample; read/edit/upload=secondpasswordexample<br>* Page [[ExampleGroup2/ExamplePage]] read= pw1 pw2 pw3; read/edit/upload=pw4 pw5
<br>(:tableend:)<br><br> I highly doubt this could be considered a "best practice".<br></div></div>