On 24/10/2011 13:57, Vassilis V. wrote:
Hello David!

You seem to be very over complicating things :) If I understand you
correctly, you want to have your users authenticate themselves in order
to have limited access to the work network and offer them certain
services there. You already mentioned your solution but dismissed it!
What you want to set up and would solve all your problems with high
security is a VPN.

Your workers connect to the VPN (There are clients for every OS), and
immediately they have access to "their" PC at work. No need to open
individual ports for VNC, SMB etc. If you want each user to only be able
to connect to his own PC, have every user get a fixed IP (described in
the book) and then set up rules in the OpenVPN tab so that each IP can
only access certain PC's. The added benefit of a VPN is that the traffic
is encrypted and each user must authenticate himself with certificates
(or/and username/password).

Hope it helps!

Vassilis

Using a VPN is certainly a possibility - our "road warriors" who use a laptop as a main computer use a VPN (OpenVPN), and I use a VPN from my home machine regularly to access everything in the network here. Where VPNs are the right solution, they are what we use.

But I see two disadvantages of VPNs. They give too much access. Obviously firewall rules can be added to limit access in some ways, but it is somewhere between difficult and impossible to get the right balance between security and functionality here. How do I set up firewalls that lets the user access company files on a server from their home machine without also opening these files to whatever malware they've installed? I can proscribe rules and regulations for computers on the company network, I can monitor them for suspicious behaviour, and do regular checks. But I can't do that for people's home computers. I can do so on a limited basis for a few users, especially for those with company laptops that they use from home or outside, but it is not scalable in general.

The other disadvantage of a VPN is that the we use a lot of specialised software - people can't easily install it on their home machines. They may also need different sorts of access to different machines - trying to get routine and firewalling rules that allow this over a VPN without being too permissive is hard.

With VNC, both these issues are solved, since they are effectively working on their company desktops.


Obviously running VNC over a VPN would improve the security, since everything is encrypted, and it would be possible to set that up. In particular, it would be easier to set OpenVPN rules to say only port 5900 is allowed, than to try to give all the required firewall rules to let users get local access from home machines to the company systems. But encrypting VNC over a VPN is not really necessary - it is probably easier to use UltraVNC (or any other VNC with encryption built-in). It is also not much of a security issue since most employees have the same ISP as the company - there is very little possibility of eavesdropping or other attacks.


David
_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list

Reply via email to