Supplying passwords this way is a terrible idea, and isn't supported (there's a comment in git fetcher source stating that explicitly). You should transition everything to ssh (at which point the issue will go away anyway), or place the https secrets into a more secure location (man gitcredentials may help).
Alex On Tue, 21 May 2024 at 15:38, Lukas Weiß via lists.yoctoproject.org <lukas.weiss=janitza...@lists.yoctoproject.org> wrote: > > Hello there, > i just updated our Yocto Project to latest 5.0 release. First tests went > well, but now after a subsequent repo-update (tag=yocto-5.0) i have problems > with call of most bitbake calls because of an error in some recipes with code > in our own repository: Clean build runs without problems, but when i run > fetch for any recipe, i get the following error: > > $ bitbake -C fetch myapp > ... > bb.data_smart.ExpansionError: Failure expanding variable > fetcher_hashes_dummyfunc[vardepvalue], expression was > ${@bb.fetch.get_hashvalue(d)} which triggered exception FetchError: Fetcher > failure: Fetch command export PSEUDO_DISABLED=1; export > DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/11510/bus"; export > GIT_SSH="/home/admin/workspaces/yocto/build/conf/ssh_util/yocto_ssh.sh"; > export PATH="(...)"; export HOME="/home/admin"; git -c gc.autoDetach=false -c > core.pager=cat -c safe.bareRepository=all ls-remote > https://gitreader:xxxxxxx...@repo.srv/swupdate.git failed with exit code > 128, output: > fatal: Authentication failed for 'https://repo.srv/swupdate.git/' > > (shortened, full output see attachment; anonymized) > > My Recipe of swupdate uses > > SRC_URI = > "git://repo.srv/swupdate.git;protocol=https;user=${AUTH_SCM_USER}:${AUTH_SCM_PASSWD};branch=${BRANCH}" > > I have multiple Recipes using this scheme, most are working, three not. I can > not find a difference. When i run the given command (green) with hosts git, > everything works fine (so it is not really a auth problem!) > > I figured out, that the problem belongs to the git ls-remote command of the > git-remote-https program in recipes recipe-sysroot-native dir > (u-boot-plat/2019.01-/recipe-sysroot-native/usr/share/git-core/git-remote-https). > I can even reproduce this, when i run the ls-remote git command manually > with my hosts git, with GIT_EXEC_PATH-Env variable set to the git-core dir in > recipe-sysroot-native. When i replace the git-remote-https program with the > hosts one, everything runs fine. > > Any ideas what is going wrong here? > > PS: I didn't have the Problem on older Yocto-Versions. > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#63156): https://lists.yoctoproject.org/g/yocto/message/63156 Mute This Topic: https://lists.yoctoproject.org/mt/106223085/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-