Bug 691595

Summary: Incorrect port syntax on evolution sftp calendar publishing
Product: Red Hat Enterprise Linux 6 Reporter: Paul Moore <pmoore>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED WONTFIX QA Contact: Desktop QE <desktop-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.0CC: mcrha
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-12-05 13:03:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Paul Moore 2011-03-28 22:28:55 UTC
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 2 RHEL 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.

Comment 3 Milan Crha 2013-05-10 11:41:34 UTC
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.

Comment 4 Ondrej Holy 2015-10-06 09:58:30 UTC
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 6 Red 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.