On 23/10/14 12:00, Werner Koch wrote:
> BTW, is it still not possible to enable the access using the device
> class?
I've had a good look at this. On Debian stable, I couldn't get it to
work, but maybe it's possible.
The SCM SPR532 seems an unlikely candidate; it's not of the correct
device class
On Wed, 22 Oct 2014 11:19, pe...@digitalbrains.com said:
> necessary udev rules are included in the gnupg package already. However, I use
> an SPR532 here. The SCM3512 is not mentioned in the rules file, so you might
> need to add an entry.
BTW, is it still not possible to enable the access using
Peter, I've had time to read and try to get to grips with the contents of your
email. They've helped me make some progress :
On 22/10/14 11:19, Peter Lebbing wrote:
> On 21/10/14 00:36, Philip Jackson wrote:
>> I've followed, I believe, all the instructions in the gnupg.com smartcard
>> howto.
>
On 22/10/14 09:34, Jens Lechtenboerger wrote:
> On 2014-10-21, Philip Jackson wrote:
>
> Did you really verify that pcscd is not running? It can cause your
> error messages: https://blogs.fsfe.org/jens.lechtenboerger/?p=89
>
Your blog provides a lot of good stuff that I shall use when I get rou
Thank you for all this, Peter. It will take me a little while to digest and
check out.
Philip
On 22/10/14 11:19, Peter Lebbing wrote:
> On 21/10/14 00:36, Philip Jackson wrote:
>> I've followed, I believe, all the instructions in the gnupg.com smartcard
>> howto.
>> In para 2.3.1 CCID : I've t
On 22/10/14 09:34, Jens Lechtenboerger wrote:
> On 2014-10-21, Philip Jackson wrote:
>
>> It then treats the other protocol, PC/SC, but all it says is "TODO
>> - To use PC/SC make sure you disable CCID by passing the
>> --disable-ccid option to GnuPG."
>>
>> From this I assumed that CCID was perha
On 21/10/14 00:36, Philip Jackson wrote:
> I've followed, I believe, all the instructions in the gnupg.com smartcard
> howto.
> In para 2.3.1 CCID : I've tried both the instructions under 'with udev
> (preferred installation)' and further down 'with hotplug (deprecated in modern
> systems)'
Thes
On 2014-10-21, Philip Jackson wrote:
> It then treats the other protocol, PC/SC, but all it says is "TODO
> - To use PC/SC make sure you disable CCID by passing the
> --disable-ccid option to GnuPG."
>
> From this I assumed that CCID was perhaps either preferred / more
> important / more useful /
On 21/10/14 15:33, Tristan Santore wrote:
> On 21/10/14 14:10, Philip Jackson wrote:
>> On 21/10/14 12:59, Tristan Santore wrote:
>>> On 20/10/14 23:36, Philip Jackson wrote:
>> snip
>>
going under my UbuntuStudio 1404 linux. Using gnupg2 2.0.26.
Trying to use the GnuPG d
On 21/10/14 14:10, Philip Jackson wrote:
> On 21/10/14 12:59, Tristan Santore wrote:
>> On 20/10/14 23:36, Philip Jackson wrote:
> snip
>
>>> going under my UbuntuStudio 1404 linux. Using gnupg2 2.0.26.
>>>
>>> Trying to use the GnuPG driver to access CCID cards, "gpg2 --card-status"
>
On 21/10/14 14:58, Pete Stephenson wrote:
> On Tue, Oct 21, 2014 at 2:50 PM, Philip Jackson
> wrote:
>> On 21/10/14 09:25, Pete Stephenson wrote:
>>> What is the result of running the command:
>>>
>>> echo $GPG_AGENT_INFO
>>
>> echo $GPG_AGENT_INFO
>> /tmp/gpg-9S6s3F/S.gpg-agent:1611:1
>
> Intere
On 21/10/14 12:59, Tristan Santore wrote:
> On 20/10/14 23:36, Philip Jackson wrote:
snip
>> going under my UbuntuStudio 1404 linux. Using gnupg2 2.0.26.
>>
>> Trying to use the GnuPG driver to access CCID cards, "gpg2 --card-status"
>> yields
>> the following output :
>>
>> gpg: sel
On Tue, Oct 21, 2014 at 2:50 PM, Philip Jackson
wrote:
> On 21/10/14 09:25, Pete Stephenson wrote:
>> What is the result of running the command:
>>
>> echo $GPG_AGENT_INFO
>
> echo $GPG_AGENT_INFO
> /tmp/gpg-9S6s3F/S.gpg-agent:1611:1
Interesting, thanks.
In the past when I've had issues similar
On 21/10/14 09:25, Pete Stephenson wrote:
> On Tue, Oct 21, 2014 at 12:36 AM, Philip Jackson
> wrote:
> [snip]
>> This looks promising but I didn't take it any further because I want to get
>> it
>> going under my UbuntuStudio 1404 linux. Using gnupg2 2.0.26.
>>
>> Trying to use the GnuPG driver
gpg: selecting openpgp failed: Card error
gpg: OpenPGP card not available: Card error
I've followed, I believe, all the instructions in the gnupg.com smartcard howto.
Philip,
Further, to the previous question, which distribution are you
currently using ? There is a locking issue in Fedora
On 20/10/14 23:36, Philip Jackson wrote:
> After a couple of weeks away from the smartcard issue, I've tried again from
> scratch. Under Windows7 using GpG4win 2.2.2 with an SCM3512 reader, SCM's
> drivers and G10's openpgp v2 card, gpg --card-status provides the following
> output :
>
> Applicat
On Tue, Oct 21, 2014 at 12:36 AM, Philip Jackson
wrote:
[snip]
> This looks promising but I didn't take it any further because I want to get it
> going under my UbuntuStudio 1404 linux. Using gnupg2 2.0.26.
>
> Trying to use the GnuPG driver to access CCID cards, "gpg2 --card-status"
> yields
> t
After a couple of weeks away from the smartcard issue, I've tried again from
scratch. Under Windows7 using GpG4win 2.2.2 with an SCM3512 reader, SCM's
drivers and G10's openpgp v2 card, gpg --card-status provides the following
output :
Application ID ...: D2760001240102052870
Version
18 matches
Mail list logo
