| 1 |
[[!comment format=mdwn |
| 2 |
username="http://smcv.pseudorandom.co.uk/" |
| 3 |
nickname="smcv" |
| 4 |
subject="comment 1" |
| 5 |
date="2012-04-15T20:53:44Z" |
| 6 |
content=""" |
| 7 |
Read/view access and write/edit access are rather different. |
| 8 |
You can limit write access via wiki configuration, and even |
| 9 |
configure it over the web with [[plugins/websetup]]. |
| 10 |
|
| 11 |
The only way to limit read access is to restrict access to the |
| 12 |
entire wiki via `.htaccess` or other web server configuration, |
| 13 |
preferably combined with use of `https`. |
| 14 |
IkiWiki can't limit read access to pages on its own[*], |
| 15 |
because it's a wiki compiler: when a page is viewed, the web |
| 16 |
server serves the compiled HTML without IkiWiki being involved. |
| 17 |
|
| 18 |
The best way to integrate access control into IkiWiki would |
| 19 |
probably be to have a CGI user interface for `.htaccess` or |
| 20 |
equivalent - but you'd still have to be careful, because, |
| 21 |
for instance, if a user can edit public pages, then they |
| 22 |
can insert a `\[[!include]]` directive to make the content |
| 23 |
of a private page public. As a result, the safest way to |
| 24 |
use it is to keep public and private information in |
| 25 |
separate wikis. |
| 26 |
|
| 27 |
[\*] strictly speaking, it *could* via a new plugin, but |
| 28 |
that would defeat many of its advantages |
| 29 |
"""]] |