On Tue, 2018-09-04 at 16:18 +1200, Paul Eggleton wrote: > Hi folks, > > In the layer index / RRS code I have found that if it tries to use > bitbake's git fetcher to access a git repository on github that has > been renamed or gone private via http/https, I get prompted for a > password interactively, presumably on the assumption that maybe if I > authenticate I might be able to see the repo. Here's an example git > command that will trigger it (trimmed from the actual command issued > by the fetcher): > > git ls-remote http://github.com/symless/synergy.git > > This can be disabled by setting the environment variables GIT_ASKPASS > to an empty string and GIT_TERMINAL_PROMPT to 0, which allows the > fetch command to fail immediately. I could conceivably do this in the > layer index / RRS scripts, but it occurred to me that perhaps this > should be disabled in bitbake's git fetcher itself. We need to decide > whether or not interactive password prompts should be allowed during > a fetch operation (I'm guessing not, although I have a feeling this > might be a "spacebar heating" situation for some). > > Thoughts? In particular, does anyone object to disabling such > interactive prompts during fetching?
I think this should be disabled in the fetcher. We don't support input from stdin during builds and this isn't good behaviour. stdin tends to be redirected to /dev/null which would cause read errors but we should also perhaps revisit and check that happens in all the codepaths. It may be the way the layer index is using the parser code. Could you check this also happens with that url in a normal build? Cheers, Richard _______________________________________________ Openembedded-architecture mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-architecture
