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: Windows password security audit tool. GUI, reports in PDF.

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

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

On Thu, Oct 20, 2022 at 09:05:47AM +0000, cuijinpeng666@...il.com wrote:
> From: Jinpeng Cui <cui.jinpeng2@....com.cn>
> 
> The implementation of strscpy() is more robust and safer.
> 
> Reported-by: Zeal Robot <zealci@....com.cn>
> Signed-off-by: Jinpeng Cui <cui.jinpeng2@....com.cn>

Again, please stop.

I have told you, and others who are purporting to send patches from ZTE
to please stop using gmail.com addresses as there is no way to verify
that you really are from ZTE.  You are potentially lying about who you
are here, which is not allowed in kernel development for obvious
reasons.

Also, these email addresses are "one way only" with no responses ever
being recieved, and so they have been banned from vger mailing lists.

I will go ask this one to be banned as well.

Please work with your employer to get their email settings fixed up so
that you can properly send patches.  Do NOT abuse gmail for this as
that's not ok.

greg k-h