Skip to content
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

Doc: Installation guide should avoid using apt-key #216

Open
taxmeifyoucan opened this issue Nov 13, 2022 · 1 comment
Open

Doc: Installation guide should avoid using apt-key #216

taxmeifyoucan opened this issue Nov 13, 2022 · 1 comment
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@taxmeifyoucan
Copy link
Member

Installation guide suggest downloading PGP key of the maintainer from a keyserver and then adding it as trusted key using apt-key. This is easy and clear way of adding the repository, however apt-key is being deprecated since it can enable certain security vulnerabilities. In the future releases of Debian/Ubuntu, it won't be supported and docs should adopt another way of adding the repo.

Seems like a proper way would be to copy the gpg file to keyrings directory and refer to it in the deb repo sources.list, e.g. Brave offers pretty simple instructions which seem correct.

I am interested in your opinion, maybe it is not a considerable security issue but the software deprecation should be taken into account for the future.

@taxmeifyoucan taxmeifyoucan added bug Something isn't working documentation Improvements or additions to documentation labels Nov 13, 2022
@Kixunil
Copy link
Collaborator

Kixunil commented Nov 14, 2022

Yep, it is definitely planned for bullseye to change the doc. It's definitely not a security issue (all packages have root anyway). My understanding is that the Debian team considers it a cleaner approach (easier to manage the keys) and I agree with this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants