command init: don't use user's gnupg configuration file #234
Conversation
This file contains 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
if user's gnupg configuration file contained options to include other keyrings, then 'elbe-keyring' wasn't created at all gpg error message if gnupg conf has keyring option: gpg: keyblock resource '.../elbe/initvm/.elbe-in/elbe-keyring': No such file or directory gpg: key 0x36AA35FF22BB8F84: 1 signature not checked due to a missing key gpg: no writable keyring found: Not found gpg: error reading '[stdin]': General error gpg: import from '[stdin]' failed: General error gpg: Total number processed: 0 Because of that resulting 'elbe-keyring.gpg' didn't had any PGP keys specified in initvm.xml file. Another problem is that without '--no-options' keys from other user-defined keyrings leaked into resulting elbe-keyring.gpg installed into build vm. Closes Linutronix#233 Signed-off-by: Andrey Skvortsov <andrej.skvortzov@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
if user's gnupg configuration file contained options to include
other keyrings, then 'elbe-keyring' wasn't created at all
gpg error message if gnupg conf has keyring option:
gpg: keyblock resource
'.../elbe/initvm/.elbe-in/elbe-keyring':
No such file or directory
gpg: key 0x36AA35FF22BB8F84: 1 signature not checked due to a missing key
gpg: no writable keyring found: Not found
gpg: error reading '[stdin]': General error
gpg: import from '[stdin]' failed: General error
gpg: Total number processed: 0
Because of that resulting 'elbe-keyring.gpg' didn't had any
PGP keys specified in initvm.xml file.
Another problem is that without '--no-options' keys from other
user-defined keyrings leaked into resulting elbe-keyring.gpg installed
into build vm.
Closes #233
Signed-off-by: Andrey Skvortsov andrej.skvortzov@gmail.com