From: Greg Scott <GregScott@InfraSupportEtc.com>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Gre Tunneling Problem
Date: Wed, 09 Jan 2002 18:28:12 +0000 [thread overview]
Message-ID: <marc-lartc-101060016524190@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101039544916808@msgid-missing>
That paper (great work!) tells about the Microsoft PPTP problems.
But what about the Linux GRE tunnel documented in the HOWTO? Does
it have the same implementation problems?
- Greg
-----Original Message-----
From: Michael T. Babcock [mailto:mbabcock@fibrespeed.net]
Sent: Wednesday, January 09, 2002 11:58 AM
To: Greg Scott
Cc: LARTC List
Subject: Re: [LARTC] Gre Tunneling Problem
On Wed, Jan 09, 2002 at 12:01:09PM -0600, Greg Scott wrote:
> What I don't understand is, how does the security work? I think the
> two tunnel endpoints are supposed to authenticate eachother with the
> TCP port 1723 packets, but what do the Linux systems use for a shared
> secret? I would use this all over the place if I felt good about its
> security.
If you want the gory details on the (in)security of it, go to Google and
search for "pptp mudge counterpane". The first link you get should be
a security audit of PPtP at counterpane.com done by Mudge of L0pht.com
fame and Bruce Schneier, author of Applied Cryptography and Secrets and
Lies (as well as both having general Internet recognition in security).
The paper deals mostly with MS-CHAP2 which is the authentication protocol
Microsoft uses in its PPTP stuff. For those who don't like PDFs, the
HTML version can be seen (as rendered by Google) at (one line):
http://www.google.com/search?q che:fKZC3BSAczQC:www.counterpane.com/pptp.p
df+pptp+mudge+counterpane+pdf&hl=en
--
Michael T. Babcock
CTO, FibreSpeed Ltd. (Hosting, Security, Consultation, Database, etc)
http://www.fibrespeed.net/~mbabcock/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
next prev parent reply other threads:[~2002-01-09 18:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-06 9:39 [LARTC] Gre Tunneling Problem glynn
2002-01-07 0:58 ` glynn
2002-01-07 1:48 ` glynn
2002-01-07 4:04 ` glynn
2002-01-07 6:28 ` glynn
2002-01-07 6:35 ` glynn
2002-01-07 9:40 ` glynn
2002-01-07 10:21 ` glynn
2002-01-07 11:41 ` Christoph Simon
2002-01-08 0:56 ` Christoph Simon
2002-01-08 1:01 ` Joe Patterson
2002-01-08 1:07 ` glynn
2002-01-08 1:15 ` glynn
2002-01-08 1:18 ` Christoph Simon
2002-01-08 4:54 ` Greg Scott
2002-01-08 7:28 ` glynn
2002-01-08 9:14 ` Christoph Simon
2002-01-08 9:48 ` Christoph Simon
2002-01-08 12:40 ` Greg Scott
2002-01-09 2:44 ` Greg Scott
2002-01-09 3:02 ` glynn
2002-01-09 14:27 ` Michael T. Babcock
2002-01-09 17:49 ` Greg Scott
2002-01-09 17:58 ` Michael T. Babcock
2002-01-09 18:28 ` Greg Scott [this message]
2002-01-09 18:43 ` Michael T. Babcock
2002-01-09 19:40 ` Greg Scott
2002-01-11 14:21 ` Greg Scott
2002-01-11 15:20 ` Joe Patterson
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=marc-lartc-101060016524190@msgid-missing \
--to=gregscott@infrasupportetc.com \
--cc=lartc@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.