27 | | If you protect access to printquota.cgi with user+password |
28 | | authentication, the REMOTE_USER CGI environment variable |
29 | | is honored, so an user can only see his own quota report, but |
30 | | not other users' quota. |
| 27 | If you protect access to printquota.cgi or dumpykota.cgi with |
| 28 | username+password authentication, the REMOTE_USER CGI environment variable |
| 29 | is honored, so an user can only see his own datas, but not |
| 30 | other users' datas. However, the special REMOTE_USER value 'root' |
| 31 | is allowed an unrestricted access. |
32 | | To make dumpykota.cgi work, you have to ensure that your web server |
33 | | runs it as a PyKota administrator. This means that dumpykota.cgi |
34 | | when run must be able to read the pykotadmin.conf file. There are |
35 | | several ways to do so, one of them is to put the user your web |
36 | | server normally runs as into the pykota group (which must be allowed |
37 | | to read pykotadmin.conf), then restart your web server : |
38 | | |
39 | | $ adduser www-data pykota |
40 | | $ /etc/init.d/apache restart |
41 | | |
42 | | This is probably not the safest way though, so you may want to |
43 | | restrict access further with an username and password, or use |
44 | | Apache's suExec mechanism to directly run this particular |
45 | | script as the pykota system user. Please refer to your web |
46 | | server's documentation for details. |
47 | | |
| 33 | If no username+password authentication takes place, then access |
| 34 | is completely unrestricted. |
| 35 | |
| 36 | You must ensure that the user your web server runs as can read |
| 37 | PyKota's pykota.conf configuration file. No read access to |
| 38 | PyKota's pykotadmin.conf configuration file is necessary though. |
| 39 | |