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: <19ab92bfcaa.fc063ed1450036.1152663278874953682@azey.net>
Date: Tue, 25 Nov 2025 05:00:59 +0100
From: azey <me@...y.net>
To: "Jakub Kicinski" <kuba@...nel.org>
Cc: "David Ahern" <dsahern@...nel.org>,
	"nicolasdichtel" <nicolas.dichtel@...nd.com>,
	"David S. Miller" <davem@...emloft.net>,
	"Eric Dumazet" <edumazet@...gle.com>,
	"Paolo Abeni" <pabeni@...hat.com>, "Simon Horman" <horms@...nel.org>,
	"netdev" <netdev@...r.kernel.org>,
	"linux-kernel" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] net/ipv6: allow device-only routes via the multipath
 API

On 2025-11-25 04:25:50 +0100  Jakub Kicinski <kuba@...nel.org> wrote:
> On Tue, 25 Nov 2025 04:15:25 +0100 azey wrote:
> > On 2025-11-25 04:00:44 +0100  Jakub Kicinski <kuba@...nel.org> wrote:
> > > On Mon, 24 Nov 2025 14:52:45 +0100 azey wrote:  
> > > > Signed-off-by: azey <me@...y.net>  
> > > 
> > > We need real/legal names because licenses are a legal matter.
> > > -- 
> > > pw-bot: cr  
> > 
> > I was under the impression this was clarified in d4563201f33a
> > ("Documentation: simplify and clarify DCO contribution example
> > language") to not be the case, are there different rules for this
> > subsystem? I think it qualifies as a "known identity" since I use
> > the alias basically everywhere (github, website, GPG, email, etc).
> 
> My understanding is that if I know you, I can apply your patch even 
> if you use your nick name (rather than what you have in your passport
> letter for letter).
> 
> I don't know you.
> 
> If you're saying that I can do some research and find out who you are
> please be aware that we deal with 700 individual per release just
> in networking.

My main concern is that I keep my on/offline identities very separated,
so you couldn't find me by my real name anywhere online. And offline,
my legal name is common enough that you couldn't single me out by it
alone either.

My understanding is that the sign-off name should be what you can
identify and contact me by in case of any problems, which my legal
name is not. As per Linus' commit I linked:

> the sign-off needed to be something we could check back with.

> we've always accepted nicknames

> the wording [..] shouldn't be causing unnecessary angst and pain,
> or scare away people who go by preferred naming.

If the concern is that it isn't unique enough, I could change it to
azey7f as that's a username I use when just azey isn't available,
though my commits are always authored "azey <me@...y.net>".

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ