You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Got this issue when I was loading a key in a fresh Docker Container.
after 2nd call to the function the key fingerprint was valid.
That happens because the stdout in this case is:
gpg: directory /root/.gnupg' created gpg: new configuration file /root/.gnupg/gpg.conf' created
gpg: WARNING: options in /root/.gnupg/gpg.conf' are not yet active during this run gpg: keyring /root/.gnupg/secring.gpg' created
gpg: keyring `/root/.gnupg/pubring.gpg' created
gpg: /root/.gnupg/trustdb.gpg: trustdb created
The text was updated successfully, but these errors were encountered:
Got this issue when I was loading a key in a fresh Docker Container.
after 2nd call to the function the key fingerprint was valid.
That happens because the stdout in this case is:
gpg: directory
/root/.gnupg' created gpg: new configuration file/root/.gnupg/gpg.conf' createdgpg: WARNING: options in
/root/.gnupg/gpg.conf' are not yet active during this run gpg: keyring/root/.gnupg/secring.gpg' createdgpg: keyring `/root/.gnupg/pubring.gpg' created
gpg: /root/.gnupg/trustdb.gpg: trustdb created
The text was updated successfully, but these errors were encountered: