Issuing call setenv("DISPLAY", ":0", 1) via gdb seems to result in a
dialog popping up, as desired.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1812247
Title:
My suspicion is that we never get as far as askpass – gnome-keyring-
daemon spawns a ssh-agent to pass requests on to (in my case, that's
easy to spot because I use PKCS#11 tokens and that's the one spawning
ssh-pkcs11-helpers), and that one doesn't have DISPLAY in its
environment, so it won't
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-keyring (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
** Tags removed: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1812247
Title:
ssh-askpass(-gnome) fails for ssh-add -c: agent refused operation
We checked what actually is the backend that the "ssh-add -c" is trying to
reach.
First we thought that should be the ssh-agent spawned for gnome-keyring-daemon
[1]
In PS that is visible as:
1 1000 4029 1 20 0 656132 15860 - SLl ? 0:24
/usr/bin/gnome-keyring-daemon
** Also affects: gnome-keyring (Ubuntu)
Importance: Undecided
Status: New
** Changed in: openssh (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
schamane, thanks for reporting back your success. I've seen this
question asked a dozen times and never seen an answer documented.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
Steps for a workaround by disabling gnome-keyring's SSH agent component,
tested in Ubuntu 18.04.1:
# disable GNOME Keyring's SSH Agent, cf.
# https://askubuntu.com/a/585212/43108 + https://askubuntu.com/a/607563/43108
mkdir ~/.config/autostart
cp /etc/xdg/autostart/gnome-keyring-ssh.desktop
I originally reported this against gnome-session. @vanvugt changed it to
openssh. I think it should be changed to gnome-keyring. I didn't see it
at first but now it's clear that it is actually gnome-keyring that
interferes: `SSH_AUTH_SOCK=/run/user/1000/keyring/ssh`
--
You received this bug
The bug has been reproduced with the system's own ssh-keygen and the
command `ssh-keygen -N $passphrase -f ~/.ssh/id_rsa`. Also,
https://unix.stackexchange.com/a/351742 is about keys that didn't work
at all. The problem here is that confirmation fails, everything seems to
be working.
--
You
Could this answer be related?
https://unix.stackexchange.com/a/351742/254144
Are your ssh keys of the new format, having been generated with the -o
option of ssh-keygen?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
** Tags added: server-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1812247
Title:
ssh-askpass(-gnome) fails for ssh-add -c: agent refused operation
Gosh, I was mistaken in #7. As in my initial report: ssh-askpass is
working, it is only failing for ssh-add -c:
tux@vbu1804:~$ ssh-add -D
All identities removed.
tux@vbu1804:~$ ssh-add -l
2048 SHA256:vHjyOAyTnsn92i47AQ8qu/oL2Y3blesvs09wUoYpDDY tux@vbu1804 (RSA)
tux@vbu1804:~$ ssh-add
13 matches
Mail list logo
