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 1NHR3E-0005BI-M8 for garchives@archives.gentoo.org; Mon, 07 Dec 2009 00:02:04 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D3D08E07FC for ; Mon, 7 Dec 2009 00:02:03 +0000 (UTC) Received: from ey-out-1920.google.com (ey-out-1920.google.com [74.125.78.150]) by pigeon.gentoo.org (Postfix) with ESMTP id A75A0E0835 for ; Sun, 6 Dec 2009 22:23:31 +0000 (UTC) Received: by ey-out-1920.google.com with SMTP id 3so207856eyh.40 for ; Sun, 06 Dec 2009 14:23:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:reply-to:to:subject:date :user-agent:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=fyvn5zIIl2IQaTdyGWZe8oD3xrHQ2FFXCtC2L4q5TQg=; b=AvmF7hZ6b8pklY7uzNYZNQH0dRe1+K1i/s/awEiDXgdnXSzEFKOyjQN37tMElRAmhI WwGeWS8JrkISfa8qqD56l4h9XfuLSSBt6Z3Mfwu9sH6jcKkLiG0PyRUquoRQo3HIt9QB HvGS7RVHCzUkmc3Fd/MYw65YThRmgGITOZHsk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; b=xkAoNloFhr47yQn9pOh0C3MuKc4BLy3zGTcRD9myqQ5WyMr8G/BMp0V+clh5IKVsB9 EvdTQ4SgcsCqg5NQU97YJTvlX8tUnHnJW8iFm0JtE0o7vMYAeYuspKftn0+pRQ+sG4nI Ys2FXbUEZ27R4eTR5Y68eo94DHM6ET5jerAnU= Received: by 10.213.0.144 with SMTP id 16mr6240564ebb.37.1260138182681; Sun, 06 Dec 2009 14:23:02 -0800 (PST) Received: from lappy.localnet (230.3.169.217.in-addr.arpa [217.169.3.230]) by mx.google.com with ESMTPS id 7sm8283596eyb.26.2009.12.06.14.23.01 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 06 Dec 2009 14:23:02 -0800 (PST) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Problems setting up sshd on an installation kernel Date: Sun, 6 Dec 2009 22:22:49 +0000 User-Agent: KMail/1.12.1 (Linux/2.6.31-gentoo-r6; KDE/4.3.1; i686; ; ) References: <20091206144836.GA2599@muc.de> <200912061628.26669.michaelkintzios@gmail.com> <20091206202338.GC2599@muc.de> In-Reply-To: <20091206202338.GC2599@muc.de> 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: multipart/signed; boundary="nextPart3648454.nz7T4A97sW"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200912062222.59975.michaelkintzios@gmail.com> X-Archives-Salt: 0270a6c9-7efc-44bb-80a0-e7008e254a6a X-Archives-Hash: 515e1da4b35847fd0a4309ec3a2e4357 --nextPart3648454.nz7T4A97sW Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On Sunday 06 December 2009 20:23:39 Alan Mackenzie wrote: > Hi, Mick, >=20 > 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? >=20 > 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. I was trying to take out of the equation user access issues.=20 > > Alternatively, check /etc/ssh/sshd_config to see if root logins are > > disabled as a default. >=20 > They are explicitly permitted. I set up sshd_config myself. OK > > While you're there you may also/first want to disable pam for ssh just = in > > case it interferes with the root login. >=20 > Er, pam? That's when my ssh client prompts me for my pass phrase, isn't > it? No, it's when it asks/expects a user passwd which I wasn't sure that you se= t=20 up beforehand. Typically, one would create a user and set up passwd both for user and root= =20 locally, then start screen as the user and detach it, login remotely with s= sh=20 and chroot from that point on. If as you said in previous message you are= =20 trying to do this from within the chrooted environment then things may be m= ore=20 complicated. I can't recall ever trying that to know how or why it fails. =2D-=20 Regards, Mick --nextPart3648454.nz7T4A97sW Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (GNU/Linux) iEYEABECAAYFAkscLsMACgkQVTDTR3kpaLY8OACg1yyaH35tYwAeOM3rXw21ksKc TFoAn0Wtm7w64m6Vyhf/Um4m03yMfcPb =Kofk -----END PGP SIGNATURE----- --nextPart3648454.nz7T4A97sW--