On 16/02/11 04:11, Martin Koegler wrote:
> On Tue, Feb 15, 2011 at 08:22:15AM -0700, Mike Fisk wrote:
>> 1. Complete session management functionality including flexible
>> authentication, strong encryption, spawning new sessions, reconnecting
>> to existing sessions, etc. I lump a lot of things
On 15/02/11 05:33, DRC wrote:
> On 2/14/11 4:02 PM, Eric Stadtherr wrote:
>> Do you know of a way to check for the successful bind? One of the
>> behaviors that drove me down the libssh path was that /usr/bin/ssh
>> happily continues running despite failing to bind to the local port.
>> Therefore t
On 2/15/11 3:11 PM, Martin Koegler wrote:
> Making the vncviewer ssh into the server as the user, detecting all
> running VNC servers of the user and finally let the user select to
> connect to one instance or start a new session: I'm really missing
> such a feature [I had done such experiments too
On Tue, Feb 15, 2011 at 08:22:15AM -0700, Mike Fisk wrote:
> 1. Complete session management functionality including flexible
> authentication, strong encryption, spawning new sessions, reconnecting
> to existing sessions, etc. I lump a lot of things together that do
> not have to be part of the
On 2/15/11 9:22 AM, Mike Fisk wrote:
> 1. Complete session management functionality including flexible
> authentication, strong encryption, spawning new sessions, reconnecting
> to existing sessions, etc. I lump a lot of things together that do
> not have to be part of the RFB protocol and X ser
As a lurking user who hasn't (yet) contributed any code to this
project, I'll risk jumping into this discussion. We use VNC for thin
client and remote access terminal services. In that context, what VNC
really needs is to be competitive with RDP, Citrix, PCoverIP, SunRay,
etc. (none of which are
