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]
Date:   Tue, 22 Feb 2022 10:30:02 -0800
From:   Jakub Kicinski <kuba@...nel.org>
To:     Horatiu Vultur <horatiu.vultur@...rochip.com>,
        Casper Andersson <casper@...an.se>
Cc:     Steen Hegelund <Steen.Hegelund@...rochip.com>,
        "David S. Miller" <davem@...emloft.net>,
        "Lars Povlsen" <lars.povlsen@...rochip.com>,
        <UNGLinuxDriver@...rochip.com>, <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next] net: sparx5: Support offloading of bridge port
 flooding flags

On Sat, 19 Feb 2022 15:56:48 +0100 Horatiu Vultur wrote:
> The 02/18/2022 20:26, Jakub Kicinski wrote:
> > > I apologize. This seems to be Protonmail's doing. When I look at the
> > > web interface for Protonmail I can see that you are the only recipient
> > > it says PGP encrypted for. This is probably because Protonmail will
> > > automatically encrypt when both ends use Protonmail. Though I do not see
> > > this indication on your reply. I tried switching to PGP/Inline instead
> > > of PGP/MIME for this message. I hope this works.  Otherwise, I can
> > > resubmit this patch using another email address. I did not find a way
> > > to disable the automatic encryption. Or if you have any other
> > > suggestions to get around this.  
> > 
> > If I'm the only one who didn't get the plain text version - it's not
> > a big deal.  
> 
> I also have problems seeing Casper's patch.

Looks like Dave marked the patch as Changes Requested in patchwork.
Casper, could you repost after all?

> The only comment that I have to the patch, it would be nice to implement
> also the SWITCHDEV_ATTR_ID_PORT_PRE_BRIDGE_FLAGS callback. But I presume
> that can be added later on.

Perhaps making it a two patch series and also addressing Horatiu's
request?

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ