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.
Description of problem: A non-default port entered into evolution sftp calendar publishing does not take effect.
Version-Release number of selected component (if applicable): 2.28.3-10 (But I have seen this on many versions of evolution.)
How reproducible: Always reproduceable.
Steps to Reproduce:
1. Specify a non-default port in Evolution Calendar Publishing via SFTP. ((Evolution Preferences -> Calendar and Tasks -> Calendar Publishing -> Add/Edit -> Service Type: Secure FTP (SSH), Enter a Server and Path. Optional Information Port: 12345, Username: fred, Password: secret))
2. Publish the Calendar (Calendars Component, Actions -> Publish Calendar Information)
3. Error: Connection Closed (Because it tried to contact the server on port 22 when it should have used port 12345)
Actual results: Dialogue Box Stating:
There was an error while publishing to sftp://fred.com:12345/home/fred/freebusy.icalendar: Authentication Required
On the command line the results were:
sftp fred.com:12345/home/user/freebusy.icalendar
Connecting to myserver.mydomain.com...
ssh: connect to host myserver.mydomain.com port 22: Connection refused
Couldn't read packet: Connection reset by peer
Expected results:
No dialogue box with the freebusy.icalendar file copied to the remote location.
This would be the equivalent of:
sftp -oPort=12345 fred.com:/home/fred/freebusy.icalendar
Connecting to myserver.mydomain.com...
Fetching /home/fred/freebusy.icalendar to freebusy.icalendar
Additional info:
The sftp package used for this test was openssh-clients-5.3p1-20.el6_0.3.i686.
Comment 2RHEL Program Management
2011-04-04 02:09:26 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Thanks for a bug report. I checked the code and it uses g_file_mount_enclosing_volume() on a GFile which has set the port too (or at least the URI which is used for this), thus I'm moving this to gvfs, because it's out of evolution hands how the library connects to the server.
I've tried to mount using gvfs-mount (gvfs-1.4.3-22.el6.i686) to sftp with a custom port and it works correctly. gvfs-mount uses also g_file_mount_enclosing_volume, so it should work correctly in evolution then...
$ gvfs-mount sftp://localhost/
Error mounting location: Connection refused by server
$ gvfs-mount sftp://localhost:12345/
Enter password
User:
I didn't test evolution and I didn't see its codes, but I am not sure it is using gio, because the reporter wrote something about sftp command. Sftp backend doesn't use sftp command, it uses ssh command instead...
$ ps ax | grep ssh
/usr/bin/ssh -oForwardX11 no -oForwardAgent no -oClearAllForwardings yes -oProtocol 2 -oNoHostAuthenticationForLocalhost yes -p 12345 -s localhost sftp
Comment 6Red Hat Bugzilla Rules Engine
2017-12-05 13:03:24 UTC
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.