From: Alberto Manuel Brandao Simoes <albie@alfarrabio.di.uminho.pt>
To: Andrew Morton <akpm@osdl.org>
Cc: netdev@oss.sgi.com
Subject: Re: Fw: [Bugme-new] [Bug 3527] New: ssh does not work with 2.6.9rc3
Date: Fri, 08 Oct 2004 20:41:49 +0100 [thread overview]
Message-ID: <4166ED7D.5040704@alfarrabio.di.uminho.pt> (raw)
In-Reply-To: <20041008104801.0dd96536.akpm@osdl.org>
Andrew Morton wrote:
> hrm. Could you check to see if it starts working OK after the machine has been
> up for more than five minutes?
3 hours up, still same problem
kind regards,
Alberto
>
> Begin forwarded message:
>
> Date: Fri, 8 Oct 2004 09:26:51 -0700
> From: bugme-daemon@osdl.org
> To: bugme-new@lists.osdl.org
> Subject: [Bugme-new] [Bug 3527] New: ssh does not work with 2.6.9rc3
>
>
> http://bugme.osdl.org/show_bug.cgi?id=3527
>
> Summary: ssh does not work with 2.6.9rc3
> Kernel Version: 2.6.9 RC 3
> Status: NEW
> Severity: normal
> Owner: other_other@kernel-bugs.osdl.org
> Submitter: albie@alfarrabio.di.uminho.pt
>
>
> Distribution: Slackware 10
>
> Problem Description:
> Had kernel 2.6.7 working correctly. It had a bug with my sis ethernet card.
> Upgraded to 2.6.8.1, and had problems with sata (bug #3521). So, tried the 2.6.9
> RC 3.
>
> With this kernel, the sis ethernet bug is fixed (well, at least I can do a ping
> -f without losing packets), SATA works but... wonder... ssh doesn't.
>
> If I have a public key on other machine without passphrase, it works.
> If not....
>
> ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory
> Permission denied, please try again.
> ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory
> Permission denied, please try again.
> ssh_askpass: exec(/usr/libexec/ssh-askpass): No such file or directory
> Permission denied (publickey,password,keyboard-interactive).
>
> Now, that file really doesn't exist. But it isn't needed with the old kernel.
> So, what 2.6.9 rc 3 has that 2.6.7 don't?
>
> Thanks,
> Alberto
>
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug, or are watching someone who is.
--
Alberto Simões
Much as I hate to say it, the Computer Science view of language design
has gotten too inbred in recent years. The Computer Scientists should
pay more attention to the Linguists, who have a much better handle on
how people prefer to communicate.
--Larry Wall
prev parent reply other threads:[~2004-10-08 19:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 17:48 Fw: [Bugme-new] [Bug 3527] New: ssh does not work with 2.6.9rc3 Andrew Morton
2004-10-08 18:10 ` Thomas Graf
2004-10-08 19:49 ` Alberto Manuel Brandao Simoes
2004-10-08 20:01 ` Alberto Manuel Brandao Simoes
2004-10-08 20:21 ` Andrew Morton
2004-10-08 20:19 ` Alberto Manuel Brandao Simoes
2004-10-08 20:31 ` Thomas Graf
2004-10-08 20:33 ` Alberto Manuel Brandao Simoes
2004-10-08 19:41 ` Alberto Manuel Brandao Simoes [this message]
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=4166ED7D.5040704@alfarrabio.di.uminho.pt \
--to=albie@alfarrabio.di.uminho.pt \
--cc=akpm@osdl.org \
--cc=netdev@oss.sgi.com \
/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;
as well as URLs for NNTP newsgroup(s).