From the question (solved)

--------------
GPG bug, can't get public key

I set up GPG on ubuntu using the tutorial from deepdotweb.com:

https://www.deepdotweb.com/2015/02/1...ide-pgp-linux/

However, when I run the command "sudo gpa" in the terminal the window opens but I get the following error message: "The GPGME library returned an unexpected error at keytable.c:150. The error was: unknown option."

Any way around this?
-----------------------
The above was solved through this link: http://crunchbang.org/forums/viewtopic.php?id=39712

------------------------

I run into the same problem, and I did the steps that solved the issue with the user above, except in my case, I cannot launch 'gpa' from the terminal...

I'm a noob at Linux and I've searched left and right for an answer...

When doing 'sudo' I get to type my user pwd... Once I do that, I get the followi ng message:
-----------------------------------------------------------------------------------
XXXXXXXX@magellan:~$ sudo gpa --disable-x509
[sudo] password for XXXXXXXX:
XXXXXXXX is not in the sudoers file. This incident will be reported.
XXXXXXXX@magellan:~$
-----------------------------------------------------------------------------------

I recall I've created or added XXXXXXXX(user) earlier to the sudoer files. It's possible I did a wrong operation...

Any idea?
Thank you

How did you add XXXX to sudoers? Did you edit the file maually or did you use visudo?

Try Scroll to the bottom and add XXXX as the last entry (remove any previous entries there or elsewhere).

For "locked God mode" (do anything you want w/ sudo + password input) on a single user system make your permissions:

(same as default root permissions)

Also, in more recent versions of Ubuntu you have to manually add yourself to your own group. I know this is retarded, but I didn't build it.

(The syntax is important, caps/lower case matters, as do the switches themselves. This string adds you to an existing group w/o fouling up your permissions or the permissions of the group.)

And sometimes on UB, even after editing sudoers w/ visudo, I've still had to go back and manually add myself to the sudo group.

(The group is first, then the user name.)

Run the commands / procedures in the order given above, do not skip around the order or skip trying some b/c you "already did that" or "don't need that" and then after fixing your permissions try running:

And it *should* work. If it fails report back w/ the error.

BTW, I did not follow / read your links and I have not played with gpg much in a long while and I have never played w/ the Gnu Privacy Assistant; but, what problem are you trying to resolve?

Whatever it is it's your system, do what you want. But if this is supposed to be privacy software then disabling its ability (or even worse if this switch disables the ability system wide) to interface w/ x509 and pull certificates seems like an exceptionally bad idea.

Do you even know what x509 is used for? x509

Hi Steven,

First, thank you so much for your time...

I want to encrypt files on my computer, currently using Debian 8.* Jessie, and for that I was creating a pgp key... All was good with the terminal until I downloaded the software to create/store my key... For some reasons that I have yet to comprehend, I cannot seem to get it to "work" when I launch it, because it hangs... The disabling of x509 was explained as a solution in the links I've provided in my original post...

No, I do not understand the consequences of disabling x509.

-- Going with the first part of your response for now! Thank you,

Broken link, the "..." abbreviation seems to have gotten into the address itself.

I don't see any mention of 'sudo' in that link, maybe try without sudo?

I'll tell you now that pgp is pretty good for what it does. But it is a major headache to get working correctly, even when you're experience with computers.

Are you trying to encrypt files locally? If so I'd look at veracrypt. It's what I use.

If you're looking to communicate securely I actually advise one of the many commercial solutions. Not only is it a major PITA to get pgp right on your end, but most of the time you end up having to help the other person get it set up on their end.

There are services / products that will make pgp set up pretty painless on both ends. (Google is your friend.)

Personally I feel it's worth ~$60(US) a year to have someone do it all for me. But, then again, I'm not guarding any state secrets if they didn't do it right or left a back door for the NSA.

Plus, end to end encrypted chat is point and click now days. Back in the day, if I had to send somebody something private, I'd just use an encrypted self extracting cab file as an attachment and give them the password over the phone.

There are lots of ways to skin this cat that are not as much a PITA as pgp.