don't set -p / "-o port" explicitly when syncing with sshfs
Bug #328253 reported by
kij
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| tomboy |
Unknown
|
Wishlist
|
|||
| tomboy (Ubuntu) |
Triaged
|
Low
|
Ubuntu Desktop Bugs | ||
Bug Description
Binary package hint: tomboy
servers are in .ssh/config, sshfs reads it, yet the port options are overruling it.
maybe connected to:
https:/
http://
but they do seem a bit old.
--from tomboy.log:
02/11/2009 21:44:09 [DEBUG]: Mounting sync path with this command: /usr/bin/sshfs -p 22 kij@XXXXXX: /home/kij/
02/11/2009 21:44:09 [DEBUG]: Error calling /usr/bin/sshfs
from shell its:
/usr/bin/sshfs -p 22 kij@XXXXXX: /home/kij/
read: Connection reset by peer
(port closed)
/usr/bin/sshfs kij@XXXXXX: /home/kij/
(works)
with XXXXXX defined in .ssh/config as:
Host XXXXXX
Hostname XXXXXX.domain.
Port 34991
User kij
Revision history for this message
| Derrick Hudson (dman) wrote | #1 |
Revision history for this message
| Pedro Villavicencio (pedro) wrote | #2 |
| Changed in tomboy (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| assignee: | nobody → Ubuntu Desktop Bugs (desktop-bugs) |
| Changed in tomboy: | |
| importance: | Unknown → Medium |
| status: | Unknown → New |
| Changed in tomboy: | |
| importance: | Medium → Wishlist |
| status: | New → Confirmed |
| Changed in tomboy: | |
| status: | Confirmed → Unknown |
To post a comment you must log in.
This is particularly braindead behavior:
* ssh automatically defaults to port 22, no need to specify it
* tomboy does not provide a means to specify what port to specify to sshfs
* tomboy does not provide any error information when the connection fails
* my ssh server does not listen on port 22 due to too many dictionary attacks
* my ~/.ssh/config explicitly gives the correct port to use
Please fix this!