David:
Heya. In general, duplicating *well implemented* encryption is pointless. If your encryption is ROT13, doing it again with triple-DES is clearly advantageous. :) But if you're dynamically generating session keys (eg, Diffie-Hellman), using a good key-size (eg, 128-bits) and using a strong algorithm (eg, RC4, AES), then the computational requiements to "break" the encryption have already been elevated to rarified states. The incremental protection you'd be getting is, at that point, not worth the added latency.
Also, most encryption engines are just encryption, not encryption
plus compression. But for VNC traffic , the data is already, in some sense, "compressed", as per the bandwidth-optimizing algorithms that
are part VNC's RFB protocol.
Hope that helps!
-Scott
On Thu, 21 Apr 2005, David Schlesinger wrote:
Hey Scott and Group:
I am using ultravnc with echovnc. ultravnc has an 'rc4' dsm (data stream modification) plugin. Now they are working on an 'aes' plugin. I've been meaning to implement the rc4. Now they are working on aes. I'd like to make sure that at least one of these is installed to all of my users in case they use ultravnc on their own, outside of echovnc.
Question: is it overkill to have the encryption in place twice - i.e. to use your aes and theirs. Will it slow down the connection? Or, maybe it will speed it up? Is it encryption and compression or just encryption?
Also, I assume it will work.. haven't tried it yet though.
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Echovnc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/echovnc-users
