Connection Notice.

Ben Maizels bmaizels "at" analystic.com
Fri, 25 Sep 1998 13:45:41 +0000


The only problem with this being that people are going to get fed up having
to check a box saying that they are present at the machine and want to be
asked permission for new vnc connections, and then unchecking it everytime
they leave the machine.  I suppose it is not too easy for an operating
system to automatically determine if a user is actually present at the
console (it could make an educated guess - for instance how long since a key
was last pressed or the mouse was last moved, but it is still making an
assumption).

I feel David's original idea of some form of notification (as opposed to
permission) would be acceptable, perhaps a brief pop-up dialogue which
vanishes after a couple of seconds and small icon on the taskbar (or some
similar indication in non-MS environments) to indicate that one or more VNC
sessions are connected to your terminal.  Ideally you should then be able to
double click on this icon and get a full list of all the connections and
their originating IPs.  Having never used any of the MS clients (only the
Unix ones which I know do not support such a thing) I have no idea how much,
if any, of this functionality is already present, so my apologies if I am
reinventing the wheel here.

Unfortunately those are just ideas, I am not in a position to actually code
such a thing, but maybe someone else can.

> -----Original Message-----
> From:	andy mcfarland [SMTP:andy.mcfarland "at" tjbrent.co.uk]
> Sent:	25 September 1998 12:48
> To:	vnc-list "at" orl.co.uk
> Subject:	RE: Connection Notice.
> 
> Had a similar idea to this but haven't got around to modifying the
> server code.
> 
> Without modifying the Protocol it would be possible to add this feature
> by changing the hand-shakeing procedure for the server.  After the
> Client/Server have decided on the protocol to be used the server has a
> chance to say "connection failed" and supply a piece of free format text
> to the client specifying the reason (section 5.1.2 of the RFB Protocol)
> 
> So change the procedure to check an option and if necessary pop-up a
> dialog along the lines of "<MachineName>/<IP Address> is requesting a
> VNC session to your desktop.  Is this OK?  [YES] [NO]".  If the answer
> is YES then go ahead and request authentication off the client, if NO
> then send a "connection failed" response with something sensible as the
> reason.
> 
> The only problem with this is the client might time-out waiting for an
> Authentication response.
> 
> Anyone?
> 
> 
> > ----------
> > From: 	David
> > Bussenschutt[SMTP:D.Bussenschutt "at" mailbox.gu.edu.au]
> > Sent: 	25 September 1998 06:29
> > 
> > Is there any way of throwing up a notice onto the screen of the
> > machine
> > running the server when someone connects to it?
> > 
> 
> ---------------------------------------------------------------------
> The VNC mailing list     -   see http://www.orl.co.uk/vnc/intouch.html
> ---------------------------------------------------------------------

---------------------------------------------------------------------
The VNC mailing list     -   see http://www.orl.co.uk/vnc/intouch.html
---------------------------------------------------------------------