linux-kernel - Re: [PATCH] kheaders: explicitly define file modes for archived headers

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: <CAK7LNAS-sCFCh6Hyrj4qra6b-Bx4HjQLt_FfJb=FB2xUWE_YiA@mail.gmail.com>
Date: Thu, 30 May 2024 23:30:09 +0900
From: Masahiro Yamada <masahiroy@...nel.org>
To: Matthias Männich <maennich@...gle.com>
Cc: linux-kernel@...r.kernel.org, kernel-team@...roid.com, gprocida@...gle.com, 
	stable@...r.kernel.org, linux-kbuild@...r.kernel.org, 
	Joel Fernandes <joel@...lfernandes.org>
Subject: Re: [PATCH] kheaders: explicitly define file modes for archived headers

On Tue, May 28, 2024 at 8:33 PM Matthias Männich <maennich@...gle.com> wrote:
>
> From: Matthias Maennich <maennich@...gle.com>
>
> Build environments might be running with different umask settings
> resulting in indeterministic file modes for the files contained in
> kheaders.tar.xz. The file itself is served with 444, i.e. world
> readable. Archive the files explicitly with 744,a+X to improve
> reproducibility across build environments.
>
> --mode=0444 is not suitable as directories need to be executable. Also,
> 444 makes it hard to delete all the readonly files after extraction.
>
> Cc: stable@...r.kernel.org
> Cc: linux-kbuild@...r.kernel.org
> Cc: Masahiro Yamada <masahiroy@...nel.org>
> Cc: Joel Fernandes <joel@...lfernandes.org>
> Signed-off-by: Matthias Maennich <maennich@...gle.com>
> ---

Applied to linux-kbuild.
Thanks!



-- 
Best Regards
Masahiro Yamada