seahorse gets confused when the host key of the other machine can't be verified
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| seahorse |
Expired
|
Medium
|
|||
| seahorse (Ubuntu) |
Triaged
|
Low
|
Ubuntu Desktop Bugs | ||
Bug Description
Binary package hint: seahorse
Hi,
I'm running gutsy. I just installed seahorse, created an ssh key, and set up
another machine to recognise it using the wizard that is part of the key
creation wizard. I had already connected to the other machine using
ssh password authentication.
I then wanted to set up another machine that I hadn't previously accessed.
I selected the "Set up computer for Secure Shell" option and filled in
the hostname. I was then given a password prompt as before, but the
message was different, instead of "<username> password for <hostname>
(<ip address>)" I had "Authenticity of the host key for <hostname> (<ip address>)
cannot be established".
Entering my password in to that dialog gave an error dialog with the same message
and the wizard quit.
I think there are two problems here, firstly that the password prompt was offered
with that error message. Secondly that there is no way to confirm the authenticity
of the host key.
Thanks,
James
| Andreas Moog (ampelbein) wrote | #1 |
| Changed in seahorse: | |
| assignee: | nobody → andreas-moog |
| importance: | Undecided → Low |
| status: | New → Incomplete |
| Andreas Moog (ampelbein) wrote | #2 |
| Changed in seahorse: | |
| assignee: | andreas-moog → desktop-bugs |
| status: | Incomplete → Triaged |
| Changed in seahorse: | |
| status: | Unknown → New |
| Changed in seahorse: | |
| status: | New → Confirmed |
| Jens Askengren (jens-askengren) wrote | #3 |
| Changed in seahorse: | |
| importance: | Unknown → Medium |
| Changed in seahorse: | |
| status: | Confirmed → Expired |
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.