Gpg Gen-key Versus Full Generate
This tutorial series will teach you how to use GPG in Linux terminal. I will not tell you a bunch of theory to overwhelm you. Instead, I show you quick and dirty examples to get you started, and explain the basic theory along the way.
This is part 1 of this series. At the end of this post, you should be able to generate your own public/private keypair and a revocation certificate. This certificate is used to revoke your public/private keypair when your private key is compromised or you forget the passphrase for your private key.
GPG can be used for encryption and for signing. This software is pre-installed on most Linux distributions. Currently the stable version is GPG 2.0. I’m using the modern version GPG 2.2 on Arch Linux.
Check Your GPG Version
First Let’s check out the version of GPG on your system and some interesting tidbits. Run the following command.
Entity framework guid primary key auto generated. At first, you need to generate a key locally. You can decide, which key attributes to use and - most importantly - you can export the key and keep it somewhere save in case you need to restore the key. Main Key and Encryption Subkey. We can use the command gpg -full-generate-key -expert to start a guided key generation with all possible. Yes, pinentry is installed. I've done some more digging into this: It works from the local console (without gpg-agent being set up at all). However it does NOT work by doing a su - then gpg2 -gen-key. Apr 17, 2015 Re: gpg -gen-key always exits Post by AliceWonder » Fri Apr 17, 2015 5:20 pm Yup - effing dumb software design, a command-line tool that wants to launch a damn X window as part of its process even when it doesn't have permission to. Oct 03, 2019 gpg -full-generate-key The above command will do the same thing as the first, only it will also allow you to configure the following for the keypair: Select what kind of key you want.
As you can see, I’m using GPG 2.2.8, which is the latest version. We also know that the configuration directory is ~/.gnupg, which will hold our public/private key files. The default option file is ~/.gnupg/gpg.conf and ~/.gnupg/dirmngr.conf. It also tells us what algorithms are supported.
If you look closely, you can see that the insecure hash algorithm SHA1 is still supported in version 2.2.8 SHA1 is obsolete and you don’t want to use it to generate signature.
Create Your Public/Private Key Pair and Revocation Certificate
Use gpg --full-gen-key
command to generate your key pair.
It asks you what kind of key you want. Notice there’re four options. The default is to create a RSA public/private key pair and also a RSA signing key. Let’s hit Enter to select the default.
Next it asks you the key length. The default is 2048 bits long. 1024 RSA key is obsolete. The longer 4096 RSA key will not provide more security than 2048 RSA key. So hit Enter to select the default.
After that it asks you how long the key should be valid, 2 years is fine. You can always update the expiration time later on.
Generate Gpg Key Windows
Now it asks you if it’s correct. Notice that the default is No. So press y
then Enter to confirm it’s correct.
And now we need to provide some user identification information for the key. This is important because this information will be included in our key. It’s one way of indicating who is owner of this key. The email address is a unique identifier for a person. You can leave Comment blank.
Select Okay.
Now it asks you to enter a passphrase to protect your private key. Enter a good and long passphrase and remember it. Because if you forget this passphrase, you won’t be able to unlock you private key.
Once you enter and confirm your passphrase. GPG will generate your keys.
It will take a while for GPG to generate your keys. So you can now do other stuff.
It took about 4 minutes on my system to generate my key pair.
This first line tells us that GPG created a unique identifier for public key. This unique identifier is in hex format. When someone wants to download you public key, they can refer to you public key via your email address or this hex value.
The third line tells us that GPG created a revocation certificate and its directory.Your should never share you private key with anyone.If you private key is compromised, you can use revocateion certificate to revoke your key. That means you tell the rest of the world that the old public key shall not be used any more.I suggest that you open this revocation certificate with your text editor to see what’s inside there.
Let’s look at the last three lines. They tell us the public key is 2048 bits using RSA algorithm. The public key ID 4F0BDACC matchs the last 8 bits of key fingerprint. The key fingerprint is a hash of your public key.
It also lists our user ID information: your name and your email address. And it also indicates the subkey which is 2048 bits using RSA algorithm and the unique identifier of the subkey.
Now you can find that there are two files created under ~/.gnupg/private-keys-v1.d/ directory. These two files are binary files with .key extension.
Export Your Public Key
Others need your public key to send encrypted message to you and only your private key can decrypt it. Use the following command to export your public key. --armor
option means that the output is ASCII armored. The default is to create the binary OpenPGP format. user-id
is your email address.
The exported public key is written to pubkey.asc
file.
Export Your Private Key
Issue the following command to export your private key.
The exported key is written to privkey.asc
file.
Gpg Gen-key Versus Full Generate Online
Protect Your Private Key and Revocation Certificate
Your private key should be kept in a safe place, like an encrypted flash drive. Treat it like your house key. Only you can have it and don’t lose it. And you must remember your passphrase, otherwise you can’t unlock your private key.
You should also protect your revocation certificate. If others have your revocation certificate, they can immediately revoke your public/private keypair and generate a fake public/priavte keypair.
In part 2 we will look at how to encrypt message with your public key and how to decrypt it with your private key. Take care!
Key-Type: 1 |
Key-Length: 2048 |
Subkey-Type: 1 |
Subkey-Length: 2048 |
Name-Real: Root Superuser |
Name-Email: root@handbook.westarete.com |
Expire-Date: 0 |
# Generate the key |
gpg --batch --gen-key gen-key-script |
commented Feb 13, 2014
Here's a page that describes the options for the gen-key script: http://www.gnupg.org/documentation/manuals/gnupg-devel/Unattended-GPG-key-generation.html Creating your SSH key pair; Adding your SSH public key to GitLab. Create and add your SSH key pair. It is best practice to use Git over SSH instead of Git over HTTP. In order to use SSH, you will need to: Create an SSH key pair; Add your SSH public key to GitLab. Creating your SSH key pair. Apr 17, 2016 Use SSH with GitLab (Mac) 1. SSH keys (use existing one or generate one). Generate ssh key mac for gitlab. |
commented Feb 13, 2014
Originally I had a couple extra steps to use rng-tools to seed entropy from /dev/urandom. Apparently this is a bad idea because it will just feed bytes regardless of whether there's enough entropy. Here's where I got the original idea, and the subsequent discussion of why it's bad. For new machines, we should generate the keys on our laptops where there's much more entropy to draw from, and then transfer them to the new server, just like we're currently doing with the encrypted data bag secret. |
commented Feb 19, 2018
This is awesome, thank you. |
commented Jan 23, 2019
I configured libvirt tu use /dev/urandom of the host: https://libvirt.org/formatdomain.html#elementsRng |
commented Apr 9, 2019 • edited
edited
Thanks that was really helpful |