summaryrefslogtreecommitdiff
path: root/doc/plugins
diff options
context:
space:
mode:
authorhttp://schmonz.livejournal.com/ <http://schmonz.livejournal.com/@web>2008-07-29 21:45:17 -0400
committerJoey Hess <joey@kitenet.net>2008-07-29 21:45:17 -0400
commit6838f9b6e5fb39a307eef3f7eea20497d4398f8b (patch)
tree7318fa1904bd91010ccb6deb87b37eb9314688c9 /doc/plugins
parent054a98647f208864bf1c14b35280255508c8e1f5 (diff)
Diffstat (limited to 'doc/plugins')
-rw-r--r--doc/plugins/contrib/unixauth/discussion.mdwn2
1 files changed, 2 insertions, 0 deletions
diff --git a/doc/plugins/contrib/unixauth/discussion.mdwn b/doc/plugins/contrib/unixauth/discussion.mdwn
index 162e5d323..5f542745d 100644
--- a/doc/plugins/contrib/unixauth/discussion.mdwn
+++ b/doc/plugins/contrib/unixauth/discussion.mdwn
@@ -15,3 +15,5 @@ all of which require taking the lock.
So I don't think I'll be accepting this plugin into ikiwiki itself..
--[[Joey]]
+
+Thanks for the comments. That's definitely an undesirable interaction between pwauth and ikiwiki; in my current application it wouldn't be a serious problem, but I'd like this plugin to be general-purpose and safe enough for inclusion in ikiwiki. It's the system-users-are-wiki-users idea I'm married to here, not pwauth itself; can you suggest another approach I might take?