RE : VNC
From: Marty (marti@videotron.ca)
Date: 01/30/03
- Previous message: pasi.kivikangas@nokia.com: "RE: security scenario"
- In reply to: Jason Dixon: "Re: VNC"
- Next in thread: Clark, Steve: "RE: VNC"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Wed, 29 Jan 2003 20:29:35 -0500 From: Marty <marti@videotron.ca> To: 'Jason Dixon' <jasondixon@myrealbox.com>, security-basics@securityfocus.com
It was due mostly to flaws within the software.
Read more about it here : http://www.sans.org/rr/win/VNC2.php
--- Marty! ****************************************** -----Message d'origine----- De : Jason Dixon [mailto:jasondixon@myrealbox.com] Envoyé : 29 janvier, 2003 19:53 À : Marty Cc : security-basics@securityfocus.com Objet : Re: VNC On Wed, 2003-01-29 at 13:08, Marty wrote: > Hi, > > I remember inquiring last year about VNC as a network remote control > solution. Sincere thanks to all those that answered. We stopped the > VNC implementation after reading about all the risks related to the > product. > > > Our tech people are coming back and charging... again. > > My question is simple is the latest version of VNC better than the > previous ones and should we allow our tech group to use it to take > control of our machines (servers and workstations)... How is it a security risk when you tunnel it via SSH (pre-shared keys, of course)? -J.
- Next message: Tucker, Jason: "RE: Yet another syslog question"
- Previous message: pasi.kivikangas@nokia.com: "RE: security scenario"
- In reply to: Jason Dixon: "Re: VNC"
- Next in thread: Clark, Steve: "RE: VNC"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
Loading