Repository navigation
fix(server): keep auth-like Codex files private to each home #23428
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
Open
juliusmarminge
wants to merge
6
commits into
main
Choose a base branch
from
fix/issue-8578
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+135
−16
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
25e9fe5
test(server): reproduce issue 8578 auth-like Codex entries leaking in…
juliusmarminge e85b25d
fix(server): Codex shadow homes keep auth-like files private
juliusmarminge af44fd7
Merge remote-tracking branch 'origin/main' into fix/issue-8578
juliusmarminge 488744d
test(server): stale auth.lock shadow links are removed, not rejected
juliusmarminge b0c255f
fix(server): remove auth-like shadow links older versions made instea…
juliusmarminge 28651d3
fix(server): drop any auth-like shadow link except auth.json instead …
juliusmarminge File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
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.
Script executed:
Repository: pingdotgg/t3code
Length of output: 7077
Script executed:
Repository: pingdotgg/t3code
Length of output: 42181
Web query:
Apple APFS default case insensitive case preserving file names documentation macOSResult:
Script executed:
Repository: pingdotgg/t3code
Length of output: 23719
Script executed:
Repository: pingdotgg/t3code
Length of output: 3152
Check the effective
auth.jsonpath before removing links.On a case-insensitive filesystem, an
AUTH.JSONsymlink is the effectiveauth.jsonentry. The scan removes it instead of raising the private-entry error. Check the lowercase path first to preserve rejection without changing cleanup on case-sensitive filesystems.Suggested fix