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] [thread-next>] [day] [month] [year] [list]
Date:   Sun, 20 Feb 2022 11:18:28 +0200
From:   Ido Schimmel <>
To:     Hans Schultz <>
        Hans Schultz <>,
        Andrew Lunn <>,
        Vivien Didelot <>,
        Florian Fainelli <>,
        Vladimir Oltean <>,
        Roopa Prabhu <>,
        Nikolay Aleksandrov <>,
        Shuah Khan <>,
        Stephen Suryaputra <>,
        David Ahern <>,
        Ido Schimmel <>,
        Petr Machata <>,
        Amit Cohen <>,
        Po-Hsu Lin <>,
        Baowen Zheng <>,,,
Subject: Re: [PATCH net-next v3 1/5] net: bridge: Add support for bridge port
 in locked mode

On Fri, Feb 18, 2022 at 04:51:44PM +0100, Hans Schultz wrote:
> In a 802.1X scenario, clients connected to a bridge port shall not
> be allowed to have traffic forwarded until fully authenticated.
> A static fdb entry of the clients MAC address for the bridge port
> unlocks the client and allows bidirectional communication.
> This scenario is facilitated with setting the bridge port in locked
> mode, which is also supported by various switchcore chipsets.
> Signed-off-by: Hans Schultz <>

With Nik's comment fixed:

Reviewed-by: Ido Schimmel <>

Powered by blists - more mailing lists