🚀 go-pugleaf

Ken Trant (trant@shire.corp.sgi.com) wrote:
: >As has been discussed here every time this has come up (and as Vernon
: >mentioned in this same thread), the best thing would be to have a script
: >that runs after install, similarly to the autoconfig and confmsg scripts,
: >that asks the user if they want to setup a secure system, and walks them
: >through it in a script.  That may still happen for a future release.
: Running COPS would give you a very good jump start to securing a system,
: it is in the public domain, and runs on SGI systems.

Not without considerable fussing, so it won't help those who don't know
enough to look at the unsecured-by-default accounts in /etc/passwd. It is
most appropriate as an organizer and periodic checker of the multiple
security concerns with which it deals. If you only want to check your system
once, just set up COPS and test it thoroughly, in the process of which you
will find all your security problems, and then delete it. :-)

I too would like to see a security-conscious script a la autoconfig,
'versions changed', and friends.

Cheers,

--
| Dave Schweisguth   Yale MB&B & Chemistry   Net: dcs@neutron.chem.yale.edu |
| Lab phone: 203-432-5208     Fax: 203-432-6144    Home phone: 203-624-3866 |
| For complying with the NJ Right To Know Act:  Contents partially unknown. |