Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Import personal access tokens with auth login --with-token #681
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
base: main
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
Import personal access tokens with auth login --with-token #681
Changes from all commits
b1ddc8714c33b8a2e8a69a2defe817cad54709798b283c4f945bc77b313c5b0File filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not doing this — and it is the third variation of one finding (this thread, auth.go:696 and auth.go:742 all say: a server that reflects the bearer token into an error body could get the candidate token into an error message or a trace file). The failure it would prevent needs the operator's own configured base URL to be a server that echoes Authorization headers back; Basecamp does not, and an operator pointing the CLI at a hostile host has already handed it the token in the request. The same error text reaches verbose output and trace files for every command the CLI runs with the stored credential, so a verification-only redaction would leave the class where it already lives; if the class is worth closing, the place is the observability hooks (redact bearer-shaped substrings once), not three sites in this PR. Leaving this open for Jeremy's call on whether hook-level redaction is wanted.
Uh oh!
There was an error while loading. Please reload this page.