Re: sydo (aka "users want control. tto)... epilogue...

["Robert G. Brown" <bob@xxxxxxx>]

Folks -
  I was reluctant to use sudo to solve the problem I discussed yesterday, 
about permitting a user to control print jobs without having root access,
since I felt that sudo was a hack. Perhaps at one time, sudo was a hack, 
but I downloaded anyway late yesterday and tinkered with it late last 
night.

  It seems to me that sudo is NOT a hack, and effectively solves the print 
serve problem. This is a robust and secure enough tool for this purpose. 
The configuration of sudo permits the administrator to authorize a single
source-user, target-user, executable combination, without any blanket 
permissions or gross changes in the users environment. Of course, the 
configuration can be messed up to be too permissive, but careful config-
uration an use of sudo looks like a Good Thing to me....

   Thanks to Wes for suggesting this, and to Steve Scherbinski for 
reinforcing that. I did write my own, very simple configuration file, but
the infor is welcome in any case.


                                                              Regards,
                                                              ---> RGB <---