25.02.2013 Views

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Data<br />

L2<br />

Net<br />

L2TP<br />

Code<br />

Figure 22-55 L2TP packet flow through any <strong>IP</strong> cloud<br />

22.14.3 L2TP security issues<br />

<strong>IP</strong> UDP L2TP PPP Data<br />

<strong>IP</strong><br />

Code<br />

<strong>IP</strong> Cloud<br />

<strong>IP</strong><br />

Code<br />

L2TP<br />

Code<br />

Although L2TP provides cost-effective access, multiprotocol transport, <strong>and</strong><br />

remote LAN access, it does not provide cryptographically robust security<br />

features. For example:<br />

► Authentication is provided only for the identity of tunnel endpoints, but not for<br />

each individual packet that flows inside the tunnel. This can expose the tunnel<br />

to man-in-the-middle <strong>and</strong> spoofing attacks.<br />

► Without per-packet integrity, it is possible to mount denial-of-service attacks<br />

by generating bogus control messages that can terminate either the L2TP<br />

tunnel or the underlying PPP connection.<br />

► L2TP itself provides no facility to encrypt user data traffic. This can lead to<br />

embarrassing exposures when data confidentiality is an issue.<br />

► While the payload of the PPP packets can be encrypted, the PPP protocol<br />

suite does not provide mechanisms for automatic key generation or for<br />

automatic key refresh. This can lead to someone listening in on the wire to<br />

finally break that key <strong>and</strong> gain access to the data being transmitted.<br />

Realizing these shortcomings, the PPP Extensions Working Group of the IETF<br />

considered how to remedy these shortfalls. Rather than duplicate work done<br />

elsewhere, it was decided to recommend using <strong>IP</strong>Sec within L2TP. This is<br />

described in RFC 2888.<br />

In summary, Layer 2 Tunnel Protocols are an excellent way of providing<br />

cost-effective remote access. And when used in conjunction with <strong>IP</strong>Sec, they are<br />

an excellent technique for providing secure remote access. However, without<br />

L2<br />

Net<br />

Data<br />

Chapter 22. <strong>TCP</strong>/<strong>IP</strong> security 879

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!