From: Jesper Juhl <juhl-lkml@dif.dk>
To: Danny Brow <dan@fullmotions.com>
Cc: Kernel-List <linux-kernel@vger.kernel.org>
Subject: Re: SSH and 2.6.9
Date: Wed, 27 Oct 2004 22:54:48 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.61.0410272247460.3284@dragon.hygekrogen.localhost> (raw)
In-Reply-To: <1098906712.2972.7.camel@hanzo.fullmotions.com>
On Wed, 27 Oct 2004, Danny Brow wrote:
> I have this odd issue with the 2.6.9 & greater kernels, that I can't ssh
> or use scp any more, this is what happens when I try:
>
> SSH Error with-in X:
> ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory
> Host key verification failed.
>
> SCP Error with-in X:
> ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory
> Host key verification failed.
> lost connection
>
> I just get Host key verification failed in the terminal with either
> command.
>
> ssh-askpass does not exsisit but it never has & ssh/scp works fine with
> 2.6.8.1 and below. When upgrading to the new kernel I just copied my
> old .config and did a make oldconfig, make, etc.
>
> Any ideas?
>
As it happens, I had a chat with a few people on IRC a few days ago who
had very similar trouble and I had no such trouble. After talking about
our kernel configs a bit we came to the conclusion that the main
difference between our .config's (except for some hardware specific
drivers and a few other bits that seemed unrelated) was that they had
CONFIG_LEGACY_PTYS=y while I had it unset. One guy recompiled his kernel
on the spot and disabled CONFIG_LEGACY_PTYS and then reported that his
trouble went away. He may have made other changes as well, I don't know,
and it may have been some of the seemingly unrelated bits that did the
trick, again I don't know.
I have not attempted to verify this myself, but I'd say it's worth a try
for you to disable CONFIG_LEGACY_PTYS (if you have it enabled) and then
test that (and report your findings back).
--
Jesper Juhl
next prev parent reply other threads:[~2004-10-27 23:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-27 19:51 Danny Brow
2004-10-27 20:54 ` Jesper Juhl [this message]
2004-10-27 21:25 ` Danny Brow
2004-10-27 21:49 ` Danny Brow
2004-10-27 22:36 ` Jesper Juhl
2004-10-28 9:29 ` Andrew Morton
2004-10-29 10:36 ` Jesper Juhl
2004-10-29 10:52 ` Oliver Falk
2004-10-29 10:55 ` ismail dönmez
2004-10-29 12:45 ` Jesper Juhl
[not found] ` <m3u0sfs0fm.fsf@rajsekar.pc>
2004-10-28 17:44 ` Danny Brow
2004-10-29 12:03 ` Rajsekar
2004-10-27 22:27 ` Danny Brow
2004-10-27 19:59 Danny Brow
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=Pine.LNX.4.61.0410272247460.3284@dragon.hygekrogen.localhost \
--to=juhl-lkml@dif.dk \
--cc=dan@fullmotions.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®