| Summary: | krdc should support tunneling through SSH like xvncviewer | ||
|---|---|---|---|
| Product: | [Applications] krdc | Reporter: | Mickael Marchand <marchand> |
| Component: | general | Assignee: | Urs Wolfer <uwolfer> |
| Status: | CONFIRMED --- | ||
| Severity: | wishlist | CC: | jrubcop, justin.zobel, mschoell, nate, petr, river, rjrich, suson, toma |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Mickael Marchand
2004-06-12 22:51:13 UTC
I agree that there is a huge need for security here, but, well, I am not convinced, just as one individual out here in the wilderness, that this is the responsiblity of krdc to provide. There are tons of packages out there that do this, including the SSH wrapper tool in KDE, which works great for setting-up SSH tunnel before firing this guy up pointed at "localhost:44444" or whatever you choose. There is also NoMachine, which is great, does this out of the box. "rdesktop" has encrytpion in it for Windohs boxes. VNC does not have encyrption, as you know, in the protocol, and it doe snot seem in our ability, nor our preview, to deal with that, since there are so many tried-n-true work-arounds and alternatives. I dont know if you have seen how long the buglist is for KDE, but one might argue that we ought not distract the dev's from the other important items. Just this guy's $0.02. Peace. Love. Linux. Jason *** Bug 105635 has been marked as a duplicate of this bug. *** *** Bug 144972 has been marked as a duplicate of this bug. *** vote++ I have here an openvpn-tunnel (so security is not an argument) where I am using vnc across. While one of the vncservers on the other side is reachable just fine, the other has to be bridged via the central server. Works just fine with "vncviewer -via bla blub". Would be fine if that also worked in krdc. For example with urls like sshhost:vncserver:screen... Otherwise krdc from kde4 is just great. Altough not as good with low bandwidths as tightvnc... *** Bug 295137 has been marked as a duplicate of this bug. *** *** Bug 256819 has been marked as a duplicate of this bug. *** I've been using remmina for quite a while and I liked the built-in ssh tunnelling feature. However remmina is plagued by many annoying bugs so I would like to move to krdc which seems to be much more stable. It's easy to say there are other tools for tunnelling (which is true) but then the connection is not one-click. It's necessary to open the tunnel first, use a static tunneling port and then connect to the server. Built-in tunnelling feature would make krdc much more powerful. Or at least give us option to run a background program before connecting - that would allow us to run ssh and open the tunnel automatically upon connecting to the server. Anyone interested in working on this? Poor bug hasn't had any love for a while. Resetting to default assignee (approved by Nate Graham) as no action on this bug for many years. Wasn't this resolved here? https://phabricator.kde.org/D13659 (In reply to Jonathan Rubenstein from comment #10) > Wasn't this resolved here? > https://phabricator.kde.org/D13659 It appears to be but I just tried to use it and it fails. I added in the ssh tunnel settings but it just errors saying it can't find the target hostname (it doesn't appear it's even trying the ssh tunnel as it is an instantaneous error). (In reply to Petr Sedlacek from comment #7) > I've been using remmina for quite a while and I liked the built-in ssh > tunnelling feature. However remmina is plagued by many annoying bugs so I > would like to move to krdc which seems to be much more stable. > > It's easy to say there are other tools for tunnelling (which is true) but > then the connection is not one-click. It's necessary to open the tunnel > first, use a static tunneling port and then connect to the server. Built-in > tunnelling feature would make krdc much more powerful. > > Or at least give us option to run a background program before connecting - > that would allow us to run ssh and open the tunnel automatically upon > connecting to the server. I actually worked around it by using a bash script to create the tunnel and launch krdc to connect to the locally mapped port. It's ugly but it works for me. |