![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
X-Original-To: cryptography@metzdowd.com From: Jerry Leichter <leichter@lrw.com> In-Reply-To: <52738ACD.6030502@gmail.com> Date: Fri, 1 Nov 2013 10:21:14 -0400 To: Yaron Sheffer <yaronf.ietf@gmail.com> Cc: "cryptography@metzdowd.com List" <cryptography@metzdowd.com>, John Gilmore <gnu@toad.com>, David Mercer <radix42@gmail.com> Errors-To: cryptography-bounces+crypto.discuss=bloom-picayune.mit.edu@metzdowd.com On Nov 1, 2013, at 7:04 AM, Yaron Sheffer <yaronf.ietf@gmail.com> wrote: > It sounds like a quick addition to DHCP - an extension that gets you 256 bits from the server, would solve 99% of the problem we have with embedded devices. It will not be sufficient for high-security environments, because an attacker might be listening on the local LAN.... Ahem. This is *exactly* the kind of reasoning I started this thread to investigate. (Though I certainly agree that a *single* DHCP packet containing a random bit string is easily attacked.) -- Jerry _______________________________________________ The cryptography mailing list cryptography@metzdowd.com http://www.metzdowd.com/mailman/listinfo/cryptography
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
home | help | back | first | fref | pref | prev | next | nref | lref | last | post |