Changeset 1087 for pykota/trunk/SECURITY

Show
Ignore:
Timestamp:
07/16/03 23:53:08 (21 years ago)
Author:
jalet
Message:

Really big modifications wrt new configuration file's location and content.

Files:
1 modified

Legend:

Unmodified
Added
Removed

  • pykota/trunk/SECURITY

    r1074 r1087  
    6363    PyKota and/or your printing system completely inoperative. 
    6464     
    65   - Ensure that no regular user can read PyKota's configuration file, 
    66     but that both the print quota administrator and the user the 
    67     printing system is run as can read it. Depending on your system's 
    68     configuration, this may give something like : 
     65  - Ensure that no regular user can read PyKota administrator's  
     66    configuration file, but that both the print quota administrator and  
     67    the user the printing system is run as can read it. Depending on  
     68    your system's configuration, this may give something like :  
    6969     
    70       $ chown lp.lpadmin /etc/pykota.conf 
    71       $ chmod 640 /etc/pykota.conf 
     70      $ chown lp.lpadmin /etc/pykota/pykotadmin.conf 
     71      $ chmod 640 /etc/pykota/pykotadmin.conf 
    7272     
    7373    If the print quota administrator is root then he will always be 
    7474    able to read PyKota's configuration file. 
    7575     
    76     Letting any user read PyKota's configuration file may expose 
    77     passwords or database information which would allow direct 
    78     connections to it if the user can write and execute his own 
    79     scripts or download and execute his own version of PyKota. 
     76    Letting any user read PyKota administrator's configuration file may  
     77    expose passwords or database information which would allow direct  
     78    connections to it if the user can write and execute his own scripts  
     79    or download and execute his own version of PyKota.  
    8080   
     81    If you want to let users generate their own print quota reports,  
     82    then ensure that /etc/pykota/pykota.conf is readable by 
     83    everyone, but writeable only by the root user : 
     84     
     85      $ chown root.root /etc/pykota/pykota.conf 
     86      $ chmod 644 /etc/pykota/pykota.conf 
     87       
    8188    NB : If you use the printquota.cgi CGI script, ensure that 
    8289         the user this script is run as (e.g. nobody or www-data) 
    83          can read PyKota's configuration file too, for example 
    84          by putting www-data in the lpadmin group. 
    85          WARNING : putting www-data in the lpadmin group so that 
    86          the CGI script can read the /etc/pykota.conf file is 
    87          dangerous. If any user can create CGI scripts launchable 
    88          as www-data then he could steal a copy of the /etc/pykota.conf  
    89          file and learn database and database users' name and passwords. 
    90          The best solution is probably to create a pykota system 
    91          account and run the CGI script as this user using Apache's SuEXEC 
    92          facility. Refer to Apache's documentation for details. 
     90         can read PyKota's configuration file /etc/pykota/pykota.conf 
     91         BUT can't read PyKota administrator's configuration file 
     92         /etc/pykota/pykotadmin.conf 
     93         Refer to Apache's documentation for details. 
    9394   
    9495  - Secure your database connection :