:
:[EMAIL PROTECTED] wrote:
:> I'm afraid I don't understand your point. If without-password
:> makes sshd useful to a larger subsection of users without effecting
:> security on the original subsection, why wouldn't you want to make
:> the change? Just because it may not make a difference for YOU doesn't
:> mean that it wouldn't be a useful change to make.
:
:But it *can't* make it useful to any more users. How do you get the
:authorized-hosts file updated? You edit it. How do you get the
:configuration changed to without-password from none? You edit it.
:
:Same work, no obvious advantage to without-password over no, and better
:obvservance of "install in the most secure way possible". Just like
:the discard port is disabled in inetd.conf -- same concept.
:
:--
:Steve Watt KD6GGD PP-ASEL-IA ICBM: 121W 56' 57.8" / 37N 20' 14.9"
I see. And at what point does editing N files make it 'easier'? 4? 5?
If we were to cut the number of files you had to edit to get X to work
from 5 to 3 would that be worthwhile enough to do a commit? What
exactly are you arguing here? Because I don't see it.
Frankly I think being able to go from 2 files to 1 to get something done,
like creating an authorized_keys file for root, is well worth the commit
if there are otherwise no downsides. I don't see any downsides to doing
this except for a few people who seem to be arguing that status-quo is
better then fixing something even if fixing that something has absolutely
no effect on them.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
