-
-
Notifications
You must be signed in to change notification settings - Fork 644
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
Generated lockfiles header has the full path location of pants exposing personal data #15740
Labels
Comments
Hey @jbasila-orca , do you remember if you were using the standard |
asherf
added a commit
to asherf/pants
that referenced
this issue
Aug 18, 2022
asherf
added a commit
to asherf/pants
that referenced
this issue
Aug 18, 2022
asherf
added a commit
to asherf/pants
that referenced
this issue
Aug 19, 2022
asherf
added a commit
to asherf/pants
that referenced
this issue
Aug 19, 2022
asherf
added a commit
to asherf/pants
that referenced
this issue
Aug 19, 2022
asherf
added a commit
to asherf/pants
that referenced
this issue
Aug 19, 2022
Although this was the original, I'll close as a duplicate of #18202 since it has more and more modern context. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is more a privacy matter and security. The generated lock file contains in the header the location of the
pants
wrapper script that was used exposing the username and also the repository name2.11.1rc2
but I think it has been like this for a long time
This was run on MacOS, but I think the same will happen on other platforms
The text was updated successfully, but these errors were encountered: