From: "Yaakov (Cygwin/X)" <yselkowitz@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: gnome-keyring bug in snapshots
Date: Wed, 30 Nov 2011 04:14:00 -0000 [thread overview]
Message-ID: <CAGvSfew2TFPGwp=Kq_bkJ0891+vJiAueAd1H+K_SHNimMw0y1Q@mail.gmail.com> (raw)
For some time now, snapshots have displayed a bug wrt gnome-keyring,
namely that passwords don't "register" when entered. This wreaks
havoc on the GNOME desktop where so many programs rely on
gnome-keyring.
This is easy to reproduce, but requires xorg-server, dbus,
gnome-keyring, and openssh. At a new terminal:
$ XWin -multiwindow &>/dev/null &
$ export DISPLAY=:0
$ eval `dbus-launch --sh-syntax`
$ export `gnome-keyring-daemon --start --components=ssh`
$ ssh USER@HOSTNAME
(Enter password for ssh key in GUI prompt)
What should happen (and does with 1.7.9) is a successful login. WIth
the 20111129 snapshot, the following message is displayed on the
terminal:
Agent admitted failure to sign using the key.
(which AFAIK comes from ssh) and the gnome-keyring prompt asks for the
password to the next private key listed in ~/.ssh/config (even if its
the wrong key for HOSTNAME). Subsequent logins do succeed, however.
This does not occur with ssh-agent(1).
Frankly, I'm a little baffled by this one, but a non-working GNOME
desktop is really keeping me from testing the snapshots for any length
of time.
Yaakov
Cygwin/X
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2011-11-30 3:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-30 4:14 Yaakov (Cygwin/X) [this message]
2011-12-03 18:45 ` Christopher Faylor
2011-12-03 21:31 ` Christopher Faylor
2011-12-03 23:04 ` Corinna Vinschen
2011-12-04 19:27 ` Christopher Faylor
2011-12-05 2:03 ` Yaakov (Cygwin/X)
2011-12-05 5:02 ` Christopher Faylor
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='CAGvSfew2TFPGwp=Kq_bkJ0891+vJiAueAd1H+K_SHNimMw0y1Q@mail.gmail.com' \
--to=yselkowitz@users.sourceforge.net \
--cc=cygwin@cygwin.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 read-only IMAP folder(s) and NNTP newsgroup(s).