On 6/1/10 6:52 AM, Thomas Sondergaard wrote:
> Why does it have to be horribly ugly and inefficient? Do you also
> consider the port-forwarding mechanism in ssh to be a horrible ugly
> hack? Other than the large framebuffer update messages causing latency
> problems for other traffic, I don't se
Paul Donohue wrote:
> He's essentially looking for the ability to encapsulate packets from another
> network connection in an RFB message, which doesn't really have anything to
> do with encryption (I think the only reason ssh was mentioned is because ssh
> just happens to have the ability to en
I guess I still don't understand why. "Convenience" seems like actually
the wrong answer here. RFB is not exactly a secure protocol, and I
don't think many SysAdmins would appreciate us opening up a big security
hole to let anyone forward whatever they want by simply getting VNC
access into the m
He's essentially looking for the ability to encapsulate packets from another
network connection in an RFB message, which doesn't really have anything to do
with encryption (I think the only reason ssh was mentioned is because ssh just
happens to have the ability to encapsulate network packets in
On Fri, 28 May 2010, DRC wrote:
>
> Why aren't you? What functionality would creating our own SSh tunnel
> provide that embedded encryption of the RFB protocol wouldn't provide?
He said he wanted tcp port forwarding.
On 5/28/10 4:51 AM, Thomas Sondergaard wrote:
> DRC wrote:
>> Why reinvent the wheel? I don't see why it's our job to reproduce the
>> functionality of SSH. Just use SSH.
>
> Convenience is a good answer. Another answer is that VNC is used for
> many things, and not all users that are allowed t
DRC wrote:
> Why reinvent the wheel? I don't see why it's our job to reproduce the
> functionality of SSH. Just use SSH.
Convenience is a good answer. Another answer is that VNC is used for
many things, and not all users that are allowed to access a system with
VNC is allowed ssh access.
> N
Why reinvent the wheel? I don't see why it's our job to reproduce the
functionality of SSH. Just use SSH.
Now, if you instead mean internal encryption of the RFB protocol stream,
then didn't we get that as a result of the GNU TLS functionality that
Adam added?
On 5/25/10 4:19 AM, Thomas Sonderg
Hi,
I'm very interested in VNC implementations that implement an ssh-like
channel mechanism. What I'm looking for is ideally an open source VNC
implementation that supports ssh-style tcp port-forwarding over RFB. If
that doesn't exist, and I don't think it does, because I haven't been
able to
