| 1 |
On Saturday 14 November 2009 21:32:39 Mick wrote: |
| 2 |
> > Approach security a little more sanely and don't give untrusted users |
| 3 |
> > root access? If you have to take steps to restrict the root account, |
| 4 |
> > you need to rethink who has use of it. Preventing damage in the event |
| 5 |
> > that the system does get compromised is one thing, but trying to |
| 6 |
> > control someone who is given access to root on the software side is |
| 7 |
> > the wrong approach, in my incredibly non-humble opinion. |
| 8 |
> |
| 9 |
> You are right of course, but in this particular case the guy who pays |
| 10 |
> wants to have root access. |
| 11 |
|
| 12 |
And you agreed to work like that? |
| 13 |
|
| 14 |
So when he fucks things up good royal and proper, will he gladly accept his |
| 15 |
shafting and pay you more to undo it? Or will he do the usual customer stunt |
| 16 |
and blame you? |
| 17 |
|
| 18 |
I only work under one of two conditions: |
| 19 |
|
| 20 |
I am root and the customer is not. |
| 21 |
The customer is root and I am not. |
| 22 |
|
| 23 |
> So, I'm just trying to find an easy way to |
| 24 |
> protect him from himself. Initially I implemented SELinux, but had to |
| 25 |
> pull that back because I couldn't in any quick way get Nagios cgi working |
| 26 |
> with it. One day I may find some time to get back to it. |
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
alan dot mckinnon at gmail dot com |
Archives