<br><br><div><span class="gmail_quote">On 6/27/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;">
<br>PMWiki passwords=user unknown.<br><br>Well, not exactly... you could still set author required variable<br>(I forget out to do that and can't find the variable<br>name in the docs any more...).<br>which at least forces authors to enter something.
</blockquote><div><br> </div><br><div>Here's my passwords section (except for configuring uploads, which are below this section)<br><br>// Site passwords<br><br> $PmWikiAdmin = crypt('myadminpassword');
<br> $PmWikiUser = crypt('mysitewideuserpassword');<br> $DefaultPasswords['admin'] = $PmWikiAdmin;<br> $DefaultPasswords['attr'] = $PmWikiAdmin;<br> $DefaultPasswords['edit'] = $PmWikiUser;
<br> $HandleAuth['source'] = 'edit';<br> $HandleAuth['diff'] = 'edit';<br> ##example array of passwords for syntax reference<br> # $DefaultPasswords['whatever'] = array(crypt('alpha'), crypt('beta'));
<br><br> //Require author name - <a href="http://www.pmwiki.org/wiki/Cookbook/RequireAuthor">http://www.pmwiki.org/wiki/Cookbook/RequireAuthor</a><br> $EnablePostAuthorRequired = 1;<br><br> //Author cookie<br> include_once("$FarmD/scripts/author.php");
<br> if($AuthId && !@$_COOKIE[$AuthorCookie]) {<br> $Author = $AuthId; setcookie($AuthorCookie,<br> $Author, $AuthorCookieExpires, $AuthorCookieDir); } </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
They could of course mask their true identity. Or someone who got<br>hold of a password could spoof a trusted user's identity.<br><br>So then the question becomes: can one live<br>without being absolutely certain of the author?
<br><br>I guess the easy path forward is to start with PMwiki passwords only and<br>then<br>see if a real "business case" emerges that mandates strict user<br>authentication.</blockquote><div><br>That's been my approach, and so far such a case hasn't emerged for me.
<br></div><br></div>