From: Danny Brow <dan@fullmotions.com>
To: Rajsekar <raj--cutme--sekar@cse.iDELTHISitm.ernet.in>,
Kernel-List <linux-kernel@vger.kernel.org>
Subject: Re: SSH and 2.6.9
Date: Thu, 28 Oct 2004 13:44:14 -0400 [thread overview]
Message-ID: <1098985454.9722.9.camel@hanzo.fullmotions.com> (raw)
In-Reply-To: <m3u0sfs0fm.fsf@rajsekar.pc>
On Thu, 2004-10-28 at 14:07 +0530, Rajsekar wrote:
> No, that is not the actual problem (even though it seems to solve it).
> The thing is, /dev/tty should be rw for everyone.
> What happens is (it happened to me and CONFIG_LEGACY_PTYS is `n' in my
> case), that ssh tries to open /dev/tty and fails and ends up trying to use
> ssh-askpass (some other way to ask for password).
>
> But I am still not sure how CONFIG_LEGACY_PTYS=n solves it.
>
> Change the permissions of /dev/tty to something like 0666 or if you have
> udev, edit the permissions.d/* files
>
> Please give me your feedback.
>
I think when udev creates the ptys nodes dynamically it corrupts the
Legacy ones already create. With CONFIG_LEGACY_PTYS turned off there
never created and udev is free to do what it wants. It could be the
complete reverse though.
By the way th settings in permissions.d are 660 for most things
including ptys. I'm running slackware.
Dan.
next prev parent reply other threads:[~2004-10-28 17:43 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
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 [this message]
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=1098985454.9722.9.camel@hanzo.fullmotions.com \
--to=dan@fullmotions.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raj--cutme--sekar@cse.iDELTHISitm.ernet.in \
/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®