New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker registry token defaults to "A" #16669
Comments
Because GitHub Packages is the default registry and it requires an authentication header (even though the value is bogus). It can be customised with |
Unfortunately it seems those environment variables are not respected if set to nothing:
|
Correct. To ensure we've understood correctly: you have a private Artifactory but it does not have any authentication? |
There is authentication but we allow anonymous access on repository mirrors (remote repositories) on our private Artifactory instance. Hence homebrew-remote which mirrors ghcr.io does not require authentication. We could create an account for homebrew access but I'd prefer not to as that creates additional overhead for password/token rotation. |
We'll review a PR to fix this. |
A potential quick fix for this might be to set
Lines 955 to 963 in a570e4d
One blind spot: Is sending |
I think this is the case. |
@colindean can you open a PR? Thanks. |
brew doctor
outputVerification
brew doctor
output" above saysYour system is ready to brew.
and am still able to reproduce my issue.brew update
twice and am still able to reproduce my issue.brew install wget
. If they do, open an issue at https://github.com/Homebrew/homebrew-core/issues/new/choose instead.brew config
outputWhat were you trying to do (and why)?
Connect to a private repository using anonymous access
What happened (include all command output)?
The default Authorization: Bearer token sent is QQ== ("A"). As a result anonymous access fails.
What did you expect to happen?
The request does not attempt to send an auth header because there is no token setup. Why is the default token "A"?
Step-by-step reproduction instructions (by running
brew
commands)The text was updated successfully, but these errors were encountered: