Hi all,
thank you Damien and Werner for your recent replies.
Even if the reader is performing o.k. now to my amassment.
When I used the feature to create the keys on the card I ran to some
strange and not reproducible problems.
I think this is what Werner refers to. Once I decided to create the
On Fri, 6 Jan 2017 14:52, dgouttegat...@incenp.org said:
> For what is worth, I have two such readers, which are working
> flawlessly with the ccid driver [1] and with 2048-bit keys. I have not
> tried them with the internal driver.
IIRC, I added some workarounds but eventually gave up due to
On 01/06/2017 10:06 AM, gnupg-users.d...@o.banes.ch wrote:
I was under the impression the OmniKey 3121 is a real reader since it is
on the how to [1].
For what is worth, I have two such readers, which are working flawlessly
with the ccid driver [1] and with 2048-bit keys. I have not tried
Hi Andrew,
thanks for you input. And I will gave it a try.
1) deactivated my script
2) added udev rule ACTION=="add", SUBSYSTEM=="usb",
ATTR{idVendor}=="076b", ATTR{idProduct}=="3022", RUN+="/usr/sbin/service
pcscd restart"
3) testdrive - reader unplug - plug in (USB)
Jan 06 13:55:00 compd
Hi Kristian,
it is not the reader (USB Device) which is removed. It is the Card in
the reader.
I would not know how to monitor this with udev. Is this possible ?
Best regards
Dirk
On 06.01.2017 10:30, Kristian Fiskerstrand wrote:
On 01/06/2017 10:06 AM, gnupg-users.d...@o.banes.ch wrote:
>
On 06/01/17 09:30, Kristian Fiskerstrand wrote:
> On 01/06/2017 10:06 AM, gnupg-users.d...@o.banes.ch wrote:
>> p.s. in the meantime a made a script which tails the scdaemon.log and
>> waits for "Removal of a card:"
>> and then kills the gpg-agent. Not a proper solution - but working so far.
>
>
On 01/06/2017 10:06 AM, gnupg-users.d...@o.banes.ch wrote:
> p.s. in the meantime a made a script which tails the scdaemon.log and
> waits for "Removal of a card:"
> and then kills the gpg-agent. Not a proper solution - but working so far.
Why not use udev rule to watch for removal event?
--
Hi Werner,
thanks for your reply.
I was under the impression the OmniKey 3121 is a real reader since it is
on the how to [1].
What would be a good alternative bevore I buy another bad one.
And I have problems understanding how the issue is connected to the key
length.
The Problem as I see it
On Wed, 4 Jan 2017 21:14, gnupg-users.d...@o.banes.ch said:
> thanks for you reply but it is now not working at all. Even if my reader
> - Ominkey 3121 is listed in you link.
Omnikey readers simply don't work correctly with 2k keys or larger. Get
a real reader and not that messy hardware which
Hi Peter,
thanks for you reply but it is now not working at all. Even if my reader
- Ominkey 3121 is listed in you link.
o.k. I removed pcscd and changed the scdaemon.conf to this:
card-timeout 5
#disable-ccid
debug-level basic
log-file /home/dirk/scdaemon.log
debug-ccid-driver
scdaemon Log
I think you should be able to use this card reader without pcscd, using the
internal CCID driver of GnuPG[1]. Just stop and disable pcscd, hopefully GnuPG
will find the reader and use it right away. That might solve your problem. I use
GnuPG's internal CCID driver, and it is completely resilient
Hello all,
I recently changed to the GnuPG Smartcard which in general works fine
for eMail and for SSH authentication (on Ubuntu 16.10).
The only problem I encountered was that when I pull the card from the
reader and reinsert it the gpg-agent will not recover.
I have to kill him gpgconf --kill
12 matches
Mail list logo
