On 11/20/2009 at 12:06, Per Jessen <per@opensuse.org> wrote: DenverD wrote:
Per Jessen wrote:
why do I have to explicitly enable ssh during installation? In previous releases, sshd was always active. To anyone with more than one box, sshd is a must - to anyone with only one box, it doesn't do any harm.
makes the default install more secure if ftpd, sshd and all others are not running...maybe?
on the other hand, i'm happy they did since i always had to disable sshd..
I guess you're a one-PC kind of guy :-)
so, the default install can't possibly make everyone happy...
Yes, that's very true. What I'd like know is still why sshd was disabled when security has not become more of an issue than it was in the previous umpteen releases since 7-something.
Interestngly enough, before the sshd deamon might have been started, but the firewall port 22 was not opened. From previous mails of yours I understand that you always switch off the firewall and as such might just not have realized it. But starting the sshd daemon with the port blocked is useless and the users requiring access either had to disable the FW or reconfigure it. Now, the user has to enable ssh if he needs it (which, IIRC, also opens the port 22 now). Per, you're a very active user. But do you consider yourself part of the largest group openSUSE is targeting? Not all settings are right for you, not all are right for me. Nevertheless, apparently my sister did not have any troubles with them (she would not even know what she can do with this s-s-h whatever thingy...). Additionally, people are always pushing to faster boot times. Disabling the not obvious needed services to achieve it is certainly not wrong. (Think about desktop computers, not servers; even there, you will probably get a higher ratio of desktop:server) Dominique -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org