After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 574517 - SSHFS sync shouldn't force "-p 22" option on tomboy by default
SSHFS sync shouldn't force "-p 22" option on tomboy by default
Status: RESOLVED FIXED
Product: tomboy
Classification: Applications
Component: General
0.12.x
Other Linux
: Normal normal
: ---
Assigned To: Tomboy Maintainers
Tomboy Maintainers
Depends on:
Blocks:
 
 
Reported: 2009-03-08 01:01 UTC by jisakiel
Modified: 2009-10-04 00:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Don't force port 22...only use -p option if port specified (2.99 KB, patch)
2009-08-23 00:46 UTC, Sandy Armstrong
none Details | Review

Description jisakiel 2009-03-08 01:01:09 UTC
When a hostname is specified without port for ssh sync, tomboy tries the following: 

[DEBUG]: Mounting sync path with this command: /usr/bin/sshfs -p 22 USER@HOST:/PATH /home/USER/.tomboy/sync-sshfs

Which fails on my configuration. 

My hostname:port combination is defined in .ssh/config as: 

Host HOSTALIAS1 HOSTALIAS2 HOST
    Hostname real-hostname.example.com
    Port 2222

sshfs without a port parameter works perfectly, as it uses the ssh configuration to resolve that hostname. I ssh as well to the host without having to specify the port. 



Using the port number in the tomboy configuration is however ok, as if I enter HOST:2222 it works perfectly, so tomboy must be parsing that line searching for ":". 

[DEBUG]: Mounting sync path with this command: /usr/bin/sshfs -p 2222 USER@HOST:/PATH /home/USER/.tomboy/sync-sshfs


Desired outcome would simply be for tomboy to *not* specify the default port unless given a different one, and trust on the sshfs default. Simple enough ;).
Comment 1 Sandy Armstrong 2009-03-08 02:14:39 UTC
Excellent point, targetting for next cycle.
Comment 2 Armen Baghumian 2009-07-18 09:50:16 UTC
It does'nt force port 22, just add port number after server name (e.g. example.org:2222)
But yes it's better to add a options textbox there to specify any kind of options there, take a look at http://bugzilla.gnome.org/show_bug.cgi?id=587269
Comment 3 Sandy Armstrong 2009-07-19 15:57:29 UTC
Armen, Tomboy actually does specify port 22 if no port is specified, so the original report is correct.  But thank you for pointing out the work-around, I forgot to do that when I commented.  :-)
Comment 4 Sandy Armstrong 2009-08-23 00:46:54 UTC
Created attachment 141464 [details] [review]
Don't force port 22...only use -p option if port specified

If anyone wants to test this out, that would be nice.  :-)
Comment 5 Sandy Armstrong 2009-08-24 06:16:38 UTC
Works for me, pushed, closing this bug.