From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tom Rymes To: development@lists.ipfire.org Subject: Re: [PATCH] pptp: Update to 1.10.0 Date: Fri, 05 Feb 2021 08:20:21 -0500 Message-ID: <9CF10841-E9D5-40A1-9641-27B481326CB5@rymes.net> In-Reply-To: <4E5D1289-36BE-4588-9749-B7A9E20187E4@ipfire.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============7718888483914547307==" List-Id: --===============7718888483914547307== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable > On Feb 5, 2021, at 6:15 AM, Michael Tremer wr= ote: >=20 > Hello, >=20 >> On 4 Feb 2021, at 22:58, Adolf Belka wrote: >>=20 >> Hi Tom, >>=20 >> On 04/02/2021 19:10, Tom Rymes wrote: >>> Isn=E2=80=99t PPTP heavily deprecated, or is that just when used with cer= tain encryption methods? >> It may be, I don't know for sure. However, while it is still in IPFire I t= hink it is better to have the latest version from 2018 rather than the one fr= om 2008. >=20 > Yes, in terms of bugs in the implementation it is. >=20 > PPTP is a universal tunnelling protocol (short for point-to-point tunneling= protocol) and it can be used for VPNs. However it is very old and the specif= ied cryptography is very outdated. In IPFire we only use it to connect to som= e DSL providers which use it on the Internet link. They do not use any encryp= tion and use weak authentication to identify the subscriber. >=20 > -Michael Thanks, Michael. I have used PPP for DSL links before, but didn=E2=80=99t rea= lize that some required PPTP. Tom --===============7718888483914547307==--