Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices

Welcome to LinuxQuestions.org, a friendly and active Linux Community.

You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!

Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.

If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.

Having a problem logging in? Please visit this page to clear all LQ-related cookies.

Introduction to Linux - A Hands on Guide

This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.

Is there a built in PGP version on Linux systems? A person told me it is not necessary to buy PGP for Linux.

Is there an encryption program built in on Linux system?

I looked at the PGP homepage. They are selling PGP for Linux. It is called 'Command line programme'. It demands 2 processors. I don't understand it.

They charge almost 200 euros for the products. I think nearly 10 or 12 years ago I worked with PGP in Windows. So I know how it works.
I am looking for encryption programs. When I send mail, I would like to use some encryption method.

I'm highly satisfied with it; it integrates reasonably well with e.g.
KMail or Mutt, too. There was some compatibility issue with some
sub-feature of newer versions of PGP, but I think that PGP was making
odd moves there. Over all you'll be able to exchange messages with
PGP users just fine.

What exactly is your question? It appears to be "Did I create my keys?" but I'm not sure. "gpg --list-keys" shows you your public keyring with keys on it. Try "gpg --list-secret-keys" and see if it outputs anything. Any secret keys listed would surely be ones you successfully created. I'm assuming you ran "gpg --gen-key" since that's the way you generate a keypair.

pubring.gpg is your public keyring. No need to worry about protecting this one. secring.pgp is your private keyring - the one you need to protect.

Run "man gpg" and read the manpage. Lots of info there on how to use gpg. Its a long and detailed manpage, covers everything I can think of.

Thanks haertig for taking time to reply me. I am new to this PGP. I am not sure whether I correctly installed the software. I just want to know from you all whether I have properly installed the software.

I'm sure everything is fine for you. Since you can run the gpg command, that indicates the software is installed. Your keyrings look fine to. Those aren't your actual keys you see when you run gpg --list-secret-keys, but you can use the export command to actually see the keys if you want.

I'd say "sec" obviously stands for "secret", "uid" stands for "userid", and "ssb" stands ... I have no clue!

It seems the command you mentioned showed only the public key in its binary form.
Am I wrong? Please tell me.

You wouldn't want to export your SECRET key, so the --export option exports your PUBLIC key(s). The --armor option takes your binary key and "ASCII Armors" it. In other words, it replaces the binary gibberish with ONLY ASCII printable characters (e.g., letters, numbers, punctuation characters, etc.) While you still can't understand this ascii-armored export, you can read it. It is NOT binary, it is a printable ascii representation of the binary. You need this so you can email it or otherwise transport it safely. Sometimes email servers can mangle binary data.

That is one thing you do with your PUBLIC key. You export it ascii armored, then email it to your friends. These friends then add it to their PUBLIC keyring. They can then encrypt something they want to keep private using your PUBLIC key and email that to you. You, and only you, can then decrypt that private message using your SECRET key. You never give out your SECRET key to anyone, ever. You can give out your PUBLIC key to anyone you want. Even post it wide open on the Internet (that's why it's called "public"!)

Your PUBLIC key has two uses: (1) whoever has it can encrypt a message for you and only you, and (2) whoever has it can verify that something YOU "signed" with your SECRET key really came from you.

You can encrypt something using your friend's PUBLIC key, and sign it with your SECRET key at the same time. This creates a message that only your friend can read, and your friend can verify it came from you. They need to have your PUBLIC key to verify it came from you, but they only need their SECRET key to decrypt it.

When you ran --gen-key you created a KEY PAIR. Composed of one SECRET key for you and only you, and one PUBLIC key for everybody else.