gt; to specific clients - and that probably wouldn't work for your scenario.
SMB is being patched on a regular basis by MS to improve its security - the
recent global Wannacry attack being a case in point. I would think SMB is the
most attacked protocol on a daily basis and trying to configure a SM
you could offer access via OpenVPN and tunnel samba through that.
I haven't been able yet to figure out what implications creating a VPN
has. I understand it's supposed to connect networks through a secured
tunnel, but what kind of access to the LAN does someone get who connects
via VPN? Besides,
hus offers a big attack
>> surface for hackers and bots. I'm not sure you want to expose this to
>> the internet without some sort of firewall in place to restrict access
>> to specific clients - and that probably wouldn't work for your scenario.
> At least it's a possibi
ely complicated and
> difficult to set up. I consider it an awful nightmare.
You need to first understand how tunnel devices work. Then it becomes
very easy to set up. The access to the LAN can be restricted by
firewall rules. As long as you don't setup routes from the transfer
that is one of
> > > > the main reasons why I do not have a VPN connection but use ssh
> > > > instead. The only disadvantage is that I can't do RDP sessions
> > > > with that --- I probably could and just don't know how to ---
> > > > but thing
ection (if we could ever get that to work).
> > > I haven't been able to figure that out myself, and that is one of
> > > the main reasons why I do not have a VPN connection but use ssh
> > > instead. The only disadvantage is that I can't do RDP sessions
> > &g
Mail list logo