Ubuntu
virt-manager package

SSH dialog for first remote connection to unknown server should not be a password field

Bug #220825 reported by Fabián Rodríguez on 2008-04-22

Affects		Status	Importance	Assigned to	Milestone
	virt-manager (Fedora)	Won't Fix	Medium	redhat-bugs #461945
	virt-manager (Ubuntu)	Won't Fix	Wishlist	Unassigned

Bug Description

Binary package hint: virt-manager

When a host KVM is running and openssh server is running, try to access it from another machine:
1) Launch virt-manager on "Client" machine
2) choose File > Open Connection... > Connection: Remote Tunnel over SSH
Enter your credentials as user@IPaddress or <email address hidden>

The attached dialog is shown asking if one wants to trust the unknown RSA fingerprint, the answer can be typed in a password field. It should be a radio button for Yes or No.

Revision history for this message

Fabián Rodríguez (magicfab) wrote on 2008-04-22:

Screenshot-OpenSSH.png Edit (17.7 KiB, image/png)

Revision history for this message

In Red Hat Bugzilla #461945, James (james-redhat-bugs) wrote on 2008-09-11:

Created attachment 316451
Screenshot

Description of problem:

The dialog that appears requesting confirmation to connect to the system uses the passphrase entry dialog, instead of a 'yes/no' dialog.

Version-Release number of selected component (if applicable):

libvirt-0.4.5-2.fc10.i386
virt-manager-0.6.0-1.fc10.i386
qemu-0.9.1-10.fc10.i386

How reproducible:
100%

Steps to Reproduce:
1. Left-click on gnome-applet-vm
2. Select connections
3. Select Add
4. Select Driver=QEMU/KVM, check remote connection, enter remote hostname details, username=root, transport=SSH
5. Click submit
6. In connections window, select [X] to enable the new connection.

Actual results:
See screenshot

Expected results:

Additional info:

Revision history for this message

In Red Hat Bugzilla #461945, James (james-redhat-bugs) wrote on 2008-09-11:

Created attachment 316452
virt-manager.log

Dustin Kirkland  (kirkland) on 2008-10-01

Changed in virt-manager:
importance:	Undecided → Wishlist
status:	New → Confirmed

Bug Watch Updater (bug-watch-updater) on 2008-10-01

Changed in virt-manager:
status:	Unknown → Confirmed

Bug Watch Updater (bug-watch-updater) on 2008-10-23

Changed in virt-manager:
status:	Confirmed → In Progress

Revision history for this message

In Red Hat Bugzilla #461945, Bug (bug-redhat-bugs) wrote on 2008-11-26:

This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Revision history for this message

In Red Hat Bugzilla #461945, Cole (cole-redhat-bugs) wrote on 2008-12-01:

We don't control this dialog, it actually comes from ssh. Changing component to OpenSSH.

Revision history for this message

In Red Hat Bugzilla #461945, Tomas (tomas-redhat-bugs) wrote on 2008-12-02:

If you write yes as a passphrase I suppose it will work, wouldn't it? The problem with the askpass dialog is that the ssh client does not give any information to the askpass application whether it is a regular passphrase question or any other question which can be echoed. I am afraid that this will have to be solved upstream first. I'll report it to the upstream bugzilla.

Revision history for this message

In Red Hat Bugzilla #461945, Fedora (fedora-redhat-bugs) wrote on 2009-03-10:

This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.

Revision history for this message

In Red Hat Bugzilla #461945, Jan (jan-redhat-bugs) wrote on 2009-04-28:

We believe that it is more appropriate for this issue to be resolved upstream.
Red Hat will continue to track the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates.
Thank you for the bug report.

Bug Watch Updater (bug-watch-updater) on 2009-04-28

Changed in virt-manager (Fedora):
status:	In Progress → Fix Released

Revision history for this message

Marc Deslauriers (mdeslaur) wrote on 2010-03-24:

Thanks for reporting this issue.

This dialog is actually from openssh, and requiring the user to type "yes" or "no" in the window is deliberate in order to make the user read what he's agreeing to.

If you don't agree with openssh's dialog box, please file a new bug against the openssh package.