Hello,
Since I got 2.1 card last week, I will test with it. For time being,
I say something what I know of.
Fib Moro wrote:
> I can then successfully change the PIN as well as AdminPIN.
>
> However, when I try to write a key to the card (gpg --edit-key xxx;
> keytocard) I
> get a message "Erro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Kahn Gillmor wrote:
>
> You don't get the luxury to decide on this transition yourself,
> i'm afraid. Mailpile has to deal with *other* MUAs doing
> throw-keyids, just like those other MUAs have to deal with it
> if/when Mailpile starts doing
On Mon 2017-02-13 18:35:17 -0500, Bjarni Runar Einarsson wrote:
> Sounds like a nice optimization... but option bloat is a thing too.
for an API, there's nothing wrong with explicitly specifying the thing
that people should *want* to be doing as a separate interface.
GnuPG has some level of diffi
On Mon 2017-02-13 11:54:04 -0500, Lukas Pitschl | GPGTools wrote:
>> Am 13.02.2017 um 17:34 schrieb Daniel Kahn Gillmor :
>>
>> On Mon 2017-02-13 06:41:51 -0500, Bjarni Runar Einarsson wrote:
>>> Step two: Encrypt using gpg --throw-keyids.
>>>
>>> This is easy on the sender's end, but whether thi
Dear GnuPG-Users List.
I'm having trouble with resetting my smartcard version 2.1.
After posting a bug report for GnuPG Werner Koch asked me to re-post my
question on this mailing list [0].
To answer his quick hint: factory-reset did unfortunately not work as I already
mentioned in my original
> Am 13.02.2017 um 17:34 schrieb Daniel Kahn Gillmor :
>
> On Mon 2017-02-13 06:41:51 -0500, Bjarni Runar Einarsson wrote:
>> Step two: Encrypt using gpg --throw-keyids.
>>
>> This is easy on the sender's end, but whether this feature can be
>> used as a matter of course depends on how it impact
On Mon 2017-02-13 06:41:51 -0500, Bjarni Runar Einarsson wrote:
> Step two: Encrypt using gpg --throw-keyids.
>
> This is easy on the sender's end, but whether this feature can be
> used as a matter of course depends on how it impacts the
> experience of the recipient.
Agreed that the recipient's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi folks,
Context: I am trying to figure out how much visible metadata I
can remove from an encrypted e-mail before it becomes completely
unusable.
Step one: stripping stuff from the message headers is relatively
easy; minimal messages with all recip
On 12/02/17 13:32, Marko Bauhardt wrote:
> Hi,
> The amor definition of my public key i uploaded
> to hkps://hkps.pool.sks-keyservers.net differs to the public key
> definition i uploaded to another web service.
An OpenPGP public key is composed of many parts which can be reordered
without changin
Hi :)
Jean-François Schaff writes:
> I'm new to gpg, and trying to use the Python bindings included in
> PGPME. I'm using Ubuntu 16.04 LTS.
>
> I have done the following things:
...
> - compiled and installed gpgme-1.8.0
>
> Everything seems to build and install as expected, but when I finally
>
On Feb 10, 2017 at 1610 +, Andrew Gallagher appeared and said:
> On 10/02/17 12:57, René Pfeiffer wrote:
> > Hello!
> >
> > I am using gpg and gpg2 with mutt and Icedove/Thunderbird (with Enigmail
> > plugin). My public keyring has grown to be very big since the email clients
> > auto-import u
11 matches
Mail list logo
