>I'd like to see all the other encodings documented, including
>the Tridia ones.
Already searched (only for fun) and not found without looking
into the code.
>* Two new RFB authentication mechanisms
>- an uprated version of the current #2 mechanism that doesn't involve
>reversible passwords at either end
Yes, this second one may be good.
But why modify the first ? What about leaving it as it is and just
develop the other ?
>* New login interchange that reduces the information available to
>unauthenticated users as well as reducing the inbound load on servers until
>after the server has authenticated the client
Yes. A simple challenge/response mecanism.
The password, server side, must be "digested", thus un-reversible.
Client sends a "are you here" request.
Server answer "yes" (or server answer nothing :-) with a random
data packet to be coded with password mecanism.
Client then send password (in fact, the random packet modified with
password mecanism).
... and after that, every thing is usual.
The server has only to store the already modified random packet
will waiting for client response. After one minute or so, forget
the packet.
Re-reading that, I'm not sure this will be clearly explained :-)
>* optional Lightweight stream encryption support (blowfish, aes, etc)
Yes, good.
How about using only one or, maybe, two encryption mecanism ?
One which is fast, one which is very robust. I'm not an expert in
encryption.
>* Ability for clients and servers to tell each other about their
>capabilities
This is now absolutely necessary.
>* Add a sound channel to the protocol
:-)
Why not.
... but what about a file transfert mode ?
Well, I use VNC every days.
I have a problem with C++ as I don't understand anything with
this obscure language. C is very ok but C++, erk, I can't do
anything with this.
This is the only reason why I did not already added file
transfert protocol for myself.
___________________________
David TAILLANDIER
[EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
