-
Notifications
You must be signed in to change notification settings - Fork 8k
Fix apt-get ascii GPG key #19138
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
Merged
Merged
Fix apt-get ascii GPG key #19138
Changes from all commits
Commits
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
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
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.
Oh, erm, silly question; would need
sudo curlnow? (or| sudo tee)? Looks like/etc/apt/keyringsmay not be accessible by everyone;The
sudo chmod a+r /etc/apt/keyrings/docker.gpgwas added for some cloud systems where permissions were not allowing traversing the directories, causing things to fail; #17070 (comment)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.
^ @dvdksn @tianon
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.
ah, yes. Would
sudo curldo or do we need tee?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.
sudo curlis probably the easy one, but thinking if cURL depends on user-directories (thereforesudopotentially looking for config inroot's home-dir and such. running cURL as root may have a slightly bigger attack surface (vstee) as well, but perhaps that's just looking for issues.I'm sure @tianon has opinions as well if
curl | sudo teeis preferred oversudo curlThere 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.
Yeah, attack surface is all that came to mind for me (generally, running
curlas root is probably safe, but not the best idea). That being said, if we usetee, we should probably also send the output to/dev/null, so I'd personally thinksudo curlis probably the simpler answer to keep the docs easier to understand (users that paranoid are hopefully not even using this line and are instead doing things like fetching the key by full fingerprint from elsewhere and/or doing deeper verification after download).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.
Yup,
sudo curlis definitely easier to grasp, so perhaps it's an ok trade-off (readability over "fully correct").We should look at the directory permissions though (the sudo chmod a+r /etc/apt/keyrings/docker.gpg)
as I recall there were some real-life scenarios outside of the user's control where things broke without #17070