[1626] in NetBSD-Development

home help back first fref pref prev next nref lref last post

Re: important quirks of NetBSD 1.3 Athena

daemon@ATHENA.MIT.EDU (Karl Ramm)
Wed Mar 18 18:17:53 1998

To: Greg Hudson <ghudson@MIT.EDU>
Cc: peeto de la noche <gamache@MIT.EDU>, netbsd-dev@MIT.EDU
From: Karl Ramm <kcr@MIT.EDU>
Date: 18 Mar 1998 18:17:45 -0500
In-Reply-To: Greg Hudson's message of Wed, 18 Mar 1998 13:50:14 EST

Greg Hudson <ghudson@MIT.EDU> writes:
> > 2. the system is set to be a public workstation by default (in /etc/athena/
> >    rc.conf).  this is probably not the best setting...
> 
> We did this for consistency with other Athena platforms.  If you
> install a Sun, for instance, it comes up as a public machine.  Of
> course, that's because Cluster Services has a requirement which isn't
> true of NetBSD-Athena, but I still like the consistency aspect.  After
> the next system packs rebuild people should be able to just do "mkserv
> remote" to make their machines private.

Also, we did this to handle the people who just want single user athena
workstations in their rooms and don't think about the fact that people can
log into them remote and break into them and sniff the network
etc. etc. etc.

Not that I know that anyone who's using NetBSD right now thinks of them
that way but I was given the impression in the net-defense meeting last
semester that a lot of linux users do, and I definitely got the impression
that having sipb-athena machines access_off by default, requiring that
remote access be deliberately enabled would be a good thing.

kcr

home help back first fref pref prev next nref lref last post