X2Go Bug report logs - #737
X2GoClient should contain an option to add arbitary ssh port forwardings

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.x2go.org (full text, mbox, reply):

From: Stefan Baur <X2Go-ML-1@baur-itcs.de>

To: submit@bugs.x2go.org

Subject: X2GoClient should contain an option to add arbitary ssh port forwardings

Date: Sat, 10 Jan 2015 10:41:53 +0100

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

package: x2goclient
severity: wishlist

It would be cool to have an option inside X2GoClient that allows ssh
port forwardings, like PuTTY does.
For simplicity (so the session DB doesn't have to be changed), this
should be limited to portforwardings from the X2GoClient to the Server
- - in SSH-speak, "-L1234:foobar.example.com:1234", but not
"-R1234:foobar.example.com:1234".

- -Stefan

- -- 
BAUR-ITCS UG (haftungsbeschränkt)
Geschäftsführer: Stefan Baur
Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364
Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJUsPPgAAoJEG7d9BjNvlEZTm4IAK64UUW4tiR3vxJQHQxLKDPg
nEqbaonYSXysv+HR2p1o+z9XcJIENZc47haJBET7885x7dqI4uqGFVFzdKo30sM/
C5dMDSX9sx2bwAw1RjUDd+kiHTVoPaUkxenz9ep5GPjf4z7nRkTb++skCtC01Cy6
MVHkzimbe93LmHVCn/jH2YsDzV+ssArX7Gc6ZRO0IV6Bn9UUCKU2PNTJmHH7wo39
4gMYS2XZizHl2jXUc04UwFCv4uHD5hBOpzlfMQyqJZss7WmBdbnSfF1SI3kZhdhp
JorPuRj6srPWIq1efmxHVED6Xr5jmR6hMZ2R+2R3fhBmU59TeHsljnNplj7is6Y=
=upEX
-----END PGP SIGNATURE-----

Message #10 received at 737@bugs.x2go.org (full text, mbox, reply):

From: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

To: Stefan Baur <X2Go-ML-1@baur-itcs.de>, 737@bugs.x2go.org

Subject: Re: [X2Go-Dev] Bug#737: X2GoClient should contain an option to add arbitary ssh port forwardings

Date: Sat, 10 Jan 2015 11:04:06 +0000

[Message part 1 (text/plain, inline)]

On  Sa 10 Jan 2015 10:41:53 CET, Stefan Baur wrote:

> package: x2goclient
> severity: wishlist
>
> It would be cool to have an option inside X2GoClient that allows ssh
> port forwardings, like PuTTY does.
> For simplicity (so the session DB doesn't have to be changed), this
> should be limited to portforwardings from the X2GoClient to the Server
> - - in SSH-speak, "-L1234:foobar.example.com:1234", but not
> "-R1234:foobar.example.com:1234".
>
> - -Stefan

For you lpr/lpd printing feature you would need a -R (reverse) port  
forwarding tunnel which would in turn open a listening socket on the  
X2Go server which could be accessed by all users on that specific X2Go  
Server.

(Which actually is the case for all other port forwardings used in  
X2Go, with the difference that those port forwardings have some means  
of authentication mechanism implemented (pulse cookie, sshfs pub/priv  
key auth).

Mike

-- 

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb

[Message part 2 (application/pgp-signature, inline)]

Message #15 received at 737@bugs.x2go.org (full text, mbox, reply):

From: Stefan Baur <X2Go-ML-1@baur-itcs.de>

To: 737@bugs.x2go.org

Subject: Fwd: Re: [X2Go-Dev] Bug#737: X2GoClient should contain an option to add arbitary ssh port forwardings

Date: Sat, 10 Jan 2015 12:07:22 +0100

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1




- -------- Weitergeleitete Nachricht --------
Betreff: Re: [X2Go-Dev] Bug#737: X2GoClient should contain an option to
add arbitary ssh port forwardings
Datum: Sat, 10 Jan 2015 12:06:37 +0100
Von: Stefan Baur <X2Go-ML-1@baur-itcs.de>
An: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

Am 10.01.2015 um 12:04 schrieb Mike Gabriel:
> For you lpr/lpd printing feature you would need a -R (reverse)
> port forwarding tunnel which would in turn open a listening socket
> on the X2Go server which could be accessed by all users on that
> specific X2Go Server.

Which is exactly why *this* is a *separate* wishlist bug, as it has
*nothing* to do with printing.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJUsQfqAAoJEG7d9BjNvlEZpvcIAI8NwpZ3yQq7/TnzFCOMK2bC
RQv8MMxMclaHLMGsKAt3WgRAxD8nh4YsSGG2DvIKl3bojZ2O50apmkME5D3wUcnT
wQGrKJ/0PfQdGnSFXox/9tfu1NDmz1tF7Mf42ImpH38DkxMfkEz9lgp4upcAhPe7
CI37b+Ffk9lsVcr6xwW/hawEsoKHLCekTZCgLwtiFzOBVNjyzUaVqYBZ455Y4rmi
bPI5q69OCeqPK2+T4yZ1ZSV6IkOscHTABZrgw54o3lpPynWz+6Yg+qMsqix5uvCD
pNAes6YbJjMEbz4tVO86SECgRdPH8o6152sum5Zp9M8Jdyanz8AHZE7IcGqqZp8=
=8Us3
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.