- Timestamp:
- 05/19/05 18:52:16 (20 years ago)
- Location:
- pykota/trunk
- Files:
-
- 2 modified
Legend:
- Unmodified
- Added
- Removed
-
pykota/trunk/FAQ
r2146 r2260 38 38 It's probably best to do this : 39 39 40 $ chown pykota.pykota pykota.confpykotadmin.conf41 $ chmod 640 pykota.conf42 $ chmod 600 pykotadmin.conf40 $ chown pykota.pykota ~pykota/pykota.conf ~pykota/pykotadmin.conf 41 $ chmod 640 ~pykota/pykota.conf 42 $ chmod 600 ~pykota/pykotadmin.conf 43 43 44 44 Then the user 'pykota' will be the only PyKota Administrator … … 47 47 like repykota. 48 48 49 But on some systems, the following may be needed instead : 50 51 $ chown lp.pykota pykota.conf pykotadmin.conf 52 $ chmod 640 pykota.conf 53 $ chmod 640 pykotadmin.conf 54 49 55 * How can I limit my users to N pages per day (month/year) ? 50 56 -
pykota/trunk/SECURITY
r2146 r2260 49 49 Debian you may want to do : 50 50 51 $ chown pykota.pykota pykota.confpykotadmin.conf52 $ chmod 640 pykota.conf53 $ chmod 600 pykotadmin.conf51 $ chown pykota.pykota ~pykota/pykota.conf ~pykota/pykotadmin.conf 52 $ chmod 640 ~pykota/pykota.conf 53 $ chmod 600 ~pykota/pykotadmin.conf 54 54 55 55 Depending on your needs, you may want to put the user the printing … … 58 58 For example : 59 59 60 $ chmod 640 pykotadmin.conf60 $ chmod 640 ~pykota/pykotadmin.conf 61 61 $ adduser lp pykota 62 62 (this makes user 'lp' a member of group 'pykota') 63 63 64 Another solution, needed on some systems : 65 66 $ chmod a+rx ~pykota/ 67 $ chown lp.pykota ~pykota/pykota.conf ~pykota/pykotadmin.conf 68 64 69 Letting any user read PyKota administrator's configuration file may 65 70 expose passwords or database information which would allow write