> >>> I'm trying to implement VNC on a few MacOS 8.5 computers I
>have, but don't
>>>> want there to be any "evidence" per se of VNC's presence. I'd like to use
>>>> the computers without VNC having to be in the list of running applications
>>>> and no UI whatsoever.
>>>>
>>>> Any ideas?
Ah, as someone else mentioned, we have another Peeping Tom. There
are remarkably few legitimate uses for such a modification.
> >> Yeah. Put it in the startup items invisible. There should be no
>>> evidence, and it should run. However, this is off the top of my
> >> head, and I am not sure.
Nope, that won't work. At best, you could use an AppleScript to load
and then hide ChromiVNC, but it'd still be in the Applecation menu.
> > The old, 1.0, version was a extension rather than a application.
The ORL/AT&T versions were, but they still put stuff in the menubar
and loaded "background apps" which many tools (OtherMenu is a good
start) can display. Oh, and they were/are hideously unstable - don't
expect to go un-noticed with them.
>There's an extension backend, but you still have to run the VNC Server
>application frontend don't you?
With ChromiVNC that is true.
Bear in mind that I will not support my software being used as
spyware, so I want confirmation of what you really want to do with it
before I even think about helping you "hide" VNC on Macs. There's
nothing stopping you from taking my software and modifying it, as
long as you adhere to the GPL, but you get zero support for such
spyware from me.
Here's some stock "uses" and acceptable alternatives:
- Employee monitoring:
You are not allowed to spy on employees' computers, just like
tapping the telephone system is illegal. You may introduce a
security policy - which employees must read and agree to before
implementation - which explicitly states that monitoring software may
be used, at which point there is no longer any need to hide VNC.
ChromiVNC provides a very discreet indication of connections
(a count in one of the windows) which most users will not notice but
which I currently feel is acceptable. Your policy, should you
require it, may include mandatory running of VNC at all times.
- Student monitoring:
See above. Students are naturally inquisitive and will
quickly find ways to shut down VNC however well it is hidden or
protected, thus making such hiding or protection irrelevant. The
remedy is appropriate sanctions (including withdrawal of computer-use
privileges) against miscreants.
- Tech support:
VNC doesn't need to be running all the time, although it can
be. Simply direct users to launch VNC when requesting support, and
keep a standard password which is available to tech support
personnel. An "attach new client" option is a possibility, and may
be implemented if requested.
- FBI/CIA/MI5/etc surveillance:
You aren't going to get any support for *that* from me.
I hope this makes my position clear.
--
--------------------------------------------------------------
from: Jonathan "Chromatix" Morton
mail: [EMAIL PROTECTED] (not for attachments)
website: http://www.chromatix.uklinux.net/vnc/
geekcode: GCS$/E dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$
V? PS PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)
tagline: The key to knowledge is not to rely on people to teach you it.
---------------------------------------------------------------------
To unsubscribe, mail [EMAIL PROTECTED] with the line:
'unsubscribe vnc-list' in the message BODY
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
