home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.sgi.admin:153 comp.sys.sgi:18633
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!howland.reston.ans.net!usc!cs.utexas.edu!sun-barr!ames!olivea!sgigate!odin!sgihub!zola!zuni!anchor!olson
- From: olson@anchor.esd.sgi.com (Dave Olson)
- Newsgroups: comp.sys.sgi.admin,comp.sys.sgi
- Subject: Re: security concerns revisted
- Message-ID: <ul1jj5c@zuni.esd.sgi.com>
- Date: 9 Jan 93 03:28:38 GMT
- References: <ui2dla0@zuni.esd.sgi.com> <C0GEH4.2KJ@helios.physics.utoronto.ca> <uij5h2g@zuni.esd.sgi.com> <1993Jan7.155721.7859@cs.wayne.edu> <1993Jan8.173044.10208@odin.corp.sgi.com>
- Sender: news@zuni.esd.sgi.com (Net News)
- Organization: Silicon Graphics, Inc. Mountain View, CA
- Lines: 23
-
- In <1993Jan8.173044.10208@odin.corp.sgi.com> trant@shire.corp.sgi.com (Ken Trant) writes:
-
- | >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.
-
- COPS does *nothing* in and of itself to secure a system. All it does
- is point to a series of (potential) problems that COPS already knows
- about.
-
- We are talking about a script that allows a customer at installation
- time (or later on) to actually configure the system to be reasonably
- secure (for more than "reasonably secure", buy our 'secure' version
- of the OS, called TIRIX).
- --
- Let no one tell me that silence gives consent, | Dave Olson
- because whoever is silent dissents. | Silicon Graphics, Inc.
- Maria Isabel Barreno | olson@sgi.com
-