docs: non-standard browser profiles (#31) - #35
Merged
Conversation
Firefox-family browsers store cookie values in plaintext, so a profile in an unusual path (e.g. Floorp/LibreWolf) can be read straight into GH_SESSION_TOKEN without a --cookie-path flag.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Rescopes #31 from a
--cookie-pathflag to a docs note, per discussion on the issue.Adds a minimal Non-standard browser profiles note to the Session token override section: Firefox-family browsers (incl. forks like Floorp/LibreWolf) store cookie values in plaintext, so a profile in an unusual path can be read straight into
GH_SESSION_TOKEN— no new flag or auth-resolution source needed.Refs #31.