On Sun, 3 May 2015 21:29, m...@monaco.cx said:
> What about updating show copies? It looks like when scdaemon starts, they're
> automatically created for new keys observed on the card. Is it a security risk
We might even have an open bug report about this. IIRC, gniibe proposed
a solution.
> Or
On Sun, 3 May 2015 21:21, m...@monaco.cx said:
> I agree with a debug message. But in general I don't think a notification is
> so
> important because the selection algorithm is arbitrary anyway. E.g., why not
> strongest rather than newest?
What does "stronger" mean: 2k RSA on-card stronger th
Gotcha. Would it be possible to throw an error when --with-sig-check
is included with --import or --recv-keys? When silently ignored, it is
very easy for a user to assume that the signature checks passed.
Daniel
On Sun, May 3, 2015 at 2:02 AM, Werner Koch wrote:
> On Sun, 3 May 2015 01:02, diaf
Hi list,
I've got what seems to be a not too uncommon setup, with a primary key
used only for certifying, then separate signature, encryption and
authentication keys as subkeys. I wanted to make new ones, and have the
subkeys on a Yubikey NEO.
All was going perfectly fine, I revoked the old
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello everyone,
I am working with a friend on project to try and get lots and lots of
people on encrypted email at an event using something like a photobooth.
At the end of the experience you leave with a keypair and little gift
wrapped with your r
