Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1157729

Summary: openssh-5.3p1-104.el6.i686 update breaks nautilus Connect to Server option
Product: Red Hat Enterprise Linux 6 Reporter: Keith <kcpvwill>
Component: opensshAssignee: Petr Lautrbach <plautrba>
Status: CLOSED CURRENTRELEASE QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.3CC: goetz.waschk, halocaridina, jziniel, nenad
Target Milestone: rc   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-11-18 08:58:50 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Error window none

Description Keith 2014-10-27 15:06:08 UTC
Created attachment 951027 [details]
Error window

Description of problem: After openssh is updated from version 5.3p1-94.el6 to 5.3p1-104.el6, the Gnome nautilus File > Connect to Server function using ssh protocol no longer works. Error window shown in attachment


Version-Release number of selected component (if applicable):5.3p1-104.el6.i686


How reproducible:100%


Steps to Reproduce:
1.Update openssh, opensssh-askpass, openssh-clients & openssh-server from 5.3p1-94.el6.i686 to 5.3p1-104.el6.1686
2.Run Gnome nautilus file browser
3.Select menu option File > Connect to Server
4.Select Service type SSH and enter IP address

Actual results:Error box shown in attached file appears


Expected results:ssh connection to specified IP address is made and login credentials requested


Additional info: The IP address 127.0.0.0 shown in the attachment is not the real address used - several real address were tested which have worked in the past and which still work if the openssh packages are downgraded to the previous version

Comment 2 Nenad Opsenica 2014-11-13 08:21:22 UTC
Same thing with x86_64. There is a discussion on Scientific Linux forum - http://scientificlinux.b1.jcink.com/index.php?showtopic=2962
Same thing happened while ago with Archlinux and it turned out to be gvfs problem.

Comment 3 Halocaridina 2014-11-17 13:30:41 UTC
This was a problem with the SL6.5 release. However, upgrading a virtual machine and laptop this past weekend from SL 6.5->SL6.6 (i386 for the former, x86_64 for the latter) and can establish SFTP connections via Nautilus again.

So upgrading to the latest point release solved this regression (at least for me).

Comment 4 Petr Lautrbach 2014-11-18 08:58:50 UTC
This bug has been fixed by gvfs update https://rhn.redhat.com/errata/RHBA-2014-1499.html