VNC Password project/suggestion

Tue, 23 Nov 1999 21:01:27 +0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01BF35F5.A99D7DD6
Content-Type: text/plain;
	charset="iso-8859-1"

Note: This userid is from our local public folder and is not affiliated with
VNC.

After bouncing this around our local administrators, here's the idea.

We have 40+ NT servers that are centrally located, running VNC as a service.
The various servers are "owned" by the various project
analyst/administrators. Some of these analyst/administrators have support
licenses with software providers/vars/etc.

The technical group (the group that I work for) has the overall
responsibility of keeping the hardware and OS running. So, every server
(which are all behind our firewall) has the same VNC password because
maintaining lists of passwords would be horrendous.

It would be great to be able to give the analyst/administrators the ability
to remotely connect to the server/servers that they (think they ;-) ) own
without giving them the master password.

It would further be a great convenience for the analyst/administrators to be
able to give out passwords to various VARS (who already use pcANYWHERE or
RemotelyAnywhere) without compromising either their password or the system
master password (mine :-| ).

Lastly, it would be helpful to be able to set a forced "view only" password
to allow our helpdesk people to view without risking unauthorized (ANY)
changes.

In summary... Instead of one password, I'd like to see up to four
configurable passwords.
0. Help Desk  (view-only... default)
1. VAR
2. Analyst
3. Master

The configuration would allow #3 to change any password, #2 could change #2
and #1, #1 and #0 cannot change passwords.

The calling sequence would be something like...  IPaddress:0:0 (where the
0's are the default and can be left out) therefore, to log on as Master,
you'd could enter... IPaddress::3 

Kick it around in the list for a while. Let's see what develops.

Matt 

Matt.Klett "at" kohlerco.com

------_=_NextPart_001_01BF35F5.A99D7DD6
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2448.0">
<TITLE>VNC Password project/suggestion</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Note: This userid is from our local public folder and =
is not affiliated with VNC.</FONT>
</P>

<P><FONT SIZE=3D2>After bouncing this around our local administrators, =
here's the idea.</FONT>
</P>

We have 40+ NT servers that are centrally located, =
running VNC as a service. The various servers are &quot;owned&quot; by =
the various project analyst/administrators. Some of these =
analyst/administrators have support licenses with software =
providers/vars/etc.

The technical group (the group that I work for) has =
the overall responsibility of keeping the hardware and OS running. So, =
every server (which are all behind our firewall) has the same VNC =
password because maintaining lists of passwords would be =
horrendous.

<P><FONT SIZE=3D2>It would be great to be able to give the =
analyst/administrators the ability to remotely connect to the =
server/servers that they (think they ;-) ) own without giving them the =
master password.</FONT></P>

<P><FONT SIZE=3D2>It would further be a great convenience for the =
analyst/administrators to be able to give out passwords to various VARS =
(who already use pcANYWHERE or RemotelyAnywhere) without compromising =
either their password or the system master password (mine :-| =
).</FONT></P>

<P><FONT SIZE=3D2>Lastly, it would be helpful to be able to set a =
forced &quot;view only&quot; password to allow our helpdesk people to =
view without risking unauthorized (ANY) changes.</FONT></P>

In summary... Instead of one password, I'd like to =
see up to four configurable passwords.
 0. Help Desk&nbsp; (view-only... default)
 1. VAR
 2. Analyst
 3. Master

<P><FONT SIZE=3D2>The configuration would allow #3 to change any =
password, #2 could change #2 and #1, #1 and #0 cannot change =
passwords.</FONT>
</P>

The calling sequence would be something like...&nbsp; =
IPaddress:0:0 (where the 0's are the default and can be left out) =
therefore, to log on as Master, you'd could enter... IPaddress::3 =

Kick it around in the list for a while. Let's see =
what develops.

<P><FONT SIZE=3D2>Matt </FONT>
</P>

<P><FONT SIZE=3D2>Matt.Klett "at" kohlerco.com</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01BF35F5.A99D7DD6--

---------------------------------------------------------------------
The VNC mailing list - see http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------