Gnupg-users Digest, Vol 85, Issue 25
loadandenjoy at hotmail.com
loadandenjoy at hotmail.com
Tue Oct 26 15:02:13 CEST 2010
i would like to un subscribe to the digest. Thank you much. Or if you could send me the right link so I can do it
Regards
Sent on the Sprint® Now Network from my BlackBerry®
-----Original Message-----
From: gnupg-users-request at gnupg.org
Sender: gnupg-users-bounces at gnupg.org
Date: Sun, 24 Oct 2010 21:33:10
To: <gnupg-users at gnupg.org>
Reply-To: gnupg-users at gnupg.org
Subject: Gnupg-users Digest, Vol 85, Issue 25
Send Gnupg-users mailing list submissions to
gnupg-users at gnupg.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.gnupg.org/mailman/listinfo/gnupg-users
or, via email, send a message with subject or body 'help' to
gnupg-users-request at gnupg.org
You can reach the person managing the list at
gnupg-users-owner at gnupg.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Gnupg-users digest..."
Today's Topics:
1. Re: Security considerations: CAST-128 (Werner Koch)
2. Re: Changing secret key encryption algorithms (Paul Richard Ramer)
3. Re: gpgkey2ssh (Alex Mauer)
4. [PATCH] Issue 1238 (scdaemon often needs restarting after
removing OpenPGP smartcard) (Nedko Arnaudov)
5. Re: Changing secret key encryption algorithms (David Shaw)
6. gnupg mirrors (was: Re: [Announce] GnuPG 1.4.11 released)
(Jason Harris)
7. Re: Confirmation for cached passphrases useful? (Ingo Kl?cker)
8. "card inactive" (Osama Khalid)
----------------------------------------------------------------------
Message: 1
Date: Fri, 22 Oct 2010 10:10:44 +0200
From: Werner Koch <wk at gnupg.org>
To: Dan Cowsill <danthehat at gmail.com>
Cc: gnupg-users at gnupg.org
Subject: Re: Security considerations: CAST-128
Message-ID: <87zku6sl4r.fsf at vigenere.g10code.de>
Content-Type: text/plain; charset=us-ascii
On Thu, 21 Oct 2010 18:41, danthehat at gmail.com said:
> I'm not sure how computationally feasible they are. According to the
> paper, successful attacks were conducted on a 4 and 6 round version of
> CAST-128.
You can mount attacks on all algorithms if you reduce the number of
rounds. In particular if you reduce them from 16 to 4. Without having
read the paper I am pretty sure that an attack on a reduced round
version of CAST has has no practical consequence.
Shalom-Salam,
Werner
--
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
------------------------------
Message: 2
Date: Fri, 22 Oct 2010 01:51:10 -0700
From: Paul Richard Ramer <free10pro at gmail.com>
To: Dan Cowsill <danthehat at gmail.com>
Cc: gnupg-users at gnupg.org
Subject: Re: Changing secret key encryption algorithms
Message-ID: <4CC1507E.6070506 at gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
On Thu, 21 Oct 2010 09:40:11 -0700, Dan Cowsill wrote:
> It seems the algorithms are mapped to algo ID's. I can confirm that the
> algorithm is different than than the one used on my real secret key, but
> I had not been able to find any resources that map the algo ID's to
> their respective names with any completeness. I was able to find an
> excellent (if dated) resource on secret keys in the process[1].
Page 62 of RFC4880 <http://www.rfc-editor.org/rfc/rfc4880.txt> specifies
the IDs of symmetric algorithms, and RFC5581
<http://www.rfc-editor.org/rfc/rfc5581.txt> specifies the IDs for the
Camellia cipher.
-Paul
--
Please use my PGP key when sending me e-mail, if you can.
PGP Key ID: 0x3DB6D884
PGP Fingerprint: EBA7 88B3 6D98 2D4A E045 A9F7 C7C6 6ADF 3DB6 D884
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 630 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20101022/366b6b71/attachment-0001.pgp>
------------------------------
Message: 3
Date: Fri, 22 Oct 2010 11:04:18 -0500
From: Alex Mauer <hawke at hawkesnest.net>
To: gnupg-users at gnupg.org
Subject: Re: gpgkey2ssh
Message-ID: <i9scm2$kip$1 at dough.gmane.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
On 10/22/2010 03:02 AM, Werner Koch wrote:
> The whole point of the ssh support is to replace ssh-agent: gpg-agent if
> started with the option --enable-ssh-support implements the
> ssh-agent-protocol and thus works with ssh and ssh-add.
> If you want to use an existing gpg key with ssh you need a way to put it
> into gpg-agent. If you use smartcards then there is no need for this
> because gpg-agent does that of its own.
Why does it not do this on its own for non-smartcard authentication
keys? Shouldn?t they already be in gpg-agent?
?Alex Mauer ?hawke?
------------------------------
Message: 4
Date: Fri, 22 Oct 2010 17:57:59 +0300
From: Nedko Arnaudov <nedko at arnaudov.name>
To: gnupg-devel at gnupg.org, gnupg-users at gnupg.org
Subject: [PATCH] Issue 1238 (scdaemon often needs restarting after
removing OpenPGP smartcard)
Message-ID: <874oce46mg.fsf at usbix.spacelabs.org>
Content-Type: text/plain; charset="us-ascii"
I've been hit by this bug and I made a quick (and maybe wrong and
nasty) fix that works for me. The patch is attached to this mail and
also is available here:
http://nedko.arnaudov.name/soft/gnupg-2.0.16-Issue1238.patch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: gnupg-2.0.16-Issue1238.patch
Type: text/x-patch
Size: 582 bytes
Desc: not available
URL: </pipermail/attachments/20101022/c7ab9da4/attachment-0001.bin>
-------------- next part --------------
My test case is:
1. start pcscd
2. insert the usb reader
3. start gpg-agent (it starts scdaemon)
4. gpg --card-status
[success, polling of card status starts]
5. remove the reader
[polling of card status continues, scdaemon notices card status change, 7->0]
6. gpg --card-status
[expected failure,
scdaemon logs: "PC/SC RESET failed: invalid value (0x80100011)",
stops the polling and a disconnect message can be seen in the pcscd log]
7. insert the reader
8. gpg --card-status
[failure, but should succeed because the card is available now]
I noticed that if step 6 is skipped, step 8 will succeed.
The patch does the code to not attempt to reset if it is known that card
is not present.
My card reader is Omnikey Cardman 6121
My smartcard is OpenPGP v2
I use the proprietary driver for the reader (ifdokccid_lnx-3.6.0.tar.gz)
scdaemon still does not fully handle card insertions and removals. It
fails permanently if I attempt to access the card before it is inserted
for first time.
--
Nedko Arnaudov <GnuPG KeyID: 5D1B58ED>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 489 bytes
Desc: not available
URL: </pipermail/attachments/20101022/c7ab9da4/attachment-0001.pgp>
------------------------------
Message: 5
Date: Fri, 22 Oct 2010 13:46:45 -0400
From: David Shaw <dshaw at jabberwocky.com>
To: Paul Richard Ramer <free10pro at gmail.com>
Cc: gnupg-users at gnupg.org
Subject: Re: Changing secret key encryption algorithms
Message-ID: <ACA5A058-78A0-4980-BB36-F39BC7FE738C at jabberwocky.com>
Content-Type: text/plain; charset=us-ascii
On Oct 22, 2010, at 4:51 AM, Paul Richard Ramer wrote:
> On Thu, 21 Oct 2010 09:40:11 -0700, Dan Cowsill wrote:
>> It seems the algorithms are mapped to algo ID's. I can confirm that the
>> algorithm is different than than the one used on my real secret key, but
>> I had not been able to find any resources that map the algo ID's to
>> their respective names with any completeness. I was able to find an
>> excellent (if dated) resource on secret keys in the process[1].
>
> Page 62 of RFC4880 <http://www.rfc-editor.org/rfc/rfc4880.txt> specifies
> the IDs of symmetric algorithms, and RFC5581
> <http://www.rfc-editor.org/rfc/rfc5581.txt> specifies the IDs for the
> Camellia cipher.
If you ever need a handy reference for which algorithm maps to which number, just run "gpg -v --version". It will print out which ciphers it has support for, and their algorithm numbers.
David
------------------------------
Message: 6
Date: Sat, 23 Oct 2010 16:53:23 -0400
From: Jason Harris <jharris at widomaker.com>
To: gnupg-users at gnupg.org
Cc: Jason Harris <jharris at widomaker.com>
Subject: gnupg mirrors (was: Re: [Announce] GnuPG 1.4.11 released)
Message-ID: <20101023205323.GA6811 at laptop>
Content-Type: text/plain; charset="us-ascii"
On Mon, Oct 18, 2010 at 08:36:59PM +0200, Werner Koch wrote:
> On Mon, 18 Oct 2010 18:36, jharris at widomaker.com said:
> > The .exe is there and matches the SHA-1, but the .sig isn't there:
>
> Ooops. Forgot to upload that one - fixed. Sorry.
> Actually, our FTP server would not have a problem to serve all requests.
> The mirrors are more a historics thing but more an more folks wan't to
> mirror (I recently added a rel=nofollow in case some of them intent to
> bump up their page rank).
>
> I should change the wording of the announcement.
OK, good to know. Thanks for the fixes.
> Thanks for the hint of the mktorrent; maybe I can add this to our
> webpage anyway.
Actually, and somewhat fortunately, I didn't find any BitTorrent
trackers I like that worked automagically (without login and manual
upload of a .torrent) and with elinks/aria2c/lftp. aria2c was happy
to ignore a non-existent tracker at localhost and do everything from
web seeds, however. Of course, it should do equally well using a
metalink, and without the problem of exporting cryptography for
US-based users...
For now, I found the following changes in the GnuPG mirrors:
http://ftp.linux.it/pub/mirrors/gnupg/ new (listed by FreeBSD)
ftp://sunsite.cnlab-switch.ch/mirror/gnupg/ new (listed by FreeBSD)
ftp://ftp.bit.nl/mirror/gnupg/ is incomplete
ftp://ftp.demon.nl/pub/mirrors/gnupg/ no longer mirrors gpg
ftp://ftp.surfnet.nl/pub/security/gnupg/ stopped mirroring gpg in 2007
http://gd.tuwien.ac.at/privacy/gnupg/ serves files, but no listings
http://www.gnupg.ca/ mirrors website, not files
--
Jason Harris | PGP: This _is_ PGP-signed, isn't it?
jharris at widomaker.com _|_ Got photons? (TM), (C) 2004
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 314 bytes
Desc: not available
URL: </pipermail/attachments/20101023/9aa9a4a9/attachment-0001.pgp>
------------------------------
Message: 7
Date: Sun, 24 Oct 2010 00:27:54 +0200
From: Ingo Kl?cker <kloecker at kde.org>
To: gnupg-users at gnupg.org
Subject: Re: Confirmation for cached passphrases useful?
Message-ID: <201010240027.55179 at thufir.ingo-kloecker.de>
Content-Type: text/plain; charset="utf-8"
On Monday 18 October 2010, Faramir wrote:
> El 17-10-2010 22:09, Doug Barton escribi?:
> > On 10/17/2010 5:43 PM, Faramir wrote:
> > | That may be true. However, remember feeling secure is part of
> > | security
> > |
> > | too, so if that feature doesn't break anything, and make people
> > | sleep better...
> >
> > Two problems with that theory. The first is that a false sense of
> > security does more harm than good. The second is that there is no
> > such thing as a zero-cost change to software. So any proposed
> > change has to have benefits that outweigh the costs. Of course
> > accurately anticipating those costs is a whole different category
> > of problems. :)
>
> Right, I agree, we don't want those stones that keeps tigers away.
> But as long as people know the feature may be ignored by malware, it
> wouldn't be false sense of security, maybe it would be the solution
> against false sense of insecurity (if such thing exist).
>
> Also, I was not saying anything about costs of adding the feature,
> so my message should have said: "if there is a developer willing to
> add it, and it doesn't break anything, and it can be disabled by
> user, I'm ok with it". Please note I'm not requesting that feature,
> I just said I would not oppose to it's addition.
The feature might not break anything now but it will make the software
more complex. More complex software tends to break more easily. One of
the main design goals of gpg-agent, pinentry, etc., was to keep the code
of those small helper applications dealing with the secret keys and the
passphrases as simple as possible to avoid the complexity trap.
Also, it's a popular fallacy that adding a feature generates cost only
once. Every new feature will increase the maintenance costs and thus
generate additional cost for the whole lifetime of the software.
Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/attachments/20101024/0deb2a2f/attachment-0001.pgp>
------------------------------
Message: 8
Date: Sun, 24 Oct 2010 21:40:10 +0300
From: Osama Khalid <osamak at gnu.org>
To: gnupg-users at gnupg.org
Subject: "card inactive"
Message-ID: <20101024184010.GA3262 at osama-laptop>
Content-Type: text/plain; charset="us-ascii"
Hello,
I've been using FSFE Fellowship OpenPGP smartcard for a couple of
weeks and now I'm getting error messages.
I wonder if it's the smartcard reader (SCR335) or the smartcard
itself.
I've attached the output of:
gpg --debug 2048 --debug-ccid-driver -v --card-status
My gpg version is 1.4.10 and it is the one that comes with
Ubuntu-10.04-based systems (I use Trisquel 4.0).
I'd appreciate any hint.
--Osama Khalid
-------------- next part --------------
$ gpg --debug 2048 --debug-ccid-driver -v --card-status
gpg: reading options from `/home/<username>/.gnupg/gpg.conf'
gpg: DBG: ccid-driver: using CCID reader 0 (ID=04E6:5115:21120811308114:0)
gpg: DBG: ccid-driver: idVendor: 04E6 idProduct: 5115 bcdDevice: 0518
gpg: DBG: ccid-driver: ChipCard Interface Descriptor:
gpg: DBG: ccid-driver: bLength 54
gpg: DBG: ccid-driver: bDescriptorType 33
gpg: DBG: ccid-driver: bcdCCID 1.00
gpg: DBG: ccid-driver: nMaxSlotIndex 0
gpg: DBG: ccid-driver: bVoltageSupport 1 5.0V
gpg: DBG: ccid-driver: dwProtocols 3 T=0 T=1
gpg: DBG: ccid-driver: dwDefaultClock 4000
gpg: DBG: ccid-driver: dwMaxiumumClock 12000
gpg: DBG: ccid-driver: bNumClockSupported 0
gpg: DBG: ccid-driver: dwDataRate 9600 bps
gpg: DBG: ccid-driver: dwMaxDataRate 307200 bps
gpg: DBG: ccid-driver: bNumDataRatesSupp. 0
gpg: DBG: ccid-driver: dwMaxIFSD 252
gpg: DBG: ccid-driver: dwSyncProtocols 00000000
gpg: DBG: ccid-driver: dwMechanical 00000000
gpg: DBG: ccid-driver: dwFeatures 000100BA
gpg: DBG: ccid-driver: Auto configuration based on ATR
gpg: DBG: ccid-driver: Auto voltage selection
gpg: DBG: ccid-driver: Auto clock change
gpg: DBG: ccid-driver: Auto baud rate change
gpg: DBG: ccid-driver: Auto PPS made by CCID
gpg: DBG: ccid-driver: TPDU level exchange
gpg: DBG: ccid-driver: dwMaxCCIDMsgLen 263
gpg: DBG: ccid-driver: bClassGetResponse echo
gpg: DBG: ccid-driver: bClassEnvelope echo
gpg: DBG: ccid-driver: wlcdLayout none
gpg: DBG: ccid-driver: bPINSupport 0
gpg: DBG: ccid-driver: bMaxCCIDBusySlots 1
gpg: DBG: ccid-driver: PC_to_RDR_IccPowerOn:
gpg: DBG: ccid-driver: dwLength ..........: 0
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 1
gpg: DBG: ccid-driver: bPowerSelect ......: 0x00 (auto)
gpg: DBG: ccid-driver: [0008] 00 00
gpg: DBG: ccid-driver: RDR_to_PC_DataBlock:
gpg: DBG: ccid-driver: dwLength ..........: 0
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 1
gpg: DBG: ccid-driver: bStatus ...........: 65
gpg: DBG: ccid-driver: bError ............: 254
gpg: DBG: ccid-driver: CCID command failed: CCID timed out while talking to the ICC
gpg: reader slot 0: using ccid driver
gpg: DBG: send apdu: c=00 i=A4 p1=04 p2=00 lc=6 le=-1 em=0
gpg: DBG: ccid-driver: PC_to_RDR_IccPowerOn:
gpg: DBG: ccid-driver: dwLength ..........: 0
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 3
gpg: DBG: ccid-driver: bPowerSelect ......: 0x00 (auto)
gpg: DBG: ccid-driver: [0008] 00 00
gpg: DBG: ccid-driver: RDR_to_PC_DataBlock:
gpg: DBG: ccid-driver: dwLength ..........: 0
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 3
gpg: DBG: ccid-driver: bStatus ...........: 65
gpg: DBG: ccid-driver: bError ............: 254
gpg: DBG: ccid-driver: CCID command failed: CCID timed out while talking to the ICC
gpg: apdu_send_simple(0) failed: card inactive
gpg: DBG: ccid-driver: PC_to_RDR_IccPowerOff:
gpg: DBG: ccid-driver: dwLength ..........: 0
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 4
gpg: DBG: ccid-driver: [0007] 00 00 00
gpg: DBG: ccid-driver: RDR_to_PC_SlotStatus:
gpg: DBG: ccid-driver: dwLength ..........: 0
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 4
gpg: DBG: ccid-driver: bStatus ...........: 1
gpg: DBG: ccid-driver: bClockStatus ......: 0x01 (stopped-L)
gpg: DBG: ccid-driver: idVendor: 04E6 idProduct: 5115 bcdDevice: 0518
gpg: DBG: ccid-driver: ChipCard Interface Descriptor:
gpg: DBG: ccid-driver: bLength 54
gpg: DBG: ccid-driver: bDescriptorType 33
gpg: DBG: ccid-driver: bcdCCID 1.00
gpg: DBG: ccid-driver: nMaxSlotIndex 0
gpg: DBG: ccid-driver: bVoltageSupport 1 5.0V
gpg: DBG: ccid-driver: dwProtocols 3 T=0 T=1
gpg: DBG: ccid-driver: dwDefaultClock 4000
gpg: DBG: ccid-driver: dwMaxiumumClock 12000
gpg: DBG: ccid-driver: bNumClockSupported 0
gpg: DBG: ccid-driver: dwDataRate 9600 bps
gpg: DBG: ccid-driver: dwMaxDataRate 307200 bps
gpg: DBG: ccid-driver: bNumDataRatesSupp. 0
gpg: DBG: ccid-driver: dwMaxIFSD 252
gpg: DBG: ccid-driver: dwSyncProtocols 00000000
gpg: DBG: ccid-driver: dwMechanical 00000000
gpg: DBG: ccid-driver: dwFeatures 000100BA
gpg: DBG: ccid-driver: Auto configuration based on ATR
gpg: DBG: ccid-driver: Auto voltage selection
gpg: DBG: ccid-driver: Auto clock change
gpg: DBG: ccid-driver: Auto baud rate change
gpg: DBG: ccid-driver: Auto PPS made by CCID
gpg: DBG: ccid-driver: TPDU level exchange
gpg: DBG: ccid-driver: dwMaxCCIDMsgLen 263
gpg: DBG: ccid-driver: bClassGetResponse echo
gpg: DBG: ccid-driver: bClassEnvelope echo
gpg: DBG: ccid-driver: wlcdLayout none
gpg: DBG: ccid-driver: bPINSupport 0
gpg: DBG: ccid-driver: bMaxCCIDBusySlots 1
gpg: DBG: ccid-driver: using CCID reader 0 (ID=04E6:5115:21120811308114:0)
gpg: DBG: ccid-driver: idVendor: 04E6 idProduct: 5115 bcdDevice: 0518
gpg: DBG: ccid-driver: ChipCard Interface Descriptor:
gpg: DBG: ccid-driver: bLength 54
gpg: DBG: ccid-driver: bDescriptorType 33
gpg: DBG: ccid-driver: bcdCCID 1.00
gpg: DBG: ccid-driver: nMaxSlotIndex 0
gpg: DBG: ccid-driver: bVoltageSupport 1 5.0V
gpg: DBG: ccid-driver: dwProtocols 3 T=0 T=1
gpg: DBG: ccid-driver: dwDefaultClock 4000
gpg: DBG: ccid-driver: dwMaxiumumClock 12000
gpg: DBG: ccid-driver: bNumClockSupported 0
gpg: DBG: ccid-driver: dwDataRate 9600 bps
gpg: DBG: ccid-driver: dwMaxDataRate 307200 bps
gpg: DBG: ccid-driver: bNumDataRatesSupp. 0
gpg: DBG: ccid-driver: dwMaxIFSD 252
gpg: DBG: ccid-driver: dwSyncProtocols 00000000
gpg: DBG: ccid-driver: dwMechanical 00000000
gpg: DBG: ccid-driver: dwFeatures 000100BA
gpg: DBG: ccid-driver: Auto configuration based on ATR
gpg: DBG: ccid-driver: Auto voltage selection
gpg: DBG: ccid-driver: Auto clock change
gpg: DBG: ccid-driver: Auto baud rate change
gpg: DBG: ccid-driver: Auto PPS made by CCID
gpg: DBG: ccid-driver: TPDU level exchange
gpg: DBG: ccid-driver: dwMaxCCIDMsgLen 263
gpg: DBG: ccid-driver: bClassGetResponse echo
gpg: DBG: ccid-driver: bClassEnvelope echo
gpg: DBG: ccid-driver: wlcdLayout none
gpg: DBG: ccid-driver: bPINSupport 0
gpg: DBG: ccid-driver: bMaxCCIDBusySlots 1
gpg: DBG: ccid-driver: PC_to_RDR_IccPowerOn:
gpg: DBG: ccid-driver: dwLength ..........: 0
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 1
gpg: DBG: ccid-driver: bPowerSelect ......: 0x00 (auto)
gpg: DBG: ccid-driver: [0008] 00 00
gpg: DBG: ccid-driver: RDR_to_PC_DataBlock:
gpg: DBG: ccid-driver: dwLength ..........: 0
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 1
gpg: DBG: ccid-driver: bStatus ...........: 65
gpg: DBG: ccid-driver: bError ............: 254
gpg: DBG: ccid-driver: CCID command failed: CCID timed out while talking to the ICC
gpg: reader slot 0: using ccid driver
gpg: DBG: send apdu: c=00 i=A4 p1=04 p2=00 lc=6 le=-1 em=0
gpg: DBG: ccid-driver: PC_to_RDR_IccPowerOn:
gpg: DBG: ccid-driver: dwLength ..........: 0
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 3
gpg: DBG: ccid-driver: bPowerSelect ......: 0x00 (auto)
gpg: DBG: ccid-driver: [0008] 00 00
gpg: DBG: ccid-driver: RDR_to_PC_DataBlock:
gpg: DBG: ccid-driver: dwLength ..........: 0
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 3
gpg: DBG: ccid-driver: bStatus ...........: 65
gpg: DBG: ccid-driver: bError ............: 254
gpg: DBG: ccid-driver: CCID command failed: CCID timed out while talking to the ICC
gpg: apdu_send_simple(0) failed: card inactive
gpg: DBG: ccid-driver: PC_to_RDR_IccPowerOff:
gpg: DBG: ccid-driver: dwLength ..........: 0
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 4
gpg: DBG: ccid-driver: [0007] 00 00 00
gpg: DBG: ccid-driver: RDR_to_PC_SlotStatus:
gpg: DBG: ccid-driver: dwLength ..........: 0
gpg: DBG: ccid-driver: bSlot .............: 0
gpg: DBG: ccid-driver: bSeq ..............: 4
gpg: DBG: ccid-driver: bStatus ...........: 1
gpg: DBG: ccid-driver: bClockStatus ......: 0x01 (stopped-L)
gpg: DBG: ccid-driver: idVendor: 04E6 idProduct: 5115 bcdDevice: 0518
gpg: DBG: ccid-driver: ChipCard Interface Descriptor:
gpg: DBG: ccid-driver: bLength 54
gpg: DBG: ccid-driver: bDescriptorType 33
gpg: DBG: ccid-driver: bcdCCID 1.00
gpg: DBG: ccid-driver: nMaxSlotIndex 0
gpg: DBG: ccid-driver: bVoltageSupport 1 5.0V
gpg: DBG: ccid-driver: dwProtocols 3 T=0 T=1
gpg: DBG: ccid-driver: dwDefaultClock 4000
gpg: DBG: ccid-driver: dwMaxiumumClock 12000
gpg: DBG: ccid-driver: bNumClockSupported 0
gpg: DBG: ccid-driver: dwDataRate 9600 bps
gpg: DBG: ccid-driver: dwMaxDataRate 307200 bps
gpg: DBG: ccid-driver: bNumDataRatesSupp. 0
gpg: DBG: ccid-driver: dwMaxIFSD 252
gpg: DBG: ccid-driver: dwSyncProtocols 00000000
gpg: DBG: ccid-driver: dwMechanical 00000000
gpg: DBG: ccid-driver: dwFeatures 000100BA
gpg: DBG: ccid-driver: Auto configuration based on ATR
gpg: DBG: ccid-driver: Auto voltage selection
gpg: DBG: ccid-driver: Auto clock change
gpg: DBG: ccid-driver: Auto baud rate change
gpg: DBG: ccid-driver: Auto PPS made by CCID
gpg: DBG: ccid-driver: TPDU level exchange
gpg: DBG: ccid-driver: dwMaxCCIDMsgLen 263
gpg: DBG: ccid-driver: bClassGetResponse echo
gpg: DBG: ccid-driver: bClassEnvelope echo
gpg: DBG: ccid-driver: wlcdLayout none
gpg: DBG: ccid-driver: bPINSupport 0
gpg: DBG: ccid-driver: bMaxCCIDBusySlots 1
Please insert the card and hit return or enter 'c' to cancel:
gpg: Interrupt caught ... exiting
------------------------------
_______________________________________________
Gnupg-users mailing list
Gnupg-users at gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-users
End of Gnupg-users Digest, Vol 85, Issue 25
*******************************************
More information about the Gnupg-users
mailing list