linux-kernel - Re: [PATCH linux-next] kallsyms: Use strscpy() instead of strlcpy()

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <Y1OGELD2BP2KB1nG@kroah.com>
Date:   Sat, 22 Oct 2022 07:56:32 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Kees Cook <keescook@...omium.org>
Cc:     jinpeng Cui <cuijinpeng666@...il.com>,
        Zeal Robot <zealci@....com.cn>, alan.maguire@...cle.com,
        ast@...nel.org, bpf@...r.kernel.org, cui.jinpeng2@....com.cn,
        jolsa@...nel.org, linux-kernel@...r.kernel.org,
        peterz@...radead.org, stephen.s.brennan@...cle.com
Subject: Re: [PATCH linux-next] kallsyms: Use strscpy() instead of strlcpy()

On Fri, Oct 21, 2022 at 09:17:10AM -0700, Kees Cook wrote:
> On Thu, Oct 20, 2022 at 02:43:52PM +0200, Greg KH wrote:
> > > I am very sorry if the patches from zte.com.cn
> > > in the past few months have made you angry,
> > > we have decided to fix the problem you pointed out
> > > as soon as possible.
> > > Our company's mailbox name@....com.cn
> > > cannot send emails to the external network,
> > > so we use name@...il.com to send patches;
> > 
> > You all have been warned numerous times over many weeks and months and
> > never responded to our emails.
> > 
> > We have no proof that using gmail accounts is actually coming from a ZTE
> > employee, so until that happens, we can not take your changes (not to
> > mention the basic fact that you all keep ignoring our review comments,
> > which is a good enough reason to ignore them.)
> 
> Aren't there a few solutions here?
> 
> 1) Just send the emails from @gmail with matching S-o-b.

As we know these developers are claiming to be from a company that we
can not confirm they are actually working for, no, we can't take their
contributions as that goes against the DCO (anonymous contributions).

> 2) Send an @zte.com.cn to lkml to confirm their @gmail/@....com.cn mapping.

That would be great, but so far no one that I have contacted from ZTE
has been able to confirm that these are actually ZTE developers.

> 3) Fix the email systems.

That would be the best thing for them to do, and would solve the problem
for everyone at their company.  Hopefully that happens soon.

thanks,

greg k-h