On Wed, 24 Jan 2001, Some Guy wrote:
> Making encryption easy violates the clique.
That's a rather narrow viewpoint. There are always trade-offs involved in
selecting features:
1. Code-bloat is a bane. Have you ever used all the features of
MS Office? No? Well, you still have megs of space wasted by all
those features you never use.
2. Choice. If you build a feature in, it makes it harder to use
other methods, especially if you make it a default. If, say, PPTP
becomes the transport, how will that impact usage over ssh?
Personally, I use ssh on both my Windows and Linux clients to tunnel my
VNC traffic. With ssh1, I can set the level of zlib compression, feel
confident in the encryption (since it's an established, open protocol),
and generally get the job done smoothly.
As a major bonus, I don't have redundant code floating around (e.g.
additional ssh code bundled into VNC when it's already on my hard drive
as a seperate application) since it's expected that if I want
encryption, I will have already set it up.
Now, I *will* say that there are some features in VNC extensions that I'd
like to see rolled into the main distribution (i.e. tight or grayscale
encodings), but one of my main reasons for recommending the "real" VNC to
other people is the minimal download size of the package.
TridiaVNC is about 9 MB...it takes FOREVER to download at 28.8k. If I need
access to a remote client's system in a hurry, I want them to have the
smallest possible download, so I'm all in favor of leaving larger and more
complex features as patches, plug-ins, or whatever.
--
Todd A. Jacobs
Senior Network Consultant
---------------------------------------------------------------------
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
---------------------------------------------------------------------
