netdev - Re: [PATCH V6 net-next] LISP: Locator/Identifier Separation Protocol

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20140627.122843.774074134481698671.davem@davemloft.net>
Date:	Fri, 27 Jun 2014 12:28:43 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	lojakab@...co.com
Cc:	chris@...icalelegance.com, netdev@...r.kernel.org,
	vermagan@...co.com
Subject: Re: [PATCH V6 net-next] LISP: Locator/Identifier Separation
 Protocol

From: Lori Jakab <lojakab@...co.com>
Date: Fri, 27 Jun 2014 10:31:57 +0300

> The OVS datapath's flow table is also influenced by traffic patterns
> sent by external hosts.  But while the IPv4 routing table is not
> optional for a networked host, OVS and LISP are, and people deploying
> them can still find value using them, in controlled environments at
> least.

You haven't shown how this is not exploitable if remote entities can
control the contents of your tables and how frequently they must be
updated.

I also worry about OVS, for the same reasons.

It isn't an answer to say that these technologies work fine if you
lock up the machine into a controlled environemt.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html