Article View: comp.protocols.ppp
Article #319Re: James - any new thots on pppoE?
From: James Carlson
Date: Tue, 13 Feb 2001 13:58
Date: Tue, 13 Feb 2001 13:58
55 lines
3628 bytes
3628 bytes
John D Loop <loop@snt.bst.bls.com> writes: > Thanks for your comments, James. > You would probably get an argument about DHCP and bridging in a WAN > environment. I believe almost all the ADSL providers started off that way > (including BellSouth), but they got away from it as fast as they could. DHCP > works well, as long as you are in a trusted environment. Stolen IPs, > broadcast traffic, rogue DHCP servers, using MAC address as "authentication" > proved very troublesome. PPPoE has absolutely no security whatsoever. It's in worse shape than DHCP, since at least with DHCP, there's ongoing effort to add security. > The Redbacks (which BellSouth [and the rest of the > known universe] switched to) were added by the providers who would do almost > anything to go to a more familiar PPP implementation (!), where authentication > is via username/password, traffic isolated to the ppp connection, nobody can > steal IPs. In short, it "looks" like dialup. Looks can be deceiving. It's trivial to forge packets on PPPoE, and use these forged packets to highjack user sessions or snipe them out of existence as long as you have bridging at the Ethernet layer. Security through obscurity is no security at all. > They (Redback) had to invent a ppp-like implementation over ethernet to pull > this off for all the ethernet NICs and ethernet bridging modems out there. I strongly disagree. It wasn't necessary at all. Treat each ADSL link as a separate Ethernet segment, and you're in business. There's no reason on earth to be bridging among separate ADSL links I think you're confusing implementation with protocol design. > I understand your concerns about pppoE, especially that it is a proprietary > non standards track implementation, but I think the ADSL providers had little > choice [other than to go away]. The Telcos have always been big proponents of > standards [they want all this equipment to interoperate..], but market forces > forced their hand. > Also, I believe since the pppoE runs on a customer-specific PVC, the potential > for the abuse is less. If you can do that with PPPoE, you can do it with DHCP. > Still trying to learn ppp, and now l2tp. Grief. I thot I had it under control > when I learned IP! > ...I don't think I want to know about HURL and MOTM.... OK; I won't tell you. -- James Carlson, Internet Engineering <james.d.carlson@east.sun.com> SUN Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677 Second Edition now available - http://people.ne.mediaone.net/carlson/ppp
Technical Details
Message-ID:
<xoavpugmfzwz.fsf@sun.com>Path:
arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!supernews.com!isdnet!grolier!btnet-peer0!btnet-feed5!btnet!carbon.eu.sun.com!new-usenet.uk.sun.com!eastnews1.east.sun.com!not-for-mailReferences:
<3A87F5AB.7592D38E@snt.bst.bls.com> <xoav8znc3q4u.fsf@sun.com> <3A89379A.8B36DAED@snt.bst.bls.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1122a6,8bcec72c5c695208 X-Google-Attributes: gid1122a6,public X-Google-Thread: 103eaf,8bcec72c5c695208 X-Google-Attributes: gid103eaf,public X-Google-ArrivalTime: 2001-02-13 06:12:04 PST Path: arc1-ca.pugleaf.net!supernews.google.com!sn-xit-02!supernews.com!isdnet!grolier!btnet-peer0!btnet-feed5!btnet!carbon.eu.sun.com!new-usenet.uk.sun.com!eastnews1.east.sun.com!not-for-mail From: James Carlson <james.d.carlson@sun.com> Newsgroups: comp.protocols.ppp,bellsouth.net.support.adsl Subject: Re: James - any new thots on pppoE? Date: 13 Feb 2001 08:58:04 -0500 Organization: Sun Microsystems Inc. - BDC Lines: 55 Message-ID: <xoavpugmfzwz.fsf@sun.com> References: <3A87F5AB.7592D38E@snt.bst.bls.com> <xoav8znc3q4u.fsf@sun.com> <3A89379A.8B36DAED@snt.bst.bls.com> NNTP-Posting-Host: phorcys.east.sun.com X-Home-Page: http://people.ne.mediaone.net/carlson/ X-Newsreader: Gnus v5.7/Emacs 20.7