Like Cupcake stated, you can’t retain the old signature from the unsquashed commits, but you can sign the new squashed commit if you rebase like this: git rebase –interactive –gpg-sign=myemail@example.com HEAD~4 Adding –gpg-sign=myemail@example.com as an argument will sign the final squashed commit.
Note: Adding the -S option all the time can be cumbersome. In git 2.0 and later, you can add a config which will take care of that option for you. See commit 2af2ef3 by Nicolas Vigier (boklm): Add the commit.gpgsign option to sign all commits If you want to GPG sign all your commits, you … Read more
What about: $ echo “hello” | gpg –symmetric –armor –passphrase “asdf” —–BEGIN PGP MESSAGE—– Version: GnuPG v1.4.11 (Darwin) jA0EAwMCWfhRZo0AiwVgyRw5Q26Tf+i6OCiQOVoUNJZEfz5ekBJw6BdVpE88 =ecV3 —–END PGP MESSAGE—– If this is what you’re looking for, you’ll want to setup gpg-agent to handle the passphrase… Passing it in from the command line like that is fairly insecure (as any program on … Read more
The only way to use a specific public key file like a keyring is if the file is in the GPG (OpenPGP) file format and not an ASCII armoured version (e.g. pubkey.gpg not pubkey.asc). So this will verify the file: gpg –no-default-keyring –keyring /path/to/pubkey.gpg –verify /path/to/file.txt.gpg And this will not: gpg –no-default-keyring –keyring /path/to/pubkey.asc –verify … Read more
Just set it up in a profile in settings.xml and activate it by default: <settings> <profiles> <profile> <id>gpg</id> <properties> <gpg.executable>gpg2</gpg.executable> <gpg.passphrase>mypassphrase</gpg.passphrase> </properties> </profile> </profiles> <activeProfiles> <activeProfile>gpg</activeProfile> </activeProfiles> </settings> As you can see you can do that with any property .. e.g. also other usernames and passwords for the jarsigner plugin and so on. This should … Read more
If you try to verify the signature using gpg –verify <pkg>.key you’ll get an output like the following: gpg: Signature made 02/17/05 14:02:42 GTB Standard Time using DSA key ID BE216115 gpg: Can’t check signature: No public key The key ID you are looking for is BE216115, so you ask gpg to retrieve it using: … Read more
If you configured Automatic Git commit signing with GPG on macOS and you see this error comment out no-tty in ~/.gnupg/gpg.conf as suggested by Fahl-Design. This will also allow you to generate new GPG keys following the GitHub instructions for new keys.
First you need check if there is a gpg key for your ID. $ gpg –list-key If you have should appear something like this: pub 2048R/6AB3587A 2013-05-23 uid xxx (gpg for xxx) sub 2048R/64CB327A 2013-05-23 If there is no gpg key. You should create $ gpg –gen-key Next you have this output: gpg (GnuPG) 2.0.14; … Read more
Even I had the above issue in Ubuntu 20 WSL, I tried all the below | above suggestions, but none worked for me. root@7400-9888K13:/mnt/c/Users/PKammari# wget -q -O – https://packages.cloudfoundry.org/debian/cli.cloudfoundry.org.key | sudo apt-key add – gpg: can’t connect to the agent: IPC connect call failed What did I do to resolve the issue? remove gpg install … Read more
I want to add a key to associate my computer with my account and I am given two options You will need at least the SSH one, if you want to push back to your repository, using an SSH URL (since the public SSH key will authenticate you). Start with SSH. See “Connecting to GitHub … Read more