Hi,
Am 03.06.2012 17:45, schrieb Robin Kipp:
> However, as I'd much rather use 2048-bit keys, I guess I'll just have
> to sort things out with the retailer I got it from... Can you
> recommend another brand that produces readers which are easier to
> use? E.g. Gemalto or G&D or anything in that di
On Sun, 3 Jun 2012 20:17, ventur...@gmail.com said:
> By disabling the insternal driver I was able to able to generate keys
> up to 3072 bits on my v2 card using a SCM-335 card reader via
> pcsclite.
That is a different problem than that with the Omnikey reader. In your
case the permissions of
Hi Rob,
I was having the same issue on FreeBSD & recently manage to address
the issue, it turned out to be the internal CCID driver which was the
cause of the problem, what worked for me was to install pcsc-lite &
libccid, then set my ~/gnupg/scdaemon.conf as:
disable-ccid
pcsc-driver libpcsclite.s
On Sun, 3 Jun 2012 17:45:16 +0200
Robin Kipp wrote:
> Hi,
>
> Am 03.06.2012 um 16:46 schrieb Branko Majic:
>
> > Well, OmniKey is famous for not working with stock libccid and
> > extended apdus. I had such problems with the OpenSC pkcs#11 and
> > pcscd. Can you try smaller key sizes (never wor
Hi Werner,
Am 03.06.2012 um 16:45 schrieb Werner Koch:
> All OMNIKEY based readers don't work with Linux or other free OS when
> Extended Length APDUs are required. I did a few hacks to allow the
> internal ccid driver to _sometimes_ work. libccid (of libpcsclite) has
> a list of supported read
Hi,
Am 03.06.2012 um 16:46 schrieb Branko Majic:
> Well, OmniKey is famous for not working with stock libccid and extended
> apdus. I had such problems with the OpenSC pkcs#11 and pcscd. Can you try
> smaller key sizes (never worked with OpenPGP, but it "solved" the issue for
> me - using 1k k
Well, OmniKey is famous for not working with stock libccid and extended apdus.
I had such problems with the OpenSC pkcs#11 and pcscd. Can you try smaller key
sizes (never worked with OpenPGP, but it "solved" the issue for me - using 1k
keys instead of 2k)
Robin Kipp wrote:
>Hi Werner,
>
>Am 0
Hi Werner,
Am 03.06.2012 um 12:29 schrieb Werner Koch:
> What reader are you using? It is possible that your reader does not
> support extended length APDUs, which are required for v2 cards.
Hmmm, very interesting. I'm using an OMNIKEY 6121 USB card reader, which I
purchased along with my Open
On Sat, 2 Jun 2012 17:39, mli...@robin-kipp.net said:
> 2012-06-02 15:46:48 scdaemon[6044] pcsc_transmit failed: not transacted
> (0x80100016)
What reader are you using? It is possible that your reader does not
support extended length APDUs, which are required for v2 cards.
Shalom-Salam,
Hi Peter,
Am 02.06.2012 um 18:17 schrieb Peter Lebbing:
>> However, it seems that I currently can neither copy nor create keys larger
>> than 1024bit on the SmartCard.
>
> Which exact OpenPGP-compatible card do you have? The v1.1 card only supports
> up
> to 1024 bit. The v2.0 card is capable o
> However, it seems that I currently can neither copy nor create keys larger
> than 1024bit on the SmartCard.
Which exact OpenPGP-compatible card do you have? The v1.1 card only supports up
to 1024 bit. The v2.0 card is capable of larger keys.
Peter.
--
I use the GNU Privacy Guard (GnuPG) in co
Hello all,
I'm trying to setup my OpenPGP-compatible SmartCard with 2048-bit subkeys,
using GnuPG version 2.0.18. However, it seems that I currently can neither copy
nor create keys larger than 1024bit on the SmartCard.
When I try to generate a completely new set of keys on the card using gpg
--
12 matches
Mail list logo
