1 |
lee <lee@××××××××.de> wrote: |
2 |
|
3 |
> <wabenbau@×××××.com> writes: |
4 |
> |
5 |
> > lee <lee@××××××××.de> wrote: |
6 |
> > |
7 |
> >> Rich Freeman <rich0@g.o> writes: |
8 |
> >> |
9 |
> >> > On Sun, Jan 17, 2016 at 6:38 AM, lee <lee@××××××××.de> wrote: |
10 |
> >> >> Suppose you use a VPN connection. How do does the client |
11 |
> >> >> (employee) secure their own network and the machine they're |
12 |
> >> >> using to work remotely then? |
13 |
> >> > |
14 |
> >> > Poorly, most likely. Your data is probably not nearly as |
15 |
> >> > important to them as their data is, and most people don't take |
16 |
> >> > great care of their own data. |
17 |
> >> |
18 |
> >> That's not what I meant to ask. Assume you are an employee |
19 |
> >> supposed to work from home through a VPN connection: How do you |
20 |
> >> protect your LAN? |
21 |
> > |
22 |
> > Depends on the VPN connection. If you use an OpenVPN client on your |
23 |
> > PC then it is sufficient to use a well configured firewall (ufw, |
24 |
> > iptables or whatever) on this PC. |
25 |
> |
26 |
> The PC would be connected to the LAN, even if only to have an internet |
27 |
> connection for the VPN. I can only guess: Wouldn't that require to |
28 |
> put this PC behind a firewall that separates it from the LAN to |
29 |
> protect the LAN? |
30 |
|
31 |
Of course a separate firewall is better than a firewall on the PC, |
32 |
because it may protect the LAN even when the PC is compromised. But |
33 |
if the PC is compromised and has access to the LAN through the |
34 |
separate firewall (what is mostly the case) then the protection is |
35 |
more ore less porous (depending on the firewall rules). |
36 |
|
37 |
If you don't have a separate firewall but only a firewall on the (not |
38 |
compromised) PC, then the LAN should be safe as long as you don't |
39 |
have enabled IP forwarding on the PC and as long as the VPN is |
40 |
configured in a way that there is only a route to your PC and not |
41 |
to the rest of your LAN. |
42 |
|
43 |
Even if you have enabled IP forwarding on the PC and even if the VPN |
44 |
has a route to the whole LAN, the LAN should nevertheless be safe |
45 |
when the firewall on the PC is configured to block all incoming |
46 |
connections. |
47 |
|
48 |
Of course the blocking of all incoming connections implies, that the |
49 |
PC is acting as a client only. |
50 |
|
51 |
> > If you use a VPN gateway then you could |
52 |
> > configure this gateway (or a firewall behind) in a way that it |
53 |
> > blocks incoming connections from the VPN tunnel. |
54 |
> |
55 |
> Hm. I'd prefer to avoid having to run another machine as such a |
56 |
> firewall because electricity is way too expensive here. And I don't |
57 |
> know if the gateway could be configure in such a way. |
58 |
|
59 |
All VPN gateways that I know have also a build in firewall. If your |
60 |
gateway hasn't, then you should ask yourself, what is more expensive - |
61 |
a separate firewall or a hacked LAN? |
62 |
But in this case I would prefer to use the PC as OpenVPN client. |
63 |
|
64 |
> > IMHO there is no more risk to use a VPN connection than with any |
65 |
> > other Internet connection. |
66 |
> |
67 |
> But it's a double connection, one to the internet, and another one to |
68 |
> another network, so you'd have to somehow manage to set up some sort |
69 |
> of double protection. |
70 |
|
71 |
See above. |
72 |
|
73 |
> Setting up a VPN alone is more than difficult enough already. |
74 |
|
75 |
This depends on the VPN that you (have to) use. If you set up the VPN |
76 |
on both sides then you probably can choose what kind of VPN you wanna |
77 |
use. |
78 |
|
79 |
OpenVPN isn't really difficult to set up. If you don't wanna use PSK |
80 |
but X509 authorization, then the most complicated thing is the creation |
81 |
of the certs. But with the help of Google (or DuckDuckGo), this is |
82 |
quick done. There are lots of information about setting up an OpenVPN |
83 |
connection. |
84 |
|
85 |
-- |
86 |
Regards |
87 |
wabe |