From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1IUoNm-0007ND-5i for garchives@archives.gentoo.org; Mon, 10 Sep 2007 18:53:15 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.14.0/8.14.0) with SMTP id l8AIj0aU029781; Mon, 10 Sep 2007 18:45:00 GMT Received: from an-out-0708.google.com (an-out-0708.google.com [209.85.132.247]) by robin.gentoo.org (8.14.0/8.14.0) with ESMTP id l8AIdZUW023072 for ; Mon, 10 Sep 2007 18:39:36 GMT Received: by an-out-0708.google.com with SMTP id c8so185909ana for ; Mon, 10 Sep 2007 11:39:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; bh=92cgi1sey32Z+KBRL0rV67a1rAFuJAWmNFU7mYO1cWc=; b=JYlZa8pmhcUTLgLp4KQBpHBdzg/7xMp+3yV9y54KchtwYkwCVBR78WV5J/WcgFRsDKyLZX93ac1j75irWx2/POCvwesxDqPYT8gVNZcsi+RpqX9dr5h7o1KhB5+S2rSVhByWK72FjDkhwEopBongWSJ0/9cynw6vSgv75OUGfiQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=EIjtEvJ7NelP9uiy1NKHVf8fjzFhW+egRpH5NrKqON0heBtKT+0eLDniTOcnA64C3w9RfeE9deuXn77tvJGsnZ5qj0zwK1QTkXs1GZ+FqWeYsO3GE/x5GCQSEweB606w5snBZtQ6EvgSZGFomcaxItXPq6s2FPfE+OtOYHTCk+g= Received: by 10.100.174.16 with SMTP id w16mr4990949ane.1189449575392; Mon, 10 Sep 2007 11:39:35 -0700 (PDT) Received: by 10.100.95.6 with HTTP; Mon, 10 Sep 2007 11:39:35 -0700 (PDT) Message-ID: Date: Mon, 10 Sep 2007 13:39:35 -0500 From: "Stephen Wittig" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] SSH won't restart In-Reply-To: <46E5877E.1030702@buanzo.com.ar> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <49bf44f10709080840k4f64df08r1f3ba9a4e3b4f031@mail.gmail.com> <46E2E590.8030207@usa.net> <49bf44f10709100958jd3516d7tbdf5bf1e804f412f@mail.gmail.com> <46E5877E.1030702@buanzo.com.ar> X-Archives-Salt: b85b8796-1902-4582-a1cb-33d2b213aaca X-Archives-Hash: e290ff0c3d33c41e715b55d3b668f4b6 Killing the ssh daemon does not effect any of the existing connections. The ssh daemon is used to listen for new connections and create a process to handle communications with that request. That is why when you update configuration parameters for sshd, they do not take effect until the next connection. The problem with connecting to the server via telnet is that your password can be easily intercepted - which is one of the major reasons telnet has been depreciated. -Stephen On 9/10/07, Arturo 'Buanzo' Busleiman wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Grant wrote: > > Should I: > > kill -9 2988 && /etc/init.d/sshd start > > Are you sure? :) > > Sounds scary to kill sshd remotely, specially over ssh :P > > That's why I usually have a telnet server up during ssh upgrade times. > > > - -- > Arturo "Buanzo" Busleiman - Consultor Independiente en Seguridad Informatica > Servicios Ofrecidos: http://www.buanzo.com.ar/pro/ > Unase a los Foros GNU/Buanzo - La palabra Comunidad en su maxima expresion. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.7 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFG5Yd+AlpOsGhXcE0RCqCvAJ46Spe77Qukj5oYjCAtBK4lO0cZ4QCcCm24 > U/zSADTHUKzZZ/G2dkZZkbo= > =5uQv > -----END PGP SIGNATURE----- > -- > gentoo-user@gentoo.org mailing list > > -- gentoo-user@gentoo.org mailing list