<html><head>
<link media="all" type="text/css" href="/webmail/static/deg/css/wysiwyg-3933289048.css" rel="stylesheet">
</head><body>
/usr/bin/x2gomountdirs: $port=@dl[1]<br><br>looks like there may be a means to do this already.<br><br>-Gerry<br><br><br><br>Jun 25, 2010 04:11:45 PM, x2go-dev@lists.berlios.de wrote:<br><blockquote style="border-left: 3px solid rgb(102, 153, 204);">Hi there,<br><br>in the current x2goclient package (3.01-5, Debian, Qt version) there <br>is need for an option to configure the reverse SSH port number (i.e. <br>the SSH daemon's port on the client side). This option should be a <br>client wide config option (not a per-session option).<br><br>Printing and file sharing (sshfs/fuse) build up a reverse port <br>forwarding tunnel from the x2goserver back to the client. This feature <br>is used for x2goprint and x2gomountdirs (if I understand the perl code <br>correctly) and could also be used for any other feature that could be <br>evoked by a reverse SSH connection...<br><br>The linux x2goclient, however, pre-requisites a running ssh daemon on <br>the client system. Its standard port is 22. The x2goclient will only <br>work if the client's SSH daemon runs on the default port 22. It will <br>fail if the port has been set to a custom (high) port.<br><br>Consider a client, whose system administrator has set the SSH port to <br>a high --- to potential intruders unknown --- port number (e.g. <br>20222). With such an SSH setup, sshfs/fuse will fail...<br><br>Reproduce:<br><br> o modify /etc/ssh/sshd_config<br> o set ,,Port 20222'' (or something else)<br> o /etc/init.d/ssh restart<br> o start x2goclient as some user and login to a remote x2goserver<br> o start a shell within the x2go session on the server<br> o type ,,mount | grep sshfs''<br><br>Suggestions:<br><br>(a)<br>add a global SSH port number option to the x2goclient (linux-only).<br><br>(b)<br>Another way for the x2goclient could be some autodetect code:<br>lsof -ni | egrep "^sshd.*root.*IPv4" | awk '{ print $8 }'<br><br>(c)<br>Another way, similar to the windows client, could be to run a separate <br>ssh instance that binds to a random port on the localhost lo-device <br>only. That's where the reverse SSH tunnel (server -> client) has its <br>endpoint.<br><br>sshd -o ListenAddress 127.0.0.1:<someport> -o <someotheroption><br><br><br>Hope to be of help,<br>Mike<br><br>-- <br><br>DAS-NETZWERKTEAM<br>mike gabriel, dorfstr. 27, 24245 barmissen<br>fon: +49 (4302) 281418, fax: +49 (4302) 281419<br><br>eMail-LeseSchreibStunde: wochentags 8h-10h<br>mail: m.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de<br><br>freeBusy:<br>https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb<br><br>_______________________________________________<br>X2go-dev mailing list<br>X2go-dev@lists.berlios.de<br>https://lists.berlios.de/mailman/listinfo/x2go-dev<br></someotheroption></someport></blockquote></body></html>