← Back to team overview

desktop-packages team mailing list archive

[Bug 375341] Re: ssh-add/ssh-askpass (gnome) not launching graphical prompt on connect

 

I can see a regression in Oneiric, but I don't know if this has to be added to this bug:
I have both Natty and Oneiric on the same laptop (both are fresh installs, no upgrades).
I share my .ssh between the two (symlinked from /media/Data)

When I start Natty, all keys under ~/.ssh are available and managed by ssh-askpass (in addition, ssh-add -l shows all of them)
When I start Oneiric, only ~/.ssh/id_[rsa|dsa] are available, and I have to manually launch ssh-add on the keys I want to add...

I have greped across all the config files I could suspect on Natty, and
did not found any explicit reference to these keys, so I assume they
were automatically discovered.

This does not seem to be the case in oneiric.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/375341

Title:
  ssh-add/ssh-askpass (gnome) not launching graphical prompt on connect

Status in “gnome-keyring” package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: gnome-keyring

  On previous release ubuntu 8.04/ubuntu 8.10 when using ssh to connect
  to remote hosts with ssh private keys from within the gnome
  environment, the ssh-askpass (gnome-ssh-askpass renamed) is launched
  to prompt for the pass phrase for the keys in
  $HOME/$USER/.ssh/{identity,id_dsa,id_rsa} once this pass phrase is
  input it is handled by gnome-keyring/ssh-agent for future connects so
  that no passphrase is required for any machine using that key.

  On a clean install of ubuntu 9.04 the behaviour is different. Upon
  connection to an ssh host, ssh-askpass is no longer launched and
  instead the ssh terminal application prompts you for the key.

  Without the setup of scripts/wrappers, this key must be entered every
  time a user wants to connect to a host using that private ssh key.

  There are many work arounds for this (using ssh agent, launching ssh-
  askpass as a session at login etc) but I believe this is either a bug,
  or an expected change in behavior in how gnome is intergrated with
  ssh.

  I have been unable to find any documentation to indicate a change in
  behavior in the gnome desktop environment.

  I am unsure if this bug request should sit with the gnome-desktop
  environment, gnome-keyring or the ssh team, I suspect this is a
  keyring intergration issue, but I have been unable to find any
  design/documentation on how keyring was working with 8.04/8.10 and
  ssh.

  
  this problem appears in both 32 and 64bit versions of the 9.04 OS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/375341/+subscriptions