Re: Wish : chat between client and server
Wed Feb 19 10:55:01 2003
Wednesday, February 19, 2003, 10:30:24, Teng-Fong wrote:
STF> First, don't forget that VNC is multi-platform. Second, in case you
STF> don't know technologies, let me explain a bit to you. Instant messenger
STF> requires first a server to logon while VNC is point to point. If you say
STF> it's possible to install an instant messenger server, the answer is "it's a
STF> waste of time and ressource".
Maybe you don't know enough point to point chat applications (as I
said there are hundreds, maybe thousands applications which do not
require a server).
Netmeeting _is_ point to point. And multiplatform (I mean, there are
*nix clients). So is talk (and yes, there are quite a few talk clients
for windows). And many, many, many other applications.
STF> As to company policy, if you understand why there're companies
STF> allowing PCAnywhere but forbidding Internet surfing or instant messenger,
STF> you could also understand why they would forbid netmeeting but allows vnc.
So let me get this straight: company policy forbids program X (ytalk for
example, or any other simple chat program), but if you include the same
code into VNC the same company policy will allow it, because it's
called VNC. Pretty shallow company policy.
STF> OTOH, it is not unusual that company computers are behind
STF> firewall(s) which blocks both incoming and outcoming traffics except a few
STF> ports, usually 80. So, in some case, if 80 is the only port, either you let
STF> VNC work for tele-maintainance or workers brwoser the web. I think the
STF> choice is clear.
I assume the "clear" choice for you is to use port 80 for VNC, isn't
it ? Even if the company policy is "NO VNC". If it were "only
VNC" they would open other ports, not port 80, isn't it ?
STF> Moreover, it's well known that ICQ has a lot of security flaws :
STF> hackers can execute (or make a user execute) worms or other dirty stuffs.
STF> For netmeeting, it's not sure it's 100% sure. But for VNC, everything must
STF> to be done _on_the_screen_. If a hacker wants to run a virus, he has to run
STF> it in a Dos window or double click. If there's a user before the server
STF> screen (which is almost always the case), he could know what he's doing.
I fail to see the logic. You say that if you have a VNC (or VNC + chat) with a
security flaw then if the flaw is exploited you could see this on the
screen. Why is that ?
STF> There're more reasons than I can easily imagine, but I think these
STF> are enough for now.
I see none. Maybe you should care to support your affirmations, or to
find other reasons.
STF> As to bloat, I don't think a chat client could be a bloat. First,
STF> it just needs two panels, one keyboard input stream listener, one network
STF> input stream listener and some codes to display characters. It couldn't be
STF> bigger than notepad. (FYI, WinVNC is about 330 kB. Notepad is about 50KB).
STF> Second, it can be a separate programme (executable), sort of plugin.
Remember, VNC is free. You cannot have the whole list of features
because you don't pay anybody to do it. Remember, the wish list is
huge:chat, encryption, file transfer, remote registry
edit, other windows related stuff (start/stop services, etc), remote
shell, streaming the audio, etc. But all of these are not real
problems; you can get around (sometimes in more than one way). I have
no idea where are "the vnc people" going, but I assume the focus is on
problems like "vnc crashes with windows X service pack Y", or "vnc is
too slow even with a lot of bandwidth", because we cannot really solve
this problems using a chat client, or ssh, or ftp server, or whatever
other tool freely available.
>> -----Message d'origine-----
>> De : email@example.com [mailto:firstname.lastname@example.org]
>> EnvoyC) : mardi 18 fC)vrier 2003 20:22
>> C : 'email@example.com'
>> Objet : Re: Wish : chat between client and server
>> There are thousands ways to chat between 2 computers. Even windows has
>> the standard netmeeting. There are many web sites where you can chat
>> from the browser (fancy java or plain html).
>> By the way what company policy forbids netmeeting but allows vnc ?!
>> P.S. About bloat: there is a need for a chat client in vnc, I wonder
>> what's next, encryption ? :-))
>> Tuesday, February 18, 2003, 18:31:22, Teng-Fong wrote:
>> STF> I've looked through the FAQ and last few months
>> of mailing-list
>> STF> archive, but I can't see this wish (if I miss it, excuse-me).
>> STF> What I would like is the possibility of chatting
>> between client and
>> STF> server. Now right, when I need to "talk" to the person
>> sitting before the
>> STF> computer running VNC server, there're only two choice :
>> STF> 1) use instant messenger like ICQ. But this application
>> isn't always
>> STF> present, nor is it always allowed to be installed (eg
>> company policy)
>> STF> 2) use Notepad. I type one line, he types one lines, etc. Very
>> STF> inconvenient when we both are typing at the same time :-)
>> STF> The chat window doesn't need to be very fancy.
>> No need to be able
>> STF> to choose font or color, no need to have image. But I
>> would like it to be
>> STF> Unicode compliant so that non Latin characters can be
>> displayed correctly.
>> VNC-List mailing list
STF> VNC-List mailing list