From: Joshua Murphy <poisonbl@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Problems setting up sshd on an installation kernel
Date: Sun, 6 Dec 2009 16:31:14 -0500 [thread overview]
Message-ID: <c30988c30912061331x3da6a455w843b72a93b11612c@mail.gmail.com> (raw)
In-Reply-To: <20091206183639.GA7431@waltdnes.org>
On Sun, Dec 6, 2009 at 1:36 PM, Walter Dnes <waltdnes@waltdnes.org> wrote:
> On Sun, Dec 06, 2009 at 02:48:36PM +0000, Alan Mackenzie wrote
>> Hi, folks!
>>
>> I'm trying to get sshd working on an embryonic Gentoo installation on my
>> laptop. The reason is that I want to ssh from my nice comfy desktop
>> system into this laptop to do the rest of the installation stuff.
>>
>> The installation kernel with which I'm having problems is:
>> Linux livecd 2.6.30-gentoo-r8 #1 SMP Tue Nov 3 11:40:51 UTC 2009.
>>
>> Having started sshd on my laptop, when I do
>>
>> ssh -lroot 192.168.2.101
>>
>> from my desktop, I get prompted for my ssh key's pass phrase, which I
>> enter. Thereafter, nothing happens, and it continues to happen for a
>> long, long time.
>
> Has your install gotten to the stage where you can chroot and emerge
> and unmerge. If so, I would suggest the following...
> 1) unmerge pam. *DO NOT LOGOUT OR REBOOT*
> 2) put the line
> sys-libs/pam
> in /etc/portage/package.mask Create the file if it doesn't exist.
> 3) emerge shadow *BEFORE YOU LOG OUT OR REBOOT*.
>
> Pam is an extra-high-security option that makes sense on a public
> server with lots of people being able to log in. On a personal laptop
> it is overkill. There was a comedy album once that was called...
> "Everything You Know Is Wrong". That describes Pam. The security
> settings for various services are in totally different files and
> locations than normal.
>
> Are you still booting from the install CD? The way you are running
> sshd is not how the install manual suggests to do it. The webpage...
> http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=1&chap=2
> shows that you can pass the kernel options...
>
> dosshd passwd=temppassword
>
> at bootup, where "temppassword" is a temporary password. This allows
> you to log in by typing the temporary password.
>
> --
> Walter Dnes <waltdnes@waltdnes.org>
None of which would affect (failing) pty allocation... while I share
the disdain for PAM, it doesn't likely do a whole lot to fix the
problem at hand.
--
Poison [BLX]
Joshua M. Murphy
next prev parent reply other threads:[~2009-12-06 21:32 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-06 14:48 [gentoo-user] Problems setting up sshd on an installation kernel Alan Mackenzie
2009-12-06 16:28 ` Mick
2009-12-06 20:23 ` Alan Mackenzie
2009-12-06 22:22 ` Mick
2009-12-06 16:59 ` Florian Philipp
2009-12-06 18:56 ` Joshua Murphy
2009-12-06 20:45 ` Alan Mackenzie
2009-12-09 15:24 ` Alan Mackenzie
2009-12-09 15:43 ` Alan McKinnon
2009-12-09 16:46 ` Alan Mackenzie
2009-12-09 19:42 ` Alan McKinnon
2009-12-09 21:57 ` Stroller
2009-12-09 22:20 ` Alan McKinnon
2009-12-10 10:36 ` Alan Mackenzie
2009-12-10 14:23 ` Neil Bothwick
2009-12-10 18:41 ` William Hubbs
2009-12-10 20:42 ` Mick
2009-12-10 15:27 ` Willie Wong
2009-12-10 16:52 ` Joshua Murphy
2009-12-09 22:35 ` Alan Mackenzie
2009-12-10 5:00 ` Stroller
2009-12-09 21:27 ` Stroller
2009-12-10 0:23 ` Dale
2009-12-06 20:17 ` Alan Mackenzie
2009-12-06 18:36 ` Walter Dnes
2009-12-06 21:31 ` Joshua Murphy [this message]
2009-12-06 21:49 ` Boy Hartsuiker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c30988c30912061331x3da6a455w843b72a93b11612c@mail.gmail.com \
--to=poisonbl@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox