From: dev-faha@t-online.de
To: openembedded-core@lists.openembedded.org
Subject: CVE-2022-24765 Git Errors with Bitbake
Date: Tue, 26 Apr 2022 01:13:53 -0700 [thread overview]
Message-ID: <dwNG.1650960833949086015.bRfk@lists.openembedded.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 524 bytes --]
Hello everyone,
since the patch for CVE-2022-24765 (uncontrolled search for git repositories) arrived we have problems using Git as package source. For some reason git thinks that the repositories do not belong to the user who is invoking the bitbake command, even though when checking the file permission manually they seem to be correct:
"fatal: unsafe repository ('...' is owned by someone else)"
So is bitbake using some mechanism (e.g. fake root?) to invoke the git commands? Is there a workaround to fix this?
[-- Attachment #2: Type: text/html, Size: 550 bytes --]
next reply other threads:[~2022-04-26 8:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 8:13 dev-faha [this message]
2022-04-26 8:23 ` [OE-core] CVE-2022-24765 Git Errors with Bitbake Alexander Kanavin
2022-05-02 12:02 ` dev-faha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dwNG.1650960833949086015.bRfk@lists.openembedded.org \
--to=dev-faha@t-online.de \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox