From: Mahesh Bandewar mahe...@google.com
Date: Thu, 18 Jun 2015 11:30:54 -0700
Actor and Partner details can be accessed via proc-fs, sys-fs
entries or netlink interface. These interfaces are world readable
at this moment. The earlier patch-series made the LACP communication
secure to avoid
On Thu, Jun 18, 2015 at 8:00 PM, Andy Gospodarek
go...@cumulusnetworks.com wrote:
On Thu, Jun 18, 2015 at 11:30:54AM -0700, Mahesh Bandewar wrote:
Actor and Partner details can be accessed via proc-fs, sys-fs
entries or netlink interface. These interfaces are world readable
at this moment.
On Fri, Jun 19, 2015 at 10:02:39AM -0700, Mahesh Bandewar wrote:
On Thu, Jun 18, 2015 at 8:00 PM, Andy Gospodarek
go...@cumulusnetworks.com wrote:
[...]
With this patch, actor_oper_port_state and partner_oper.port_state are
not displayed in /proc, but that information is available via
On Thu, Jun 18, 2015 at 11:30:54AM -0700, Mahesh Bandewar wrote:
Actor and Partner details can be accessed via proc-fs, sys-fs
entries or netlink interface. These interfaces are world readable
at this moment. The earlier patch-series made the LACP communication
secure to avoid nuisance attack
Actor and Partner details can be accessed via proc-fs, sys-fs
entries or netlink interface. These interfaces are world readable
at this moment. The earlier patch-series made the LACP communication
secure to avoid nuisance attack from within the same L2 domain but
it did not prevent someone
