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

initvm: add an option for additional Debian archive key location #375

Closed
wants to merge 1 commit into from

Conversation

yegorich
Copy link
Contributor

@yegorich yegorich commented Apr 4, 2023

The option keys_dir provides a path to the additional key location.

The use case is when you create an initvm on, for example, Ubuntu where the debian-archive-keyring package installs the keys to /usr/share/keyrings/. As elbe looks in /etc/apt/trusted.gpg.d for the keys, it ignores the ones in /usr/share/keyrings/.

Fixes #368

The option `keys_dir` provides a path to the additional key location.

The use case is when you create an initvm on, for example, Ubuntu
where the `debian-archive-keyring` package installs the keys to
`/usr/share/keyrings/`. As elbe looks in `/etc/apt/trusted.gpg.d`
for the keys, it ignores the ones in `/usr/share/keyrings/`.

Signed-off-by: Yegor Yefremov <[email protected]>
@yegorich
Copy link
Contributor Author

yegorich commented Apr 4, 2023

Should we use either /etc/apt/trusted.gpg.d or keys_dir?

@yegorich
Copy link
Contributor Author

What about setting keys_dir to /etc/apt/trusted.gpg.d by default and let keys_dir accept a list of directories separated by ;?

@bgermann
Copy link
Contributor

Closing in favour of #367

@bgermann bgermann closed this May 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

debian-archive-keyring handling
2 participants