netdev - Re: [PATCH net 0/3] net/sched Bind logic fixes for cls_fw, cls_u32 and cls

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20230725130917.36658b63@kernel.org>
Date: Tue, 25 Jul 2023 13:09:17 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: valis <sec@...is.email>
Cc: Paolo Abeni <pabeni@...hat.com>, netdev@...r.kernel.org,
 jhs@...atatu.com, xiyou.wangcong@...il.com, jiri@...nulli.us,
 davem@...emloft.net, edumazet@...gle.com, pctammela@...atatu.com,
 victor@...atatu.com, ramdhan@...rlabs.sg, billy@...rlabs.sg, Greg
 Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: [PATCH net 0/3] net/sched Bind logic fixes for cls_fw, cls_u32
 and cls_route

On Tue, 25 Jul 2023 21:05:23 +0200 valis wrote:
> The document you quoted does not forbid pseudonyms.
> In fact, it was recently updated to clarify that very fact.

We don't know who you are. To my understanding the adjustment means
that you are not obligated to use the name on your birth certificate
but we need to know who you are.

Why is it always "security" people who try act like this is some make
believe metaverse. We're working on a real project with real licenses
and real legal implications.

Your S-o-b is pretty much meaningless. If a "real" person can vouch for
who you are or put their own S-o-b on your code that's fine.