1 |
Killing the ssh daemon does not effect any of the existing |
2 |
connections. The ssh daemon is used to listen for new connections and |
3 |
create a process to handle communications with that request. That is |
4 |
why when you update configuration parameters for sshd, they do not |
5 |
take effect until the next connection. |
6 |
|
7 |
The problem with connecting to the server via telnet is that your |
8 |
password can be easily intercepted - which is one of the major reasons |
9 |
telnet has been depreciated. |
10 |
|
11 |
-Stephen |
12 |
|
13 |
On 9/10/07, Arturo 'Buanzo' Busleiman <buanzo@××××××××××.ar> wrote: |
14 |
> -----BEGIN PGP SIGNED MESSAGE----- |
15 |
> Hash: SHA512 |
16 |
> |
17 |
> Grant wrote: |
18 |
> > Should I: |
19 |
> > kill -9 2988 && /etc/init.d/sshd start |
20 |
> > Are you sure? :) |
21 |
> |
22 |
> Sounds scary to kill sshd remotely, specially over ssh :P |
23 |
> |
24 |
> That's why I usually have a telnet server up during ssh upgrade times. |
25 |
> |
26 |
> |
27 |
> - -- |
28 |
> Arturo "Buanzo" Busleiman - Consultor Independiente en Seguridad Informatica |
29 |
> Servicios Ofrecidos: http://www.buanzo.com.ar/pro/ |
30 |
> Unase a los Foros GNU/Buanzo - La palabra Comunidad en su maxima expresion. |
31 |
> -----BEGIN PGP SIGNATURE----- |
32 |
> Version: GnuPG v1.4.7 (GNU/Linux) |
33 |
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
34 |
> |
35 |
> iD8DBQFG5Yd+AlpOsGhXcE0RCqCvAJ46Spe77Qukj5oYjCAtBK4lO0cZ4QCcCm24 |
36 |
> U/zSADTHUKzZZ/G2dkZZkbo= |
37 |
> =5uQv |
38 |
> -----END PGP SIGNATURE----- |
39 |
> -- |
40 |
> gentoo-user@g.o mailing list |
41 |
> |
42 |
> |
43 |
-- |
44 |
gentoo-user@g.o mailing list |