[no subject]

> Yet another reason why DHCP is a badly designed protocol.  Who created it
> anyway?  The other reason is that it is UDP which is spoofable, rather than
> TCP which is not with a decent stack.  Microsoft?

Sun did, or at least bootp on which dhcp is based. IMHO, though, TCP vs UDP
doesn't really matter for bootp / dhcp because they're broadcast-based. Why
bother spoofing? It's easier just to set up a bogus DHCP server to answer
the client's DHCPDISCOVER....

later,
chris


</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="00133" href="msg00133.html">[ale] Comcast linux...</a></strong>
<ul><li><em>From:</em> jerry.yu at Voicecom.com (Yu, Jerry)</li></ul></li>
<li><strong><a name="00161" href="msg00161.html">[ale] Comcast linux...</a></strong>
<ul><li><em>From:</em> bob at verysecurelinux.com (Bob Toxen)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg00163.html">[ale] Comcast linux...</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg00165.html">[ale] Comcast linux...</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg00194.html">[ale] Comcast linux...</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg00088.html">[ale] router web interface and Mozilla</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#00164"><strong>Date</strong></a></li>
<li><a href="threads.html#00164"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>