From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NHNYw-0000Tb-98 for garchives@archives.gentoo.org; Sun, 06 Dec 2009 20:18:43 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BABF2E07F2; Sun, 6 Dec 2009 20:18:08 +0000 (UTC) Received: from mail.muc.de (colin.muc.de [193.149.48.1]) by pigeon.gentoo.org (Postfix) with ESMTP id 42F84E07F2 for ; Sun, 6 Dec 2009 20:18:08 +0000 (UTC) Received: (qmail 91269 invoked by uid 3782); 6 Dec 2009 20:18:07 -0000 Received: from acm.muc.de (pD9E5395F.dip.t-dialin.net [217.229.57.95]) by colin2.muc.de (tmda-ofmipd) with ESMTP; Sun, 06 Dec 2009 21:18:06 +0100 Received: (qmail 7475 invoked by uid 1000); 6 Dec 2009 20:23:39 -0000 Date: Sun, 6 Dec 2009 20:23:39 +0000 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Problems setting up sshd on an installation kernel Message-ID: <20091206202338.GC2599@muc.de> References: <20091206144836.GA2599@muc.de> <200912061628.26669.michaelkintzios@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200912061628.26669.michaelkintzios@gmail.com> User-Agent: Mutt/1.5.9i X-Delivery-Agent: TMDA/1.1.5 (Fettercairn) From: Alan Mackenzie X-Primary-Address: acm@muc.de X-Archives-Salt: 983d2e8e-6045-47a1-9f92-50ba12835cca X-Archives-Hash: 1a0b76e5b6461440215f119a5002ff40 Hi, Mick, On Sun, Dec 06, 2009 at 04:28:10PM +0000, Mick wrote: > On Sunday 06 December 2009 14:48:36 Alan Mackenzie wrote: > > Is there anything I can do to get sshd working from this kernel (and > > if so, what?), or is there something fundamentally wrong with the > > kernel configuration? > Not sure if this is a kernel problem. Have you tried to set up a user > account and passwd then login as a plain user over ssh and then su to > root? No. Could that make a difference? It is prompting me for my key's passphrase and accepts it; it is failing to create a pseudo terminal. > Alternatively, check /etc/ssh/sshd_config to see if root logins are > disabled as a default. They are explicitly permitted. I set up sshd_config myself. > While you're there you may also/first want to disable pam for ssh just in case > it interferes with the root login. Er, pam? That's when my ssh client prompts me for my pass phrase, isn't it? > Regards, > Mick -- Alan Mackenzie (Nuremberg, Germany).