From: Stefan Klug <stefan.klug@baslerweb.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: [PATCH 1/3] fetch2: Fix fetching of git repositories with kerberos authentication
Date: Mon, 18 Mar 2019 14:58:18 +0100 [thread overview]
Message-ID: <20190318135820.7344-2-stefan.klug@baslerweb.com> (raw)
In-Reply-To: <20190318135820.7344-1-stefan.klug@baslerweb.com>
When using pam_krb to login to a system KRB5CCNAME is set to the
corresponding kerberos auth cache file. The bitbake fetcher removes
this variable from the environment leading to a git authentication failure.
Also the fetcher ignores the normally used BB_ENV_[EXTRA_]WHITE
variables and relies on a hardcoded list.
Therefore it is impossible to fix this issue outside of bitbake.
Signed-off-by: Stefan Klug <stefan.klug@baslerweb.com>
---
lib/bb/fetch2/__init__.py | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/bb/fetch2/__init__.py b/lib/bb/fetch2/__init__.py
index f112067d..df8e83e7 100644
--- a/lib/bb/fetch2/__init__.py
+++ b/lib/bb/fetch2/__init__.py
@@ -830,6 +830,7 @@ def runfetchcmd(cmd, d, quiet=False, cleanup=None, log=None, workdir=None):
'GIT_SSH',
'GIT_SSL_CAINFO',
'GIT_SMART_HTTP',
+ 'KRB5CCNAME',
'SSH_AUTH_SOCK', 'SSH_AGENT_PID',
'SOCKS5_USER', 'SOCKS5_PASSWD',
'DBUS_SESSION_BUS_ADDRESS',
--
next prev parent reply other threads:[~2019-03-18 14:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 13:58 [PATCH 0/3] Fix some bitbake authentication issues Stefan Klug
2019-03-18 13:58 ` Stefan Klug [this message]
2019-03-18 23:44 ` [PATCH 1/3] fetch2: Fix fetching of git repositories with kerberos authentication Richard Purdie
2019-03-18 13:58 ` [PATCH 2/3] fetch2: Gracefully handle corrupt download-cache tarballs Stefan Klug
2019-03-18 23:45 ` Richard Purdie
2019-03-18 13:58 ` [PATCH 3/3] fetch2/wget: Fix authentication in checkstatus() of the wget fetcher Stefan Klug
2019-03-19 6:28 ` Andre McCurdy
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=20190318135820.7344-2-stefan.klug@baslerweb.com \
--to=stefan.klug@baslerweb.com \
--cc=bitbake-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.