OpenWrt/LEDE Project

  • Status New
  • Percent Complete
  • Task Type Feature Request
  • Category Other
  • Assigned To No-one
  • Operating System All
  • Severity Low
  • Priority Very Low
  • Reported Version All
  • Due in Version Undecided
  • Due Date Undecided
  • Private
Attached to Project: OpenWrt/LEDE Project
Opened by Zbyněk Kocur - 17.07.2017

FS#911 - Problem with login into private git repos

I am not able to use packages from my private git repos which needs login. The system during the build process don’t ask me for login as before.

Here is the verbose log output:

make[3]: Leaving directory `/home/flowtester/caes/platform/package/base-files'
make[3]: Entering directory `/home/flowtester/caes/platform/package-bumblebee/packages/libdevereader'
mkdir -p /home/flowtester/caes/platform/dl
SHELL= flock /home/flowtester/caes/platform/tmp/.libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860.tar.gz.flock -c '          echo "Checking out files from the git repository..."; mkdir -p /home/flowtester/caes/platform/tmp/dl && cd /home/flowtester/caes/platform/tmp/dl && rm -rf libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860 && [ \! -d libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860 ] && git clone libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860 && (cd libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860 && git checkout daa94e0fad44a000892570665e6c792fd9cad860 && git submodule update --init --recursive) && echo "Packing checkout..." && export TAR_TIMESTAMP=`cd libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860 && git log -1 --format='\''@%ct'\''` && rm -rf libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860/.git &&  tar --numeric-owner --owner=0 --group=0 --sort=name ${TAR_TIMESTAMP:+--mtime="$TAR_TIMESTAMP"} -c libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860 |     gzip -nc > /home/flowtester/caes/platform/tmp/dl/libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860.tar.gz && mv /home/flowtester/caes/platform/tmp/dl/libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860.tar.gz /home/flowtester/caes/platform/dl/ && rm -rf libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860;     '
Checking out files from the git repository...
Cloning into 'libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860'...
fatal: Authentication failed for ''
make[3]: *** [/home/flowtester/caes/platform/dl/libdevereader-1.1.7-daa94e0fad44a000892570665e6c792fd9cad860.tar.gz] Error 128
make[3]: Leaving directory `/home/flowtester/caes/platform/package-bumblebee/packages/libdevereader'
make[2]: *** [package/feeds/bumblebee/libdevereader/compile] Error 2
make[2]: Leaving directory `/home/flowtester/caes/platform'
make[1]: *** [/home/flowtester/caes/platform/staging_dir/target-mipsel_24kc_musl/stamp/.package_compile] Error 2
make[1]: Leaving directory `/home/flowtester/caes/platform'
make: *** [world] Error 2

If I try it manually from cli everythings works but not during the prepare process ....

Project Manager
Baptiste Jonglez commented on 17.07.2017 09:29


It's not realistic to have user interaction during the build process.

You should setup authentication to your git repository using SSH keys, so that it does not need user interaction.

Zbyněk Kocur commented on 17.07.2017 09:32

I know, it is not common, but few days ago it works and now not. A lot of project is setup by this way. Is it a problem to use this way for autentization?

Project Manager
Baptiste Jonglez commented on 17.07.2017 09:39

Can you point out which commit broke this? You can use git-bisect for this.

It's not a problem per se, it's just an uncommon use-case. Also it does not seem very practical to have to enter a login and a password each time you want to build.

Zbyněk Kocur commented on 17.07.2017 09:43

Yes, I know, but the git hosting system which we use doesn't support user ssl keys. For now it is not possible to change it.

I would like to know what hapends? It is some modification in lede? OpenWRT works as before ....

Project Manager
Baptiste Jonglez commented on 17.07.2017 09:56

The build system has changed a lot since OpenWrt, in particular to be faster. It seems like this change is an unwanted side-effect. Did this work with LEDE before? If so, please find which LEDE commit broke support for this use-case.

As a workaround, you can use GIT_ASKPASS or core.askPass. For instance, something like this:

git config core.askPass "cat /home/myuser/mygitpassword.txt"

where mygitpassword.txt contains the password. Or use something more complicated with a secure keystore.

Zbyněk Kocur commented on 19.07.2017 08:37

I try the askPass variable but it doesnt help me. In CLI is login OK, but not in LEDE environment.

Zbyněk Kocur commented on 27.11.2017 19:56


commmit ID bad2f9c4dc39ff8a8bdc7ad4bd86f2c068457a5a works fine and shell ask for login and password in case of git and https. The problem is in file include/ If I use version from oldest LEDE it works fine. New version does not ask for login to https.

The problem is in variable GIT_ASKPASS which is set to /bin/true after disable it, everything works fine.

diff --git a/include/ b/include/
index 3f5a750030..6e09230308 100644
--- a/include/
+++ b/include/
@@ -23,7 +23,7 @@ HOSTCC ?= $(CC)
 export REVISION
 export GIT_CONFIG_PARAMETERS='core.autocrlf=false'
-export GIT_ASKPASS:=/bin/true
+#export GIT_ASKPASS:=/bin/true
 export MAKE_JOBSERVER=$(filter --jobserver%,$(MAKEFLAGS))
 export GNU_HOST_NAME:=$(shell $(TOPDIR)/scripts/config.guess)
 export HOST_OS:=$(shell uname)
Zbyněk Kocur commented on 10.12.2017 06:35

I think it would be better to have a login queried by default. Now an error occurs and the user does not know ....


Available keyboard shortcuts


Task Details

Task Editing