public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH] pptp: Update to 1.10.0
Date: Fri, 05 Feb 2021 16:07:55 +0000	[thread overview]
Message-ID: <256F3807-BDD6-4A5E-9D0A-8B02D2DE79F6@ipfire.org> (raw)
In-Reply-To: <9CF10841-E9D5-40A1-9641-27B481326CB5@rymes.net>

[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]

Hi,

> On 5 Feb 2021, at 13:20, Tom Rymes <tom(a)rymes.net> wrote:
> 
>> 
>> On Feb 5, 2021, at 6:15 AM, Michael Tremer <michael.tremer(a)ipfire.org> wrote:
>> 
>> Hello,
>> 
>>> On 4 Feb 2021, at 22:58, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>> 
>>> Hi Tom,
>>> 
>>> On 04/02/2021 19:10, Tom Rymes wrote:
>>>> Isn’t PPTP heavily deprecated, or is that just when used with certain encryption methods?
>>> It may be, I don't know for sure. However, while it is still in IPFire I think it is better to have the latest version from 2018 rather than the one from 2008.
>> 
>> Yes, in terms of bugs in the implementation it is.
>> 
>> 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 specified cryptography is very outdated. In IPFire we only use it to connect to some DSL providers which use it on the Internet link. They do not use any encryption and use weak authentication to identify the subscriber.
>> 
>> -Michael
> 
> Thanks, Michael. I have used PPP for DSL links before, but didn’t realize that some required PPTP.

It is very rare these days. Which brings me to the question: Can anyone actually test this any more?

-Michael

> 
> Tom


  reply	other threads:[~2021-02-05 16:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-04 12:56 Adolf Belka
2021-02-04 17:15 ` Peter Müller
2021-02-04 18:10   ` Tom Rymes
2021-02-04 22:58     ` Adolf Belka
2021-02-05 11:15       ` Michael Tremer
2021-02-05 13:20         ` Tom Rymes
2021-02-05 16:07           ` Michael Tremer [this message]
2021-02-05 17:36             ` Adolf Belka

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=256F3807-BDD6-4A5E-9D0A-8B02D2DE79F6@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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