RE: [rfbhackers] Auditing Capabilities

[Andrew v. d. S. <aj...@gr...>]

Todd,

The protocol per se doesn't have any auditing features. The major thing
from my point of view is that it is easily verifiable, and nearly all
channels completely optional. If the client or server implementers wish
to include auditing features (and I think this is a good idea), then
they should do so based upon the grammar of the protocol.

Did anyone see the BEEP (block extensible exchange protocol) discussion
on Slashdot yesterday? Who thinks moving to Beep as the underlying
protocol? This would seriously cut down the time it takes to migrate to
RFB 4.x as you'd only need to map BEEP messages to RFB capabilities.  

Andrew

-----Original Message-----
From: sec...@li...
[mailto:sec...@li...] On Behalf Of
Smith, Todd
Sent: Wednesday, 17 July 2002 6:10 AM
To: 'sec...@li...'
Subject: [rfbhackers] Auditing Capabilities

I hope that this is on-topic but I don't see within the protocol specs
or
within any of the clients and servers the ability to audit connection
information from a VNC server.  Have I missed something?

Todd Smith <tod...@ca...>


-------------------------------------------------------
This sf.net email is sponsored by: Jabber - The world's fastest growing 
real-time communications platform! Don't just IM. Build it in! 
http://www.jabber.com/osdn/xim
_______________________________________________
Securevnc-rfbhackers mailing list
Sec...@li...
https://lists.sourceforge.net/lists/listinfo/securevnc-rfbhackers