Security Basics mailing list archives
Re: VNC Security
From: Andy Bruce - softwareAB <andy () softwareab net>
Date: Tue, 26 Apr 2005 15:35:36 -0400
---BEGIN CUT--- In all of these scenarios, you do the setup before hand. All of these scenarios are easily installed, and configured as a tech, and are as simple as 1-3 clicks for a user, no config, because everything (ssh keys, vpn preshared keys, etc) are all saved and stored in advance. A moment of setup in advance saves you hours of support later. ---END CUT--- I couldn't agree more. However, in my case I don't have access to these remote users PCs. They don't work for me or any particular company. In the usual case, they call in with a problem out of the blue. Sometimes I can help them without logging in. Sometimes I can't. For our internal boxes, I happen to use either the full Cygwin package or at least openssh for the users I work with. Then they just open port 22 (I normally don't want them to keep even that open) and I login and get work done. While I wouldn't call getting an SSH daemon setup on windows *correctly* a "moment" (google "sshd problems windows" for why...) it's well worth the effort. Public/private keys are even better. It's just that in many situations it's not possible to do the setup before hand. Regards, Andy
Current thread:
- RE: VNC Security, (continued)
- RE: VNC Security Steve Bostedor (Apr 20)
- RE: VNC Security Steve Bostedor (Apr 20)
- RE: VNC Security Joshua Berry (Apr 20)
- RE: VNC Security Steve Bostedor (Apr 20)
- RE: VNC Security Joshua Berry (Apr 21)
- RE: VNC Security Joshua Berry (Apr 21)
- Re: VNC Security Alexandre Zglav (Apr 21)
- RE: VNC Security Conlan Adams (Apr 26)
- Re: VNC Security Andy Bruce - softwareAB (Apr 26)
- RE: VNC Security Conlan Adams (Apr 26)
- Re: VNC Security Andy Bruce - softwareAB (Apr 26)
- RE: VNC Security Alexandre Zglav (Apr 27)