On Sunday 16 September 2007 18:01:48 Alexander Skwar wrote:
Key words in some circumstances.
Like?
Actually, I never found this to be true.
Never? Good for you.
Grant, the original poster would disagree (who got himself locked out due to
the inability to restart sshd BTW), and so would I
Hi,
On Sun, 16 Sep 2007 22:25:07 +0200 Alexander Skwar
[EMAIL PROTECTED] wrote:
A /etc/init.d/sshd stop won't kill any SSH sessions. It'll
simply the sshd master process. Because of that, additional
logins won't be possible.
An /etc/init.d/sshd stop/restart can very well fail. Depending on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hans-Werner Hilse wrote:
Hi,
Hi!
So I would definately prefer to always have a guaranteed working sshd
running (I find OpenVPN/telnet a bit strange and an unnecessary
potential security hole).
If running permanently, then I agree, but I do
Hi,
On Mon, 17 Sep 2007 12:56:16 -0300 Arturo 'Buanzo' Busleiman
[EMAIL PROTECTED] wrote:
So I would definately prefer to always have a guaranteed working
sshd running (I find OpenVPN/telnet a bit strange and an unnecessary
potential security hole).
If running permanently, then I agree,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hans-Werner Hilse wrote:
I just prefer manual opening of access means above manual securing
them. It's just about what happens if you fail -- when the task was
securing, you might have a security leak, but if it was openiung
access, it is still
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Alexander Skwar wrote:
A /etc/init.d/sshd stop won't kill any SSH sessions. It'll
simply the sshd master process. Because of that, additional
logins won't be possible.
You seem to believe that most people makes no mistakes. I wouldn't need
6 matches
Mail list logo
