On 25 Jan 2016, at 14:50, Antoine Michard wrote:
> Thx Again Andrew. You are an incredible source of GPG knowledge
I'm really not. Just trying to be helpful. Don't trust me any more than any
other random person on the Internet. I'm quite likely to make a mistake or
leave out something importa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/25/2016 02:55 PM, Andrew Gallagher wrote:
> On 25/01/16 10:08, Antoine Michard wrote:
>>
>> So I thinking what is the best to do next: - Delete my useless
>> first subkey encryption from my keyring and send update to key
>> server.
>
> Once y
>> It's work well except that for https://encrypt.to, he use my first
>> encryption key and I can't decrypt it with my Smartcard.
>
> I'd report an issue to encrypt.to maintainer.
> encrypt.to also doesn't handle correctly the case when more than one key
> matches speceificed short key id, e.g. htt
On Mon 2016-01-25 05:08:31 -0500, Antoine Michard wrote:
> So I thinking what is the best to do next:
> - Delete my useless first subkey encryption from my keyring and send
> update to key server.
If you don't want people to encrypt messages to your D693C37C subkey,
you should revoke that subkey (
On 25/01/16 10:08, Antoine Michard wrote:
>
> So I thinking what is the best to do next:
> - Delete my useless first subkey encryption from my keyring and send
> update to key server.
Once you've published a subkey it stays published. Deleting a previously
published subkey only removes it from yo
On 25.01.2016 12:08, Antoine Michard wrote:
> It's work well except that for https://encrypt.to, he use my first
> encryption key and I can't decrypt it with my Smartcard.
I'd report an issue to encrypt.to maintainer.
encrypt.to also doesn't handle correctly the case when more than one key
matches
Hi all,
In July when I've created my Master Key, I didn't use --expert option
and now my master key is Cert and Sign and got 2 subkey for encryption
(+1 revoke).
pub 4096R/0882B381 créé : 2015-07-04 expire : jamais utilisation : SC
confiance : ultimevalidité : ulti
