Jeff King wrote: > On Tue, Dec 02, 2014 at 04:59:53PM -0800, Jonathan Nieder wrote: >> As long as you have no credential helpers configured, your GIT_ASKPASS >> based approach should work fine. > > Yeah, it's fine (as is GIT_ASKPASS=true). You could also provide a > credential helper that gives you an empty username and password. But in > both cases, I think that git will then feed the empty password to the > server again, resulting in an extra useless round-trip. You probably > instead want to say "stop now, git, there is nothing else to be done". > > We could teach the credential-helper code to do that (e.g., a helper > returns "stop=true" and we respect that). But I think you can do it > reasonably well today by making the input process fail. How can my scripts defend against a credential helper that I didn't set up that e.g. pops up a GUI window to ask for a password? Thanks, Jonathan -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html