Is there an easy way to make Git always signs each commit or tag that is created?

I tried it with something like:
&lt;pre&gt;alias commit = commit -S&lt;/pre&gt;
But that didn&#39;t do the trick.

I don&#39;t want to install a different program to make this happen. Is it doable with ease?

Just a side question, maybe commits shouldn&#39;t be signed, only tags, which I never create, as I submit single commits for a project like Homebrew, etc.


Is there a way to &quot;autosign&quot; commits in Git with a GPG key?

I just started using git and I install git and gpg via homebrew.
For some reason, I get this error when i do `git commit`
I looked at so many other stackoverflow questions regarding this topic and none of them worked for me.
How can I fix this error so that I can upload successfully. 

    error: gpg failed to sign the data
    fatal: failed to write commit object


Git error - gpg failed to sign data

I have a copy of the postgresql apt repository gpg key and would like to view the details of the gpg key as it comes in the file. Is this possible without importing it into a key ring?

How to display gpg key details without importing it?

I have a new mac pro (OS X 10.9.5) that I get to set up from scratch. I want to install RVM and the first thing it says to do is: 

&gt; Install mpapis public key (might need `gpg2` and or `sudo`)
&gt;
&gt;     gpg --keyserver hkp://keys.gnupg.net --recv-keys D39DC0E3

When I tried I got:

    gpg --keyserver hkp://keys.gnupg.net --recv-keys D39DC0E3
    zsh: command not found: gpg

I&#39;ve tried to find a good guide on how to overcome this that also looks trustworthy but I&#39;ve had no luck.

Can someone explain what `gpg` is, why I dont already have it, and how do I get it the right way.

How to resolve &quot;gpg: command not found&quot; error during RVM installation?

I&#39;m trying to use interesting password management [tool][1] named Pass.

I did the following:

 1. Installed gpg tool `$ sudo dnf install gpg`
 2. Generated a key using `$ gpg --gen-key` 
 3. Typed `$ pass init &quot;foobar id of my gpg key&quot;` as stated [here][1]
 4. Got
 
`mkdir: created directory ‘/home/chichivica/.password-store/’
 Password store initialized for foobar@email.com`

 5. Tried to add a simple password 

`$ pass insert foo
Enter password for foo: 
Retype password for foo:`

 6. And there is the problem

`gpg: A45A123C: There is no assurance this key belongs to the named user
gpg: [stdin]: encryption failed: Unusable public key`


Could anyone give me some advice?

  [1]: http://www.passwordstore.org/

gnupg: There is no assurance this key belongs to the named user

Is it possible to encrypt data, such that it can be decrypted with several different keys?

Example:

&gt;I&#39;ve encrypted data with key1, but I want to be able to decrypt with keys 2, 3, and 4.

Is this possible?

encryption/decryption with multiple keys

I am trying to automate backups with `duplicity`, but when I test the result, I get 

&gt; gpg: public key decryption failed: bad passphrase

I want to check whether the passphrase I am using is actually the passphrase associated with the corresponding gpg secret-key, but I can&#39;t see anyway in the gpg command-line options to say &quot;Don&#39;t encrypt or decrypt anything. Just confirm I am using the right passphrase.&quot;

This suggests that maybe I am (yet again) misunderstanding Gnu Privacy Guard. *(It has a predilection for taunting me until I cry.)*

Does it make sense to ask gpg to verify a passphrase? If so, how?

How to use gpg command-line to check passphrase is correct

On GitHub, I want to add a key to associate my computer with my account and I am given two options: create an SSH or a GPG key. 

What is the difference between the two keys? and is there a preferred one to use?  
I understand how to create both by following the guide on the site but I don&#39;t know which one is better to use.

GPG vs SSH keys

I started using gnupg. An error occurs when trying to import a key from any server:

    @ubuntu:~/Desktop$ gpg --keyserver keys.gnupg.net --recv-key 908F435E
    gpg: keyserver receive failed: No name



gpg: keyserver receive failed: No name

Background: My boss has tried exporting an ASC key to me with public and private parts but whenever I get the file the private part never loads up and it won&#39;t decrypt any files.

We have tried Exporting the ASC Key using: 

- Windows Application Kleopatra 2.1 (included in gpg4win)
- Windows Application GNU Privacy Assistant (included in gpg4win) 


                Error: &quot;Decryption failed. Secret Key Not available.&quot; 

How do you properly export a secret or private asc key to decrypt gpg files? 

How to Export Private / Secret ASC Key to Decrypt GPG Files

I try to decrypt file using following command:

    gpg --output file.txt --decrypt file.pgp

File is decrypted successfully but i get an error:

&gt; &quot;gpg: Can&#39;t check signature: public key not found&quot;

Any idea, why I get this error?

Can&#39;t check signature: public key not found

I am running next command within a crontab to encrypt a file and I don&#39;t want a keyboard interaction

    echo &quot;PASSPHRASE&quot; | gpg --passphrase-fd 0 -r USER --encrypt FILENAME.TXT

but I have this answer:

    gpg: C042XXXX: There is no assurance this key belongs to the named user
    
    pub  40XXX/C042XXXX 2012-01-11 Name LastName. (comment) &lt;user@email.com&gt;
     Primary key fingerprint: XXXX XXXX XXXX XXXX XXXX  XXXX XXXX XXXX XXXX XXXX
          Subkey fingerprint: XXXX XXXX XXXX XXXX XXXX  XXXX XXXX XXXX XXXX XXXX
    
    It is NOT certain that the key belongs to the person named
    in the user ID.  If you *really* know what you are doing,
    you may answer the next question with yes.
    
    Use this key anyway? (y/N) 

gpg encrypt file without keyboard interaction

Trying to update some repositories on Debian Etch installation and getting the following errors from running &quot;apt-get update&quot;

    W: GPG error: http://www.debian-multimedia.org etch Release: The following signatures couldn&#39;t be verified because teh public key is not available: NO_PUBKEY 07DC563D1F41B907
    W: You may want to run apt-get update to correct these problems

The irony of it instructing me to run apt-get update is a nice kicker...

How to trust a apt repository : Debian apt-get update error public key is not available: NO_PUBKEY &lt;id&gt;

I installed GPG from brew.

    brew install gpg

It is gnupg2-2.0.30_2.

When I commit, I do get a error message:

    You need a passphrase to unlock the secret key for
    user: &quot;Max Mustermann (mycomment) &lt;mm@test.de&gt;&quot;
    2048-bit RSA key, ID 1111AAAA, created 2017-01-05 
    
    error: gpg failed to sign the data
    fatal: failed to write commit object

I used the command:

    gpg --list-secret-keys | grep ^sec

and it gives me back:

    sec   2048R/1111AAAA 2017-01-05

Then I used this command:

    git config --global user.signingkey 1111AAAA

commit gives me back the same error message.

How can I solve this problem?


git - gpg onto mac osx: error: gpg failed to sign the data

I am having a problem while trying to decrypt some keys using GPG. The following output is given to me:

    gpg: can&#39;t connect to the agent: IPC connect call failed

I already edited some files, pointed in this tutorial: https://michaelheap.com/gpg-cant-connect-to-the-agent-ipc-connect-call-failed/ but with no success.

Possible reasons for that?

Thanks in advance

gpg: can&#39;t connect to the agent: IPC connect call failed

I&#39;m automating my Docker installation. Something like this:

    if apt-key fingerprint 0EBFCD88 | grep &quot;Key fingerprint = 9DC8 5822 9FC7 DD38 854A E2D8 8D81 803C 0EBF CD88&quot; &gt; /dev/null
    then
      # proceed
    fi

This worked fine in older versions of `apt-key`, but recent versions have two issues:

1. A different output format: I can hack around that
2. A warning:

        Warning: apt-key output should not be parsed (stdout is not a terminal)

Clearly, I can hack around this as well, just redirect `stderr` to `/dev/null`. It just made me curious:

**How do these fine folks suggest I verify my key fingerprints?** Or am I getting this fundamentally wrong by wanting to automate it, does that defeat the point? (I think not, since I still manually lifted the expected fingerprint from the website, but feel free to tell me otherwise...)

How to circumvent &quot;apt-key output should not be parsed&quot;?

Setup : Ubuntu Server on Virtual Machine with 6 cores and 3GB of RAM.

when I am trying to generate a `asymmetric key pair` via `GPG` like this `gpg --gen-key` . I get the following error :

    Not enough random bytes available.  Please do some other work to give
    the OS a chance to collect more entropy!
I tried to google a little bit. This is what I realise , 
I need to fire up another terminal and type in `cat /udev/random` --&gt; It randomly generates a series of randomly generated values to increase the entropy. 

I dont see any change in here `watch cat /proc/sys/kernel/random/entropy_avail`

and it still persists to give me the same error


PGP: Not enough random bytes available. Please do some other work to give the OS a chance to collect more entropy

I am using:

     gpg --gen-key

Is there a better way to create a PGP key? What does this program want? A fully slammed server?

&gt; Not enough random bytes available.  Please do some other work to give the OS a chance to collect more

GPG error &quot;Not enough random bytes available. Please do some other work to give the OS a chance to collect more&quot;

Given the option between using GPG and OpenSSL for local encryption before pushing archives to an off-site backup location, what are the benefits and drawbacks of each solution?

Background:
I currently manage a server infrastructure based on Ubuntu 14.04.1 with all current patches applied as they become available.

All of these systems are headless, automatically built using vetted preseeds and automation tools, and run in virtual machines via KVM on uniform Intel-based hardware.

We have a preference for Ruby, but a stronger preference for &quot;doing things correctly&quot;. Because of both, we&#39;ve chosen the &quot;backup&quot; gem as the means to create encrypted archives of data we want preserved, since it will create the same encrypted archives for a developer using Vagrant that it would in production, regardless of the mechanism by which it&#39;s transmitted. 

All software and configuration is managed via Puppet, so neither decision will have any impact on &quot;user experience&quot; or convenience. Either option will create relevant scripts to manage, verify, or restore from any backups created. 

Given that, does either encryption option offer any advantage against the other when used for this purpose?

OpenSSL vs GPG for encrypting off-site backups?

I&#39;m using [Travis-CI][1] to provide continuous integration builds for a few Java open source projects I&#39;m working on.

Normally this works smoothly, but I have a problem when the POM specifies GPG signing, e.g. 

    &lt;plugin&gt;
      &lt;groupId&gt;org.apache.maven.plugins&lt;/groupId&gt;
      &lt;artifactId&gt;maven-gpg-plugin&lt;/artifactId&gt;
      &lt;version&gt;1.4&lt;/version&gt;
      &lt;executions&gt;
        &lt;execution&gt;
          &lt;id&gt;sign-artifacts&lt;/id&gt;
          &lt;phase&gt;verify&lt;/phase&gt;
          &lt;goals&gt;
            &lt;goal&gt;sign&lt;/goal&gt;
          &lt;/goals&gt;
        &lt;/execution&gt;
      &lt;/executions&gt;
    &lt;/plugin&gt;

This causes the Travis build to fail - apparently because it does not have a passphrase available while running `mvn install`. See [this build][2] for an example.

What is the best way to configure Maven and/or Travis to skip GPG signing for CI test builds, but still perform GPG signing when I do a proper release build?


  [1]: https://travis-ci.org/
  [2]: https://travis-ci.org/nuroko/nurokore/jobs/4683227

Suppressing GPG signing for Maven-based continuous integration builds (Travis CI)

I am trying to push my staging repository  on `oss.sonatype.org` to central repository, but this action is getting failed and i am getting following exception

    Event: Failed: Signature Validation
    typeId	signature-staging
    failureMessage	No public key: Key with id: (XXXXX) was not able to be located on http://keyserver.ubuntu.com:11371. Upload your public key and try the operation again.

I used `gbp` to generate public and well private key for me and i even sent public key to the server with following command

    gpg --keyserver hkp://pool.sks-keyservers.net --send-keys EE539F98

Still i am getting same exception.I cross checked and there is only one `Sub Key`, not sure what else i need to do to push public key so as this can be found by nexus 



No public key: Key with id: (XXXXX) was not able to be located (oss.sonatype.org)

If I have the same filename in the target directory, decryption fails.

The command I&#39;m using to decrypt:

    gpg --passphrase-fd 0 -o D:/Notification/mytest.txt --batch \
      --passphrase-file D:/passphrase.txt -d D:/Notification/mytest.gpg

It doesn&#39;t overwrite the *mytest.txt* file so each time I need to delete the file before I execute the script.

Is there any option to overwrite the output fie?

How to automatically overwrite the output file when running `gpg` (i.e. without being prompted)?

Would it be possible for the GPG password to be saved, so that I am not prompted for the passphrase everytime I make a git commit?

Remember GPG password when signing git commits

I have a gpg .key file that is used as passphrase for decrypting a .dat.pgp file. The encrypted .data.pgp file gets successfully decrypted on one server with same .key file using following command

    cat xxx_gpg.key | /usr/bin/gpg --batch --quiet -o xxx.dat --passphrase-fd O -d xxx.dat.pgp

But, when I move same key to another server xxx_gpg.key and run same above command, I get following error - 

    gpg: decryption failed: No secret key


EDIT: 

I find that `gpg --list-secret-keys` returns some data on server where it works but no results are returned for other server.

How can we configure secret key


gpg decryption fails with no secret key error

The encryption tool of gnuPG package gpg prompts for passphrase using a GUI dialog box when invoked by a regular user, however when invoked by root it prompts on CLI. How to make it use the CLI even when invoked by a regular user.
 version:GnuPG 1.4.12 

How to make gpg prompt for passphrase on CLI

Are the exported private keys gotten by executing `gpg --export-secret-keys` still encrypted and protected by their passphrase? This seems to be the case but I can&#39;t find anywhere that explicitly confirms this.

If the exported keys are still encrypted then is there anyway to get the pure, unencrypted private key (like you can for the public segment)?

All Gnupg Solutions on Gang of Coders

Total of 26 Gnupg Solutions

Is there a way to "autosign" commits in Git with a GPG key?