[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEBa_SASfBCb8TCS=qzNw90ZNE+wzADmY1_VtJiBnmixXgt6NQ@mail.gmail.com>
Date: Tue, 25 Jul 2023 23:36:14 +0200
From: valis <sec@...is.email>
To: Jakub Kicinski <kuba@...nel.org>
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, Jul 25, 2023 at 10:09 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> 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.
Hi Jakub!
>
> 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.
I could start a discussion about what makes a name valid, but I'm
pretty sure netdev is not the right place for it.
>
> 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.
I posted my patches to this mailing list per maintainer's request and
according to the published rules of the patch submission process as I
understood them.
Sorry if I misinterpreted something and wasted anybody's time.
I'm not going to resubmit the patches under a different name.
Please feel free to use them if someone is willing to sign off on them.
Best regards,
valis
Powered by blists - more mailing lists