From: R0b0t1 <r030t1@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] [OT] What is the best open-source VPN server for Linux?
Date: Fri, 6 Apr 2018 20:44:01 -0500 [thread overview]
Message-ID: <CAAD4mYiEzzr3Cf-NKr-_KjvEaj+DoxnQ=1FjatPutBVw2q0XSQ@mail.gmail.com> (raw)
In-Reply-To: <1992980.6RBP82CMcb@dell_xps>
On Fri, Apr 6, 2018 at 12:58 PM, Mick <michaelkintzios@gmail.com> wrote:
> On Friday, 6 April 2018 00:10:00 BST Grant Taylor wrote:
>> On 04/05/2018 03:51 AM, gevisz wrote:
>> > Yes, the Host is running Windows.
>>
>> Seeing as how both the ""Host and the ""Client are running Windows, I
>> would think seriously about trying to leverage Windows' built in VPN
>> capabilities.
>>
>> The following things come to mind:
>>
>> - (raw) IPSec - this might be somewhat challenging b/c reasons
>
> I think you mean IKEv2 + IPSec?
>
> IKEv2 is used to exchange keys and IPSec is used to set up and encrypt the
> tunnel itself. The tunnel is operating at layer 2, so TCP/UDP/ICMP will all
> be encrypted when sent through through the IPSec encrypted tunnel.
>
>
>> - L2TP+IPSec - probably less challenging b/c of wizards
>
> This is using L2TP for encapsulating the frames + IKEv1 for secure key
> exchange + IPsec for encryption of the L2TP tunnel.
>
>
>> - PPTP - just don't unless you haveto
>
> Well said:
>
> https://en.wikipedia.org/wiki/Point-to-Point_Tunneling_Protocol#Security
>
> It is an obsolete method with poor security. I would not use it under any
> circumstances, unless security is of no importance.
>
>
>> I'd encourage your friend to check out the VPN capabilities built into
>> Windows. He may need to install / configure (R)RAS to enable the features.
>
> As I mentioned before, there is also IKEv2+IPSec, which allows the client to
> roam between networks without dropping the connection.
>
> Finally, there is SSTP encrypting PPP frames within TLS. I don't know why one
> would use this instead of OpenVPN, except that it comes as part of the
> MSWindows package, while OpenVPN has to be installed separately.
>
>
>> In my experience, using native features that come from the software
>> vendor is often simpler to maintain long term.
>
> +1
>
> They are also easier to set up initially, because both MSWindows peers will
> use the same combo of encryption suites, ciphers, etc.
You mean the same horribly insecure ciphers? The built in options are
so weak that I am not aware of anyone seriously using them; most
setups tunnel Windows technologies like RDP (which may sometimes
insist on being set up with encryption) over Linux based technologies.
next prev parent reply other threads:[~2018-04-07 1:44 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 20:18 [gentoo-user] [OT] What is the best open-source VPN server for Linux? gevisz
2018-04-04 22:02 ` Grant Taylor
2018-04-04 23:03 ` Mick
2018-04-05 9:57 ` gevisz
2018-04-05 9:51 ` gevisz
2018-04-05 10:28 ` gevisz
2018-04-05 11:51 ` Mick
2018-04-05 14:42 ` gevisz
2018-04-05 13:14 ` Bill Kenworthy
2018-04-05 14:51 ` gevisz
2018-04-05 22:45 ` Bill Kenworthy
2018-04-06 18:13 ` gevisz
2018-04-05 22:53 ` Grant Taylor
2018-04-05 16:29 ` Grant Taylor
2018-04-05 21:04 ` gevisz
2018-04-05 23:10 ` Grant Taylor
2018-04-06 17:55 ` gevisz
2018-04-07 12:19 ` Mick
2018-04-07 13:33 ` R0b0t1
2018-04-06 17:58 ` Mick
2018-04-06 18:20 ` Grant Taylor
2018-04-06 22:51 ` Mick
2018-04-06 23:21 ` Grant Taylor
2018-04-07 1:44 ` R0b0t1 [this message]
2018-04-04 23:55 ` R0b0t1
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAAD4mYiEzzr3Cf-NKr-_KjvEaj+DoxnQ=1FjatPutBVw2q0XSQ@mail.gmail.com' \
--to=r030t1@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox