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
To this end, I have a secrets store called test-gopass-1, which gets cloned via a Personal Access Token from inside the workflow. However, after cloning the store, gopass seems unable to find the secret key in GPG and tries to create a new key from git author settings, despite the key very clearly existing in the gpg keyring.
The key being used is 0xF9CA7755347E6586, belonging to gopass-terraform-example <gopass-terraform-example@github>.
gopass creates a random key, but it can actually decrypt the secret via gopass show, despite thinking it has no key available during setup. If it actually tried to use the key it just created, it would not be able to read the secrets store.
The image is ubuntu-latest.
The key is imported through a secret called PGP_KEY, the PGP key ID is provided to the root store via a secret called PGP_KEY_ID.
Run gopass --yes setup \
gopass --yes setup \
--remote https://***@github.com/felixhammerl/test-gopass-1.git \
--alias test-gopass-1 \
--name "gopass-terraform-example" \
--email "gopass-terraform-example@github"
shell: /usr/bin/bash -e {0}
__ _ _ _ _ _ ___ ___
/'_ '\ /'_'\ ( '_'\ /'_' )/',__)/',__)
( (_) |( (_) )| (_) )( (_| |\__, \\__, \
'\__ |'\___/'| ,__/''\__,_)(____/(____/
( )_) | | |
\___/' (_)
🌟 Welcome to gopass!
🌟 Initializing a new password store ...
🔐 No useable cryptographic keys. Generating new key pair
🧪 Creating cryptographic key pair (gpg) ...
🎩 Gathering information for the gpg key pair ...
✅ Key pair for gpg generated
Passphrase: exerciser truck custodian rocker
⚠ You need to remember this very well!
⚠ 🔐 We need to unlock your newly created private key now! Please enter the passphrase you just generated.
✅ Key pair 0xAF428D93F835FF58 validated
🔐 Cryptographic keys generated
Joining existing team ...
🌟 Configuring your password store ...
✅ Configuration written
[test-gopass-1]Configuring git remote ...
[test-gopass-1]Cloning from the git remote ...
[test-gopass-1]✅ Done. Joined Team "test-gopass-1"
[test-gopass-1]⚠ You still need to request access to decrypt secrets!
The .gpg-id of felixhammerl/test-gopass-1:
0x7859E6520888D02E
0xF9CA7755347E6586
Expected behavior
gopass is able to access the secret located in gopass show test-gopass-1/dev/asdasd by identifying the key already present in gpg, without creating an additional key.
/usr/bin/gpg
gpg (GnuPG) 2.2.27
libgcrypt 1.9.4
Copyright (C) 2021 Free Software Foundation, Inc.
License GNU GPL-3.0-or-later <https://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Home: /home/runner/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2
Summary
I am trying to use gopass in Github Actions.
To this end, I have a secrets store called
test-gopass-1
, which gets cloned via a Personal Access Token from inside the workflow. However, after cloning the store, gopass seems unable to find the secret key in GPG and tries to create a new key from git author settings, despite the key very clearly existing in the gpg keyring.The key being used is
0xF9CA7755347E6586
, belonging togopass-terraform-example <gopass-terraform-example@github>
.gopass creates a random key, but it can actually decrypt the secret via
gopass show
, despite thinking it has no key available during setup. If it actually tried to use the key it just created, it would not be able to read the secrets store.The image is
ubuntu-latest
.The key is imported through a secret called
PGP_KEY
, the PGP key ID is provided to the root store via a secret calledPGP_KEY_ID
.Steps To Reproduce
Here is the action:
The log output of the
gopass setup
execution is:The
.gpg-id
offelixhammerl/test-gopass-1
:Expected behavior
gopass is able to access the secret located in
gopass show test-gopass-1/dev/asdasd
by identifying the key already present in gpg, without creating an additional key.Environment
gopass_1.15.8_linux_amd64.deb
wget https://github.com/gopasspw/gopass/releases/download/v1.15.8/gopass_1.15.8_linux_amd64.deb && sudo dpkg -i gopass_1.15.8_linux_amd64.deb
which gpg
:/usr/bin/gpg
gpg --version
:gpg --with-colons --with-fingerprint --fixed-list-mode --list-secret-keys
:Please let me know if you would like the debug logs
The text was updated successfully, but these errors were encountered: