On Thu 2017-02-16 11:37:55 -0500, Werner Koch wrote:
> On Wed, 15 Feb 2017 20:52, d...@fifthhorseman.net said:
>
>> However, this will cause problems for people dealing with a smartcard
>> with a PGPv3 key on it.
>
> I doubt that you can put a PGP-2 key on an OpenPGP smartcard. We
> require a
On Wed, 15 Feb 2017 20:52, d...@fifthhorseman.net said:
> However, this will cause problems for people dealing with a smartcard
> with a PGPv3 key on it.
I doubt that you can put a PGP-2 key on an OpenPGP smartcard. We
require a SHA-1 fingerprint.
> hm, bummer. a configure option to keep the
On Wed 2017-02-15 13:33:57 -0500, Werner Koch wrote:
> On Wed, 15 Feb 2017 16:23, d...@fifthhorseman.net said:
>
>> should we adjust the build of 1.4 in debian to patch out the direct
>> access of smartcards? if we use --disable-card-support during
>> ./configure will that disable use of the
On Wed, 15 Feb 2017 16:23, d...@fifthhorseman.net said:
> should we adjust the build of 1.4 in debian to patch out the direct
> access of smartcards? if we use --disable-card-support during
> ./configure will that disable use of the agent for smartcards as well,
> or will it just remove the
On Wed 2017-02-15 05:24:34 -0500, Werner Koch wrote:
> On Tue, 14 Feb 2017 00:55, d...@fifthhorseman.net said:
>
>> * gpg 1.4 expects to connect directly to the active smartcard. 2.1
>>expects access to the smartcard to be mediated by the scdaemon
>>process. I don't know what happens if
On Tue, 14 Feb 2017 00:55, d...@fifthhorseman.net said:
> * gpg 1.4 expects to connect directly to the active smartcard. 2.1
>expects access to the smartcard to be mediated by the scdaemon
>process. I don't know what happens if both of these systems try to
>access a single
6 matches
Mail list logo
