[1254] in Release_7.7_team
Re: ssh and access_on
daemon@ATHENA.MIT.EDU (Thomas Bushnell, n/BSG)
Wed Apr 15 10:51:17 1998
Date: Wed, 15 Apr 1998 10:51:12 -0400
From: tb@MIT.EDU (Thomas Bushnell, n/BSG)
To: jweiss@MIT.EDU
Cc: release-team@MIT.EDU
In-Reply-To: Jonathon Weiss's message of Wed, 15 Apr 1998 00:04:54 EDT
<199804150404.AAA16144@the-other-woman.MIT.EDU>
From: Jonathon Weiss <jweiss@MIT.EDU>
Date: Wed, 15 Apr 1998 00:04:54 EDT
So, it occured to me that ssh is going to behave in a somewhat
non-intuitive fashion in 8.2. Namely is won't be affected by
access_on and access_off (since it is run stand alone and not out of
inetd.) The main effect here is that on a public ws access_on won't
turn on ssh. However this means that on a machine that is normally
run as access_on, but not mkserv remote, access_off won't turn it off.
I understand that there are some significant efficiency issues about
key generation when running it out of inetd rather than stand alone,
so that may not be a great idea. Thoughts?
My first and only thought is to modify sshd to pay attention to the
access_on/off state itself. That requires modifying it, which is a
serious negative as well.