diff options
author | Petr Štetiar <ynezz@true.cz> | 2023-05-17 22:08:12 +0200 |
---|---|---|
committer | Petr Štetiar <ynezz@true.cz> | 2023-05-18 08:19:17 +0200 |
commit | a7747e8670cb9bc92a28f3a20d07708c171a1b09 (patch) | |
tree | 2ecd89eaf8d22f2989ece04e6b035a1e0e9e6598 /COPYING | |
parent | c68c71eaa97189a7ed2840009a6fdfb370d69e5c (diff) | |
download | upstream-a7747e8670cb9bc92a28f3a20d07708c171a1b09.tar.gz upstream-a7747e8670cb9bc92a28f3a20d07708c171a1b09.tar.bz2 upstream-a7747e8670cb9bc92a28f3a20d07708c171a1b09.zip |
ci: fix check kernel patches job
Currently the check fails due to the following error:
warning: Not a git repository. Use --no-index to compare two paths outside a working tree
usage: git diff --no-index [<options>] <path> <path>
Thats likely caused by commit 1cb8cdbf0723 ("ci: use new buildbot worker
images with Debian 11") which contains a patched Git version with CVE
security fixes introduced in DLA-3239-2:
Multiple issues were found in Git, a distributed revision control
system. An attacker may cause other local users into executing arbitrary
commands, leak information from the local filesystem, and bypass
restricted shell.
Note: Due to new security checks, access to repositories owned and
accessed by different local users may now be rejected by Git; in case
changing ownership is not practical, git displays a way to bypass these
checks using the new "safe.directory" configuration entry.
So lets opt-out of this new behavior by setting `safe.directory=*` and
thus force Git to consider all Git repositories as safe regardless of
their owner, since we need to trust those sources anyway and it should
be likely more robust solution, then fiddling with filesystem
permissions.
Fixes: 1cb8cdbf0723 ("ci: use new buildbot worker images with Debian 11")
References: https://www.debian.org/lts/security/2022/dla-3239-2
Signed-off-by: Petr Štetiar <ynezz@true.cz>
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions