On 2018-01-19 at 19:57 +1100, Simon Kissane wrote:
> However, when I try to decrypt data encrypted with the private key, I
> get a "failed to convert unprotected openpgp key: Checksum error"
Simpler check:
% gpg --export-secret-key
gpg: key 4252EB6983CE74C44F549B6F8666715904EE61F2: error receivin
On 1/22/18 12:30 PM, Kristian Fiskerstrand wrote:
> On 01/22/2018 06:31 PM, Daniele Nicolodi wrote:
>> On 1/22/18 5:31 AM, Kristian Fiskerstrand wrote:
>>> On 01/22/2018 08:33 AM, Werner Koch wrote:
That is an acceptable user-id. I would have used a dot as delimiter but
that is a persona
On 01/22/2018 06:31 PM, Daniele Nicolodi wrote:
> On 1/22/18 5:31 AM, Kristian Fiskerstrand wrote:
>> On 01/22/2018 08:33 AM, Werner Koch wrote:
>>> That is an acceptable user-id. I would have used a dot as delimiter but
>>> that is a personal taste.
>>
>> Dot is a permitted part of username in PO
On 1/22/18 5:31 AM, Kristian Fiskerstrand wrote:
> On 01/22/2018 08:33 AM, Werner Koch wrote:
>> That is an acceptable user-id. I would have used a dot as delimiter but
>> that is a personal taste.
>
> Dot is a permitted part of username in POSIX though, while : is not :)
Uh? As far as I know, t
Hello Daniel,
I'm on Ubuntu 17.10 with GnuPG 2.1.15, by the way.
Daniel Kahn Gillmor wrote on 2018-01-22 12:53
(UTC+0100)
> It may also depend on how the session itself is started. Maybe one of
> you is starting the user session in non-graphical mode (either a vt
> login, or maybe ssh?), while
On Mon 2018-01-22 11:52:21 +0100, Peter Lebbing wrote:
> It works for me out-of-the-box on Debian stretch/stable, supervised by
> systemd... if I SSH before I do any GnuPG stuff, it correctly prompts me
> in the (graphical) session that started the agent. So something must be
> different in your in
On 01/22/2018 08:33 AM, Werner Koch wrote:
> That is an acceptable user-id. I would have used a dot as delimiter but
> that is a personal taste.
Dot is a permitted part of username in POSIX though, while : is not :)
--
Kristian Fiskerstrand
Blog: https://blog.sumptu
On Mon 2018-01-22 08:43:41 +0100, Werner Koch wrote:
> Another problem with ssh is that ssh can't start gpg-agent on the the
> fly. Thus you need to make sure that gpg-agent has already been started
> when you use ssh. A way to ensure this is to run
>
> gpg -K
the systemd user service takes c
On 22/01/18 09:36, André Colomb wrote:
> Strange thing is, I could use the GPG part of gpg-agent already before
> issuing that command. Why does that behave differently?
Because GnuPG *does* pass TTY and display to the agent.
> Can something be done to the systemd user unit file so the process g
On 2018-01-22 08:43, Werner Koch wrote:
>> 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 the --su
10 matches
Mail list logo
