Hello everyone,
I've recently encountered the problem explained in item #3 here:
https://www.gnupg.org/documentation/manuals/gnupg/Common-Problems.html
and I would like to discuss it.
I use the `systemd` user service provided with Arch Linux and it's
`ExecStart` is:
/usr/bin/gpg-agent --
Simon Kissane wrote:
> (This is just a test key generated for testing purposes, so it is fine
> to share it publicly.)
Interesting "User ID" on that key:
"root:testGpg:key_54503F79_3794_456C_8725_8977A68B71C1"
I hope no one is foolish enough to import your key and run your script.
__
On Mon, Jan 22, 2018 at 11:36 AM, Zechariah Seth
wrote:
> Simon Kissane wrote:
>> (This is just a test key generated for testing purposes, so it is fine
>> to share it publicly.)
>
> Interesting "User ID" on that key:
> "root:testGpg:key_54503F79_3794_456C_8725_8977A68B71C1"
>
> I hope no one is f
On Mon, 22 Jan 2018 03:40, skiss...@medallia.com said:
> showing that problem (whatever it is) isn't the User ID. (My reading of
> RFC4880
> section 5.11 is that having an email in the User ID is just a convention not
> mandatory, so software should be robust in the face of User IDs breaking that
On Sun, 21 Jan 2018 17:41, doron.be...@gmail.com said:
> As far as I understand, because I use `systemd`'s user service, whenever
> I want to unlock an authentication key I need to run the command
> `gpg-connect-agent updatestartuptty /bye`.
Although I have no experience with the peculiarities of
