Public bug reported:

Binary package hint: seahorse

Seahorse has a very useful feature to automatically copy your public ssh-key to 
a remote machine so you can login using that key later on.
There is one assumption seahorse makes that is not always true though: when 
ssh'ing to the remote machine to place the public key there, it assumes the 
current directory is your home directory, and tries to do stuff with 
.ssh/authorized_keys there.

On one of the machines I frequently use, I'm not in my homedir after
ssh'ing there. Seahorse tries to access .ssh/authorized_keys and fails,
because the current directory is /data. I think Seahorse should not rely
on the current directory being $HOME, but explicitely make it so as the
first command to be run remotely.

I have attached a screenshot of the errormessage I received.

** Affects: seahorse (Ubuntu)
     Importance: Undecided
         Status: New

-- 
Seahorse assumes current dir is $HOME when setting up ssh
https://bugs.launchpad.net/bugs/230222
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to