From wk at gnupg.org Wed Mar 1 20:27:00 2017 From: wk at gnupg.org (Werner Koch) Date: Wed, 01 Mar 2017 20:27:00 +0100 Subject: [Announce] GnuPG 2.1.19 released Message-ID: <87d1e0bxx7.fsf@wheatstone.g10code.de> Hello! The GnuPG team is pleased to announce the availability of a new release of GnuPG: version 2.1.19. See below for a list of new features and bug fixes. About GnuPG ============= The GNU Privacy Guard (GnuPG) is a complete and free implementation of the OpenPGP standard which is commonly abbreviated as PGP. GnuPG allows to encrypt and sign data and communication, features a versatile key management system as well as access modules for public key directories. GnuPG itself is a command line tool with features for easy integration with other applications. A wealth of frontend applications and libraries making use of GnuPG are available. As an Universal Crypto Engine GnuPG provides support for S/MIME and Secure Shell in addition to OpenPGP. There are two major flavours of GnuPG: - GnuPG 2.1 (dubbed "modern") comes with the latest features and is suggested for most users. This announcement is about this branch. - GnuPG 2.0 is an older but widely used branch which we will maintain until 2017-12-31. GnuPG is Free Software (meaning that it respects your freedom). It can be freely used, modified and distributed under the terms of the GNU General Public License. Noteworthy changes in version 2.1.19 ==================================== * gpg: Print a warning if Tor mode is requested but the Tor daemon is not running. * gpg: New status code DECRYPTION_KEY to print the actual private key used for decryption. * gpgv: New options --log-file and --debug. * gpg-agent: Revamp the prompts to ask for card PINs. * scd: Support for multiple card readers. * scd: Removed option --debug-disable-ticker. Ticker is used only when it is required to watch removal of device/card. * scd: Improved detection of card inserting and removal. * dirmngr: New option --disable-ipv4. * dirmngr: New option --no-use-tor to explicitly disable the use of Tor. * dirmngr: The option --allow-version-check is now required even if the option --use-tor is also used. * dirmngr: Handle a missing nsswitch.conf gracefully. * dirmngr: Avoid PTR lookups for keyserver pools. The are only done for the debug command "keyserver --hosttable". * dirmngr: Rework the internal certificate cache to support classes of certificates. Load system provided certificates on startup. Add options --tls, --no-crl, and --systrust to the "VALIDATE" command. * dirmngr: Add support for the ntbtls library. * wks: Create mails with a "WKS-Phase" header. Fix detection of Draft-2 mode. * The Windows installer is now build with limited TLS support. * Many other bug fixes and new regression tests. A detailed description of the changes found in this 2.1 branch can be found at . Getting the Software ==================== Please follow the instructions found at or read on: GnuPG 2.1.19 may be downloaded from one of the GnuPG mirror sites or direct from its primary FTP server. The list of mirrors can be found at . Note that GnuPG is not available at ftp.gnu.org. The GnuPG source code compressed using BZIP2 and its OpenPGP signature are available here: https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.1.19.tar.bz2 (6255k) https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.1.19.tar.bz2.sig or here: ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-2.1.19.tar.bz2 ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-2.1.19.tar.bz2.sig An installer for Windows without any graphical frontend except for a very minimal Pinentry tool is available here: https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.1.19_20170301.exe (3670k) https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.1.19_20170301.exe.sig or here ftp://ftp.gnupg.org/gcrypt/binary/gnupg-w32-2.1.19_20170301.exe ftp://ftp.gnupg.org/gcrypt/binary/gnupg-w32-2.1.19_20170301.exe.sig The source used to build the Windows installer can be found in the same directory with a ".tar.xz" suffix. The Windows installer now comes with TOFU support, many translations, support for Tor, and limited support for HKPS and Web Key Directory. Checking the Integrity ====================== In order to check that the version of GnuPG which you are going to install is an original and unmodified one, you can do it in one of the following ways: * If you already have a version of GnuPG installed, you can simply verify the supplied signature. For example to verify the signature of the file gnupg-2.1.19.tar.bz2 you would use this command: gpg --verify gnupg-2.1.19.tar.bz2.sig gnupg-2.1.19.tar.bz2 This checks whether the signature file matches the source file. You should see a message indicating that the signature is good and made by one or more of the release signing keys. Make sure that this is a valid key, either by matching the shown fingerprint against a trustworthy list of valid release signing keys or by checking that the key has been signed by trustworthy other keys. See the end of this mail for information on the signing keys. * If you are not able to use an existing version of GnuPG, you have to verify the SHA-1 checksum. On Unix systems the command to do this is either "sha1sum" or "shasum". Assuming you downloaded the file gnupg-2.1.19.tar.bz2, you run the command like this: sha1sum gnupg-2.1.19.tar.bz2 and check that the output matches the next line: 10a088a6716789ac5c5cce2776952d8f4a5c57fc gnupg-2.1.19.tar.bz2 2614462170937abae1293cf227cacfb1028a11d3 gnupg-w32-2.1.19_20170301.exe abcfb15a59abb2bf05e9182133df53e5c5666272 gnupg-w32-2.1.19_20170301.tar.xz Internationalization ==================== This version of GnuPG has support for 26 languages with Chinese, Czech, French, German, Japanese, Norwegian, Russian, and Ukrainian being almost completely translated. Due to expected changes in forthcoming releases some strings pertaining to the TOFU code are not yet translated. Documentation ============= If you used GnuPG in the past you should read the description of changes and new features at doc/whats-new-in-2.1.txt or online at https://gnupg.org/faq/whats-new-in-2.1.html The file gnupg.info has the complete user manual of the system. Separate man pages are included as well but they have not all the details available as are the manual. It is also possible to read the complete manual online in HTML format at https://gnupg.org/documentation/manuals/gnupg/ or in Portable Document Format at https://gnupg.org/documentation/manuals/gnupg.pdf . The chapters on gpg-agent, gpg and gpgsm include information on how to set up the whole thing. You may also want search the GnuPG mailing list archives or ask on the gnupg-users mailing lists for advise on how to solve problems. Many of the new features are around for several years and thus enough public knowledge is already available. You may also want to follow our postings at and . Support ======== Please consult the archive of the gnupg-users mailing list before reporting a bug . We suggest to send bug reports for a new release to this list in favor of filing a bug at . If you need commercial support check out . If you are a developer and you need a certain feature for your project, please do not hesitate to bring it to the gnupg-devel mailing list for discussion. Maintenance and development of GnuPG is mostly financed by donations. The GnuPG project employs 4 full-time developers, one part-timer, and one contractor. They all work exclusivly on GnuPG and closely related software like Libgcrypt, GPGME, and GPA. Please consider to donate via: https://gnupg.org/donate/ Thanks ====== We have to thank all the people who helped with this release, be it testing, coding, translating, suggesting, auditing, administering the servers, spreading the word, answering questions on the mailing lists, and donating money. The GnuPG hackers, Andre, dkg, gniibe, Justus, Neal, and Werner p.s. This is an announcement only mailing list. Please send replies only to the gnupg-users'at'gnupg.org mailing list. p.p.s List of Release Signing Keys: To guarantee that a downloaded GnuPG version has not been tampered by malicious entities we provide signature files for all tarballs and binary versions. The keys are also signed by the long term keys of their respective owners. Current releases are signed by one or more of these four keys: 2048R/4F25E3B6 2011-01-12 [expires: 2019-12-31] Key fingerprint = D869 2123 C406 5DEA 5E0F 3AB5 249B 39D2 4F25 E3B6 Werner Koch (dist sig) rsa2048/E0856959 2014-10-29 [expires: 2019-12-31] Key fingerprint = 46CC 7308 65BB 5C78 EBAB ADCF 0437 6F3E E085 6959 David Shaw (GnuPG Release Signing Key) rsa2048/33BD3F06 2014-10-29 [expires: 2020-10-30] Key fingerprint = 031E C253 6E58 0D8E A286 A9F2 2071 B08A 33BD 3F06 NIIBE Yutaka (GnuPG Release Key) rsa2048/7EFD60D9 2014-10-19 [expires: 2020-12-31] Key fingerprint = D238 EA65 D64C 67ED 4C30 73F2 8A86 1B1C 7EFD 60D9 Werner Koch (Release Signing Key) The keys are available at and in any recently released GnuPG tarball in the file g10/distsigkey.gpg . Note that this mail has been signed by a different key. -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 194 bytes Desc: not available URL: -------------- next part -------------- _______________________________________________ Gnupg-announce mailing list Gnupg-announce at gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-announce From ankostis at gmail.com Wed Mar 1 21:03:51 2017 From: ankostis at gmail.com (ankostis) Date: Wed, 1 Mar 2017 21:03:51 +0100 Subject: [Announce] GnuPG 2.1.19 released In-Reply-To: <87d1e0bxx7.fsf@wheatstone.g10code.de> References: <87d1e0bxx7.fsf@wheatstone.g10code.de> Message-ID: Thank you for your efforts. Would it be possible with the next release to build also the python-2 & 3 bindings for Windows? Best, Kostis Anagnostopoulos On 1 March 2017 at 20:27, Werner Koch wrote: > Hello! > > The GnuPG team is pleased to announce the availability of a new release > of GnuPG: version 2.1.19. See below for a list of new features and bug > fixes. > > > About GnuPG > ============= > > The GNU Privacy Guard (GnuPG) is a complete and free implementation > of the OpenPGP standard which is commonly abbreviated as PGP. > > GnuPG allows to encrypt and sign data and communication, features a > versatile key management system as well as access modules for public key > directories. GnuPG itself is a command line tool with features for easy > integration with other applications. A wealth of frontend applications > and libraries making use of GnuPG are available. As an Universal Crypto > Engine GnuPG provides support for S/MIME and Secure Shell in addition to > OpenPGP. > > There are two major flavours of GnuPG: > > - GnuPG 2.1 (dubbed "modern") comes with the latest features and is > suggested for most users. This announcement is about this branch. > > - GnuPG 2.0 is an older but widely used branch which we will maintain > until 2017-12-31. > > GnuPG is Free Software (meaning that it respects your freedom). It can > be freely used, modified and distributed under the terms of the GNU > General Public License. > > > Noteworthy changes in version 2.1.19 > ==================================== > > * gpg: Print a warning if Tor mode is requested but the Tor daemon > is not running. > > * gpg: New status code DECRYPTION_KEY to print the actual private > key used for decryption. > > * gpgv: New options --log-file and --debug. > > * gpg-agent: Revamp the prompts to ask for card PINs. > > * scd: Support for multiple card readers. > > * scd: Removed option --debug-disable-ticker. Ticker is used > only when it is required to watch removal of device/card. > > * scd: Improved detection of card inserting and removal. > > * dirmngr: New option --disable-ipv4. > > * dirmngr: New option --no-use-tor to explicitly disable the use of > Tor. > > * dirmngr: The option --allow-version-check is now required even if > the option --use-tor is also used. > > * dirmngr: Handle a missing nsswitch.conf gracefully. > > * dirmngr: Avoid PTR lookups for keyserver pools. The are only done > for the debug command "keyserver --hosttable". > > * dirmngr: Rework the internal certificate cache to support classes > of certificates. Load system provided certificates on startup. > Add options --tls, --no-crl, and --systrust to the "VALIDATE" > command. > > * dirmngr: Add support for the ntbtls library. > > * wks: Create mails with a "WKS-Phase" header. Fix detection of > Draft-2 mode. > > * The Windows installer is now build with limited TLS support. > > * Many other bug fixes and new regression tests. > > A detailed description of the changes found in this 2.1 branch can be > found at . > > > Getting the Software > ==================== > > Please follow the instructions found at or > read on: > > GnuPG 2.1.19 may be downloaded from one of the GnuPG mirror sites or > direct from its primary FTP server. The list of mirrors can be found at > . Note that GnuPG is not > available at ftp.gnu.org. > > The GnuPG source code compressed using BZIP2 and its OpenPGP signature > are available here: > > https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.1.19.tar.bz2 (6255k) > https://gnupg.org/ftp/gcrypt/gnupg/gnupg-2.1.19.tar.bz2.sig > or here: > ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-2.1.19.tar.bz2 > ftp://ftp.gnupg.org/gcrypt/gnupg/gnupg-2.1.19.tar.bz2.sig > > An installer for Windows without any graphical frontend except for a > very minimal Pinentry tool is available here: > > https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.1.19_20170301.exe (3670k) > https://gnupg.org/ftp/gcrypt/binary/gnupg-w32-2.1.19_20170301.exe.sig > or here > ftp://ftp.gnupg.org/gcrypt/binary/gnupg-w32-2.1.19_20170301.exe > ftp://ftp.gnupg.org/gcrypt/binary/gnupg-w32-2.1.19_20170301.exe.sig > > The source used to build the Windows installer can be found in the same > directory with a ".tar.xz" suffix. The Windows installer now comes with > TOFU support, many translations, support for Tor, and limited support > for HKPS and Web Key Directory. > > > Checking the Integrity > ====================== > > In order to check that the version of GnuPG which you are going to > install is an original and unmodified one, you can do it in one of > the following ways: > > * If you already have a version of GnuPG installed, you can simply > verify the supplied signature. For example to verify the signature > of the file gnupg-2.1.19.tar.bz2 you would use this command: > > gpg --verify gnupg-2.1.19.tar.bz2.sig gnupg-2.1.19.tar.bz2 > > This checks whether the signature file matches the source file. > You should see a message indicating that the signature is good and > made by one or more of the release signing keys. Make sure that > this is a valid key, either by matching the shown fingerprint > against a trustworthy list of valid release signing keys or by > checking that the key has been signed by trustworthy other keys. > See the end of this mail for information on the signing keys. > > * If you are not able to use an existing version of GnuPG, you have > to verify the SHA-1 checksum. On Unix systems the command to do > this is either "sha1sum" or "shasum". Assuming you downloaded the > file gnupg-2.1.19.tar.bz2, you run the command like this: > > sha1sum gnupg-2.1.19.tar.bz2 > > and check that the output matches the next line: > > 10a088a6716789ac5c5cce2776952d8f4a5c57fc gnupg-2.1.19.tar.bz2 > 2614462170937abae1293cf227cacfb1028a11d3 gnupg-w32-2.1.19_20170301.exe > abcfb15a59abb2bf05e9182133df53e5c5666272 gnupg-w32-2.1.19_20170301.tar.xz > > > Internationalization > ==================== > > This version of GnuPG has support for 26 languages with Chinese, Czech, > French, German, Japanese, Norwegian, Russian, and Ukrainian being almost > completely translated. Due to expected changes in forthcoming releases > some strings pertaining to the TOFU code are not yet translated. > > > Documentation > ============= > > If you used GnuPG in the past you should read the description of > changes and new features at doc/whats-new-in-2.1.txt or online at > > https://gnupg.org/faq/whats-new-in-2.1.html > > The file gnupg.info has the complete user manual of the system. > Separate man pages are included as well but they have not all the > details available as are the manual. It is also possible to read the > complete manual online in HTML format at > > https://gnupg.org/documentation/manuals/gnupg/ > > or in Portable Document Format at > > https://gnupg.org/documentation/manuals/gnupg.pdf . > > The chapters on gpg-agent, gpg and gpgsm include information on how > to set up the whole thing. You may also want search the GnuPG mailing > list archives or ask on the gnupg-users mailing lists for advise on > how to solve problems. Many of the new features are around for > several years and thus enough public knowledge is already available. > > You may also want to follow our postings at > and . > > > Support > ======== > > Please consult the archive of the gnupg-users mailing list before > reporting a bug . > We suggest to send bug reports for a new release to this list in favor > of filing a bug at . If you need commercial > support check out . > > If you are a developer and you need a certain feature for your project, > please do not hesitate to bring it to the gnupg-devel mailing list for > discussion. > > Maintenance and development of GnuPG is mostly financed by donations. > The GnuPG project employs 4 full-time developers, one part-timer, and > one contractor. They all work exclusivly on GnuPG and closely related > software like Libgcrypt, GPGME, and GPA. Please consider to donate via: > > https://gnupg.org/donate/ > > > Thanks > ====== > > We have to thank all the people who helped with this release, be it > testing, coding, translating, suggesting, auditing, administering the > servers, spreading the word, answering questions on the mailing > lists, and donating money. > > > The GnuPG hackers, > > Andre, dkg, gniibe, Justus, Neal, and Werner > > > > p.s. > This is an announcement only mailing list. Please send replies only to > the gnupg-users'at'gnupg.org mailing list. > > p.p.s > List of Release Signing Keys: > > To guarantee that a downloaded GnuPG version has not been tampered by > malicious entities we provide signature files for all tarballs and > binary versions. The keys are also signed by the long term keys of > their respective owners. Current releases are signed by one or more > of these four keys: > > 2048R/4F25E3B6 2011-01-12 [expires: 2019-12-31] > Key fingerprint = D869 2123 C406 5DEA 5E0F 3AB5 249B 39D2 4F25 E3B6 > Werner Koch (dist sig) > > rsa2048/E0856959 2014-10-29 [expires: 2019-12-31] > Key fingerprint = 46CC 7308 65BB 5C78 EBAB ADCF 0437 6F3E E085 6959 > David Shaw (GnuPG Release Signing Key) > > rsa2048/33BD3F06 2014-10-29 [expires: 2020-10-30] > Key fingerprint = 031E C253 6E58 0D8E A286 A9F2 2071 B08A 33BD 3F06 > NIIBE Yutaka (GnuPG Release Key) > > rsa2048/7EFD60D9 2014-10-19 [expires: 2020-12-31] > Key fingerprint = D238 EA65 D64C 67ED 4C30 73F2 8A86 1B1C 7EFD 60D9 > Werner Koch (Release Signing Key) > > The keys are available at and in > any recently released GnuPG tarball in the file g10/distsigkey.gpg . > Note that this mail has been signed by a different key. > > -- > Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. > > _______________________________________________ > Gnupg-announce mailing list > Gnupg-announce at gnupg.org > http://lists.gnupg.org/mailman/listinfo/gnupg-announce > _______________________________________________ > Gnupg-users mailing list > Gnupg-users at gnupg.org > http://lists.gnupg.org/mailman/listinfo/gnupg-users > From gnupg-users at spodhuis.org Fri Mar 3 07:21:39 2017 From: gnupg-users at spodhuis.org (Phil Pennock) Date: Fri, 3 Mar 2017 01:21:39 -0500 Subject: Stripping expired subkey during export? Message-ID: <20170303062138.GA32472@breadbox.private.spodhuis.org> For certain exports of my PGP key, I want the key minimized and clean of cruft; while the public keyservers will reaccumulate all signatures, data-sources where "presence is trust" do not need everything else. Smaller keys for DNS records, certain authenticated databases, etc. I also recently updated my key 0x4D1E900E14C1CC04 to use sha256 for all bindings (by doing a pref update). gpg --export-options export-clean,export-minimal \ --export 0x4D1E900E14C1CC04 | gpg --list-packets | less All but one signature is `digest algo 8`. One is still `digest algo 2`. That's for keyid `A445DC2B1C5B7F39` which is _expired_. gpg (GnuPG) 2.1.19 libgcrypt 1.7.6 Why is `export-clean` not dropping the expired subkey? Is it that export-clean only filters unusable userids, not unusable subkeys? At this point, I'm not trying to remove the subkey because it's SHA1, but because it has expired. Since I already create a temp keyring (for export variants which drop 25519 sub-keys, to give to systems which break on those), I decided that I could apply an import-filter on that, since sig_digest_algo is import-only, so I used: --import-filter drop-sig='sig_digest_algo < 8' and then exported clean/minimal from there; but there's no change. This import filter appears to do nothing. Is this misunderstanding on my part, or a bug in GnuPG? If the former, is there enough here to point to the flaw in my mental model, so that someone can educate me please? Is there a reason beyond "nobody asked for it yet" why there's no "expired" filter for drop-subkey/drop-sig? Thanks, -Phil -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 996 bytes Desc: Digital signature URL: From wk at gnupg.org Fri Mar 3 09:57:39 2017 From: wk at gnupg.org (Werner Koch) Date: Fri, 03 Mar 2017 09:57:39 +0100 Subject: [Announce] GnuPG 2.1.19 released In-Reply-To: (ankostis@gmail.com's message of "Wed, 1 Mar 2017 21:03:51 +0100") References: <87d1e0bxx7.fsf@wheatstone.g10code.de> Message-ID: <871sue4u0s.fsf@wheatstone.g10code.de> On Wed, 1 Mar 2017 21:03, ankostis at gmail.com said: > Would it be possible with the next release to build also the python-2 > & 3 bindings for Windows? Good suggestion - we will look into it. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From wk at gnupg.org Fri Mar 3 09:51:57 2017 From: wk at gnupg.org (Werner Koch) Date: Fri, 03 Mar 2017 09:51:57 +0100 Subject: Stripping expired subkey during export? In-Reply-To: <20170303062138.GA32472@breadbox.private.spodhuis.org> (Phil Pennock's message of "Fri, 3 Mar 2017 01:21:39 -0500") References: <20170303062138.GA32472@breadbox.private.spodhuis.org> Message-ID: <87a8924uaa.fsf@wheatstone.g10code.de> On Fri, 3 Mar 2017 07:21, gnupg-users at spodhuis.org said: > Why is `export-clean` not dropping the expired subkey? Is it that > export-clean only filters unusable userids, not unusable subkeys? Right: /* Always do the cleaning on the public key part if requested. * Note that both export-clean and export-minimal only apply to * UID sigs (0x10, 0x11, 0x12, and 0x13). A designated * revocation is never stripped, even with export-minimal set. */ Not cleaning expired subkeys is a good thing for secret key export, so that you can keep on decyrpting old mails. Exporting an expired public key can be helpful to see your expired key. For sending keys to keyserver it would actually be better to remove expired encryption subkeys. But the keyservers will merge them anyway. As a compatible hack we could add an 'expired' property to the export-filter's drop-subkey method. Just did this: gpg --export-options export-clean \ --export-filter drop-subkey='expired -t' \ --export 1e42b367 removes all my expired subkeys. This is just a first step; we also need a properties for the key capability. > --import-filter drop-sig='sig_digest_algo < 8' > > and then exported clean/minimal from there; but there's no change. This > import filter appears to do nothing. drop-sigs does not work on self-signatures - might this be your problem? I have not done any these, though. > Is there a reason beyond "nobody asked for it yet" why there's no > "expired" filter for drop-subkey/drop-sig? No. I added filters only when I needed them. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From gerd.von.egidy at intra2net.com Fri Mar 3 18:04:15 2017 From: gerd.von.egidy at intra2net.com (Gerd v. Egidy) Date: Fri, 03 Mar 2017 18:04:15 +0100 Subject: Verify with missing public key: unexpected returncode Message-ID: <5444049.pHodmbYJJB@thunder.m.i2n> Hi, I have a scenario where a signature on a file should be checked. The file is signed by several keys and for this scenario it is ok if at least one is correct. In some cases it can happen that the system doing the check does not have access to all public keys that are used for signing. When reading the gpg2 manpage on return codes: > The program returns 0 if everything was fine, 1 if at least a signature was > bad, and other error codes for fatal errors. I think it should return 1 in this case. But I get 2. Why? Here are the commands to reproduce: $ gpg2 --verify test.asc.gpg gpg: Signature made Fri Mar 3 17:44:57 2017 CET using RSA key ID DB2D0998DC19EEA3 gpg: Good signature from "Foo Foo" [ultimate] gpg: Signature made Fri Mar 3 17:45:01 2017 CET using RSA key ID 467C036CA9014F3F gpg: Good signature from "Bar Bar" [ultimate] $ gpg2 --delete-secret-keys 467C036CA9014F3F $ gpg2 --delete-keys 467C036CA9014F3F $ gpg2 --verify test.asc.gpg ; echo "RET: $?" gpg: Signature made Fri Mar 3 17:44:57 2017 CET using RSA key ID DB2D0998DC19EEA3 gpg: checking the trustdb gpg: marginals needed: 3 completes needed: 1 trust model: pgp gpg: depth: 0 valid: 1 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 1u gpg: Good signature from "Foo Foo" [ultimate] gpg: Signature made Fri Mar 3 17:45:01 2017 CET using RSA key ID 467C036CA9014F3F gpg: Can't check signature: No public key RET: 2 Kind regards, Gerd From rjh at sixdemonbag.org Fri Mar 3 18:09:33 2017 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Fri, 3 Mar 2017 12:09:33 -0500 Subject: Verify with missing public key: unexpected returncode In-Reply-To: <5444049.pHodmbYJJB@thunder.m.i2n> References: <5444049.pHodmbYJJB@thunder.m.i2n> Message-ID: <70ff2c6f-2d87-31ad-5fcf-a3921fd80040@sixdemonbag.org> > I think it should return 1 in this case. But I get 2. Why? Because there were no bad signatures. A signature which cannot be verified is neither good nor bad, it just is. The alternative would be for GnuPG to return a bad signature literally *whenever* it had no public key with which to verify the signature, meaning that 99% of signatures on a mailing list would be reported as bad. Can you imagine the bug reports we'd get from people if that were the case? "Your software package is listing every single signed message I've received as being bad!" From kristian.fiskerstrand at sumptuouscapital.com Fri Mar 3 18:11:04 2017 From: kristian.fiskerstrand at sumptuouscapital.com (Kristian Fiskerstrand) Date: Fri, 3 Mar 2017 18:11:04 +0100 Subject: Verify with missing public key: unexpected returncode In-Reply-To: <5444049.pHodmbYJJB@thunder.m.i2n> References: <5444049.pHodmbYJJB@thunder.m.i2n> Message-ID: On 03/03/2017 06:04 PM, Gerd v. Egidy wrote: > When reading the gpg2 manpage on return codes: One quick observation, if using this in automated way and return code matters, you likely want to check out "gpgv", otherwise you should be parsing --status-fd output for more details -- ---------------------------- Kristian Fiskerstrand Blog: https://blog.sumptuouscapital.com Twitter: @krifisk ---------------------------- Public OpenPGP keyblock at hkp://pool.sks-keyservers.net fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 ---------------------------- Qui audet vincit Who dares wins -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From gerd.von.egidy at intra2net.com Fri Mar 3 18:24:08 2017 From: gerd.von.egidy at intra2net.com (Gerd v. Egidy) Date: Fri, 03 Mar 2017 18:24:08 +0100 Subject: Verify with missing public key: unexpected returncode In-Reply-To: <70ff2c6f-2d87-31ad-5fcf-a3921fd80040@sixdemonbag.org> References: <5444049.pHodmbYJJB@thunder.m.i2n> <70ff2c6f-2d87-31ad-5fcf-a3921fd80040@sixdemonbag.org> Message-ID: <3457091.Fg0io3Xr8y@thunder.m.i2n> Hi Robert, > > I think it should return 1 in this case. But I get 2. Why? > > Because there were no bad signatures. A signature which cannot be > verified is neither good nor bad, it just is. ok. > The alternative would be for GnuPG to return a bad signature literally > *whenever* it had no public key with which to verify the signature, > meaning that 99% of signatures on a mailing list would be reported as > bad. Can you imagine the bug reports we'd get from people if that were > the case? "Your software package is listing every single signed message > I've received as being bad!" Hmm, but according to the manpage you currently get a returncode meaning "fatal error" in this case. That sounds much more severe to me than a bad signature. Kind regards, Gerd From thomas.jarosch at intra2net.com Fri Mar 3 18:25:05 2017 From: thomas.jarosch at intra2net.com (Thomas Jarosch) Date: Fri, 03 Mar 2017 18:25:05 +0100 Subject: How U2F works In-Reply-To: <878tortdre.fsf@fsij.org> References: <878tortdre.fsf@fsij.org> Message-ID: <2883631.IehI8nyOGf@storm.m.i2n> On Tuesday, 28 February 2017 00:28:21 CET NIIBE Yutaka wrote: > Anyhow, it would be possible for Gnuk to add U2F support (somehow > limited, because of available resource on board). regarding limited resources, the Yubikey people did a fine trick: There is no per-website data stored on the Yubikey. So the amount of websites you can use a single FIDO U2F key for is unlimited. See "Limited storage on device" for details: https://developers.yubico.com/U2F/Protocol_details/Key_generation.html Also I think the attestation key is not enforced by websites, so gnuk could just send a bogus / user configurable cert. Cheers, Thomas From gerd.von.egidy at intra2net.com Fri Mar 3 18:28:16 2017 From: gerd.von.egidy at intra2net.com (Gerd v. Egidy) Date: Fri, 03 Mar 2017 18:28:16 +0100 Subject: Verify with missing public key: unexpected returncode In-Reply-To: References: <5444049.pHodmbYJJB@thunder.m.i2n> Message-ID: <15847112.GauK7WTFUM@thunder.m.i2n> Hi Kristian, On Friday, 03 March 2017 18:11:04 CET Kristian Fiskerstrand wrote: > On 03/03/2017 06:04 PM, Gerd v. Egidy wrote: > > When reading the gpg2 manpage on return codes: > One quick observation, if using this in automated way and return code > matters, you likely want to check out "gpgv", otherwise you should be > parsing --status-fd output for more details Yes, this is an automated scenario. I'm already using --status-fd and parsing it's output. But to be on the safe side, I was checking the return code too. With the way gpg2 currently implements the return codes it seems I can't use them. Kind regards, Gerd From thomas.jarosch at intra2net.com Fri Mar 3 18:28:51 2017 From: thomas.jarosch at intra2net.com (Thomas Jarosch) Date: Fri, 03 Mar 2017 18:28:51 +0100 Subject: [Announce] GnuPG 2.1.19 released In-Reply-To: <87d1e0bxx7.fsf@wheatstone.g10code.de> References: <87d1e0bxx7.fsf@wheatstone.g10code.de> Message-ID: <13306230.46fsF48Vrr@storm.m.i2n> On Wednesday, 01 March 2017 20:27:00 CET Werner Koch wrote: > Noteworthy changes in version 2.1.19 > ==================================== > > .. > > * scd: Support for multiple card readers. > > * scd: Improved detection of card inserting and removal. thanks for the new release! The support for multiple card readers sounds very promising. I tried that setup a year ago and it was difficult to configure two isolated scademons at the same time. Cheers, Thomas From jestedfa at microsoft.com Fri Mar 3 19:04:27 2017 From: jestedfa at microsoft.com (Jeffrey Stedfast) Date: Fri, 3 Mar 2017 18:04:27 +0000 Subject: Problems with GPGME returning "Not Implemented" or "Configuration error" In-Reply-To: References: Message-ID: <9A1C68DF-E850-4F3E-90CF-35B20D50BB65@microsoft.com> Anyone have any thoughts on this? On 2/27/17, 9:20 AM, "Gnupg-users on behalf of Jeffrey Stedfast" wrote: Hi all, I'm working on re-implementing GMime to use libgpgme (1.8.0 on Fedora 25) instead of using my own custom logic for fork()ing/exec()ing gpg & parsing the status-fd output to do PGP encryption and I've gotten that to work just fine for PGP, but I am having trouble using nearly identical logic (only diff is armor/textmode state) to sign or encrypt using the CMS backend. For some reason, gpgme_op_sign() is returning GPG_ERR_NOT_IMPLEMENTED while gpgme_op_encrypt() is returning "Configuration error". From what I can deduce by scouring the web for information, it seems like NOT_IMPLEMENTED should never get returned unless I am using options that just haven't been implemented yet but that doesn't seem like it should be the case since I don't think I'm doing anything out of the ordinary. When signing, I've set armor=0, textmode=0, mode=DETACH (or NORMAL), and added a signer to the context. For encrypting, I am getting "Configuration error" which I'm also confused about because I don't know what configuration options could be causing this. Once again, armor=0, textmode=0, flags=0, and I've created a NULL-terminated list of recipient keys to pass to gpgme_op_encrypt(). Since my unit tests are re-using the same gpgme context to import some smime certs, then export some certs, then sign some streams, etc - could that be the problem? As I write this email, I realize that's something I haven't yet checked... All I can think of is that perhaps there is some leftover state from gpgme_op_import() or gpgme_op_export_ext() that is breaking the gpgme_op_sign() when run at a later point? Thanks for any help or guidance in tracking down these issues, Jeff _______________________________________________ Gnupg-users mailing list Gnupg-users at gnupg.org https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Flists.gnupg.org%2Fmailman%2Flistinfo%2Fgnupg-users&data=02%7C01%7Cjestedfa%40microsoft.com%7Cb0a0640b2eed469e54fd08d45f3eba6b%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636238170396989821&sdata=FN1OyS2%2Byb2QBi4b8K2EoZqabLS%2FTzQgfDcVGGTHf%2B4%3D&reserved=0 From gnupg-users at spodhuis.org Sat Mar 4 00:13:40 2017 From: gnupg-users at spodhuis.org (Phil Pennock) Date: Fri, 3 Mar 2017 23:13:40 +0000 Subject: Stripping expired subkey during export? In-Reply-To: <87a8924uaa.fsf@wheatstone.g10code.de> References: <20170303062138.GA32472@breadbox.private.spodhuis.org> <87a8924uaa.fsf@wheatstone.g10code.de> Message-ID: <20170303231339.GA11006@tower.spodhuis.org> On 2017-03-03 at 09:51 +0100, Werner Koch wrote: > Not cleaning expired subkeys is a good thing for secret key export, so > that you can keep on decyrpting old mails. Sure, but this is a non-secret export, for the versions for publication. > Exporting an expired public > key can be helpful to see your expired key. I can see this for a signing key, so that old signatures can be validated, but I don't see that it's a helpful default for encryption subkeys, and since encryption subkeys are the only ones typically created by default, that seems dominant. > As a compatible hack we could add an 'expired' property to the > export-filter's drop-subkey method. Just did this: > > gpg --export-options export-clean \ > --export-filter drop-subkey='expired -t' \ > --export 1e42b367 > > removes all my expired subkeys. This is just a first step; we also need > a properties for the key capability. I see commit 1813f3be and will build/test this and report back on the devel list if I experience issues. Thanks! > drop-sigs does not work on self-signatures - might this be your problem? > I have not done any these, though. Ugh, yes. Thanks, I explored everything I could see and kept running into roadblocks. Thanks for clearing a new path through. -Phil From wk at gnupg.org Sat Mar 4 12:59:55 2017 From: wk at gnupg.org (Werner Koch) Date: Sat, 04 Mar 2017 12:59:55 +0100 Subject: export-minimal doesn't affect export-secret-key? In-Reply-To: <58ac102c-e77b-2f32-dbcc-222138022350@digitalbrains.com> (Peter Lebbing's message of "Sat, 25 Feb 2017 16:26:34 +0100") References: <680160cc-58e7-4f03-1624-e3a642791d75@digitalbrains.com> <87h93l970k.fsf@alice.fifthhorseman.net> <58ac102c-e77b-2f32-dbcc-222138022350@digitalbrains.com> Message-ID: <87efyd1cck.fsf@wheatstone.g10code.de> On Sat, 25 Feb 2017 16:26, peter at digitalbrains.com said: > I'd like to add to the bug report that I also observe this behaviour > with GnuPG 1.4.18 on Debian jessie/stable (package 1.4.18-7+deb8u3) and > GnuPG 2.0.26 on the same (package 2.0.26-6+deb8u1). So it is not just 2.1. FWIW, it has been fixed in 2.1.19. Fixing it in the other branches will likely not happen because over there a lot of code needs duplication. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From wk at gnupg.org Sat Mar 4 13:01:17 2017 From: wk at gnupg.org (Werner Koch) Date: Sat, 04 Mar 2017 13:01:17 +0100 Subject: Problems with GPGME returning "Not Implemented" or "Configuration error" In-Reply-To: <9A1C68DF-E850-4F3E-90CF-35B20D50BB65@microsoft.com> (Jeffrey Stedfast's message of "Fri, 3 Mar 2017 18:04:27 +0000") References: <9A1C68DF-E850-4F3E-90CF-35B20D50BB65@microsoft.com> Message-ID: <87a8911caa.fsf@wheatstone.g10code.de> Hi Jeff, On Fri, 3 Mar 2017 19:04, jestedfa at microsoft.com said: > Anyone have any thoughts on this? Soneone of us will get back to you on Monday. We have been pretty busy with the 2.1.19 release the last week. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From wk at gnupg.org Sat Mar 4 13:06:51 2017 From: wk at gnupg.org (Werner Koch) Date: Sat, 04 Mar 2017 13:06:51 +0100 Subject: [Announce] GnuPG 2.1.19 released In-Reply-To: <13306230.46fsF48Vrr@storm.m.i2n> (Thomas Jarosch's message of "Fri, 03 Mar 2017 18:28:51 +0100") References: <87d1e0bxx7.fsf@wheatstone.g10code.de> <13306230.46fsF48Vrr@storm.m.i2n> Message-ID: <8760jp1c10.fsf@wheatstone.g10code.de> On Fri, 3 Mar 2017 18:28, thomas.jarosch at intra2net.com said: > The support for multiple card readers sounds very promising. Indeed, I do not anymore need to open the door to the server room to change the card several times during release preparing (the commit key and the releasing signing key are on different cards). Caveat: You need to take to enter the right PIN for the right card. This was the reason why the prompts have been reworked to print the serial number of the card and the Name stored on the card. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From jestedfa at microsoft.com Sat Mar 4 13:52:41 2017 From: jestedfa at microsoft.com (Jeffrey Stedfast) Date: Sat, 4 Mar 2017 12:52:41 +0000 Subject: Problems with GPGME returning "Not Implemented" or "Configuration error" In-Reply-To: <87a8911caa.fsf@wheatstone.g10code.de> References: <9A1C68DF-E850-4F3E-90CF-35B20D50BB65@microsoft.com> <87a8911caa.fsf@wheatstone.g10code.de> Message-ID: <6C5CD61B-6299-4F98-AA0D-BD6FDB684255@microsoft.com> Hey Werner, No worries ? I know how busy things can get around a release. Jeff On 3/4/17, 7:01 AM, "Werner Koch" wrote: Hi Jeff, On Fri, 3 Mar 2017 19:04, jestedfa at microsoft.com said: > Anyone have any thoughts on this? Soneone of us will get back to you on Monday. We have been pretty busy with the 2.1.19 release the last week. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. From gerd.von.egidy at intra2net.com Mon Mar 6 00:27:30 2017 From: gerd.von.egidy at intra2net.com (Gerd v. Egidy) Date: Mon, 06 Mar 2017 00:27:30 +0100 Subject: Announcing paperbackup.py to backup keys as QR codes on paper In-Reply-To: References: <9664399.F7pj19RVc2@thunder.m.i2n> <2661606.PZSOA07WEn@thunder.m.i2n> Message-ID: <1621160.PWUglIu5gb@rdx.n.i2n> Hi Peter, > So I think the three initial bytes of an MD5 would work well to detect > typing errors. I just implemented the line checksums as discussed. Kind regards, Gerd From gniibe at fsij.org Mon Mar 6 04:17:55 2017 From: gniibe at fsij.org (NIIBE Yutaka) Date: Mon, 06 Mar 2017 12:17:55 +0900 Subject: How U2F works In-Reply-To: <2883631.IehI8nyOGf@storm.m.i2n> References: <878tortdre.fsf@fsij.org> <2883631.IehI8nyOGf@storm.m.i2n> Message-ID: <87h937f5zw.fsf@iwagami.gniibe.org> Thomas Jarosch wrote: > regarding limited resources, the Yubikey people did a fine trick: > There is no per-website data stored on the Yubikey. So the amount > of websites you can use a single FIDO U2F key for is unlimited. > > See "Limited storage on device" for details: > https://developers.yubico.com/U2F/Protocol_details/Key_generation.html > > > Also I think the attestation key is not enforced by websites, > so gnuk could just send a bogus / user configurable cert. Thanks a lot for the information. Well, I concluded that it is not worth (for me) to try to integrate U2F feature into Gnuk. If some free software friendly network service sites ask me a possibility to use such a method to authenticate their users, firstly I would propose better method which can respect users' computing better instead, secondly I would propose developing as a separate firmware implementation (possibly re-using Gnuk lower-level code) as compromise. The reason is: The use cases are so different: The model who/how controls crypto computation is so different. (I mean, Gnuk vs. U2F) I had been somewhat naive when I saw U2F specification at first. I was considering like: * While U2F uses X.509 certificate by the attestation key (in the specification), it could be OpenPGP certificate. * Free Software implementation of U2F would be nice thing. but, I leaned the reality. In my opinion, the attestation key is a "key", literary and it is not wise for network service providers not to check certificates (say, to avoid MitM attack). Here is my understanding. I think that U2F offers network service providers a method of device authentication and those who can trust the device vendor can use this method to augment their user authentication. Here is a picture, explaining the method. [ Network service provider: A ] --------------\ Trust ^ | | protocol for remote use of token | v v [ User: U ]===having a token T1 by [ Device Vendor: D ] ^ ^ | protocol for remote use of token | v | [ Network service provider: B ] --------------/ Trust Note that U2F itself is not user authentication. User authentication is composed at network service provider side by traditional username+passphrase AND the fact a user has the device (which can be made sure by U2F device authentication). In the design, the device is assumed to be shared among different network service providers. U2F is the protocol to offer remote crypto computation by network service providers. Users are... offering electric power to the device. Users help network service providers so that the U2F authentication can work effectively (say, by providing their fingerprint). In such a scheme, network service providers don't hesitate to send nonfree JavaScript to their users, because the purpose is doing remote use of the vendor's token (I don't say, it's user's token, even if user is a "holder" is the token). -- From wk at gnupg.org Mon Mar 6 15:41:12 2017 From: wk at gnupg.org (Werner Koch) Date: Mon, 06 Mar 2017 15:41:12 +0100 Subject: Problems with GPGME returning "Not Implemented" or "Configuration error" In-Reply-To: (Jeffrey Stedfast's message of "Mon, 27 Feb 2017 14:20:38 +0000") References: Message-ID: <87zigytqlz.fsf@wheatstone.g10code.de> On Mon, 27 Feb 2017 15:20, jestedfa at microsoft.com said: > I'm working on re-implementing GMime to use libgpgme (1.8.0 on Fedora > 25) instead of using my own custom logic for fork()ing/exec()ing gpg & Great, we like the use of the GPGME API. I guess GMime is not used by Evolution ;-) Which GnuPG and GPGME versions are you using? > For some reason, gpgme_op_sign() is returning GPG_ERR_NOT_IMPLEMENTED That can have several reasons. I can't tell without having a log. > while gpgme_op_encrypt() is returning "Configuration error". Does it work on the command line? I would suggested to put "disable-crl-checks" into gpgsm.conf or even "disable-dirmngr". If that works you need, you need to make sure that CRLs and intermediate certificates can be downloaded. That may require to configure LDAP access. >>From what I can deduce by scouring the web for information, it seems >>like NOT_IMPLEMENTED should never get returned unless I am using >>options that just haven't been implemented yet but that doesn't seem >>like it should be the case since I don't think I'm doing anything out >>of the ordinary. Reseting the context may also be a cause for this. > For encrypting, I am getting "Configuration error" which I'm also > confused about because I don't know what configuration options could > be causing this. Probably dirmngr.conf. See above. What you should do is to enable debugging: If you are using gnupg 2.1 you should put --8<---------------cut here---------------start------------->8--- log-file socket:// debug ipc verbose --8<---------------cut here---------------end--------------->8--- into {gpg-agent,gpgsm,dirmngr}.conf . With older versions use have to use this (also work with 2.1, though): --8<---------------cut here---------------start------------->8--- log-file socket:///home/USER/.gnupg/S.log debug 1024 verbose --8<---------------cut here---------------end--------------->8--- then fire up an xterm and run watchgnupg --time-only --force ~/.gnupg/S.log and you see in real time what's going on at the gnupg level. To debug run your program using GPGME_DEBUG=4:/tmp/gpgme.h: ./testpg. gpgme.log gives a pretty detailed listing. Feel free to forward it to me. If you use a level 7 you will get a complete I/O listing. > All I can think of is that perhaps there is some leftover state from gpgme_op_import() or gpgme_op_export_ext() that is breaking the gpgme_op_sign() when run at a later point? Possible. I don't think we have good tests for this. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From wk at gnupg.org Mon Mar 6 16:10:44 2017 From: wk at gnupg.org (Werner Koch) Date: Mon, 06 Mar 2017 16:10:44 +0100 Subject: How U2F works In-Reply-To: (Glenn Rempe's message of "Mon, 27 Feb 2017 16:28:25 -0800") References: <878tortdre.fsf@fsij.org> Message-ID: <87varmtp8r.fsf@wheatstone.g10code.de> On Tue, 28 Feb 2017 01:28, glenn at rempe.us said: > What though is the benefit of using gnupg key as the crypto behind the > client auth? Seems like you are more exposed by having a portable gpg It is up to the user where to store the key. For obvious reasons the user should use a token (e.g. gnuk or another OpenPGP smartcard, or one of the other supported X.509 smartcards). Frankly, I don't really understand the use case for U2F? Why not using plain user certificates which is supported by browser and servers for ages? Is that because the web frameworks don't have good support for this? An old argument against user certificates was the need to purchase a device or a certificates. Now U2F requires that you purchase a device anyway, thus this would void that argument. With OpenPGP a web service could ask for the user's public key during enrollment and sign that key with their key. The login procedure can then send a challenge, verify it and check that the key has been signed (OpenPGP key signature) by their key. That would be a decentralized system and only the enrollment needs to care about user data and such. The user could use the very same key (toke) for other services as well because other service providers can either add their own key signature or thus the key signature of another service provider. Well, backup is certainly an issue but one which can be solved - in particular when the tokens are produced by the service provider. The OpenPGP card spec provides secure messaging and a few other feature, which we once designed for a similar purpose: A service provider was able to update the user's cards over the net (time-based travel cards). Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From wk at gnupg.org Mon Mar 6 16:46:41 2017 From: wk at gnupg.org (Werner Koch) Date: Mon, 06 Mar 2017 16:46:41 +0100 Subject: powertop(8) Points at gpg-agent. In-Reply-To: <20170221095617.3E1281FE93@orac.inputplus.co.uk> (Ralph Corderoy's message of "Tue, 21 Feb 2017 09:56:17 +0000") References: <20170217135952.3402B212CE@orac.inputplus.co.uk> <8760k5nu1p.fsf@wheatstone.g10code.de> <20170220133206.0A8D92141D@orac.inputplus.co.uk> <20170221095617.3E1281FE93@orac.inputplus.co.uk> Message-ID: <87efyatnku.fsf@wheatstone.g10code.de> On Tue, 21 Feb 2017 10:56, ralph at inputplus.co.uk said: > I wonder if aiming for dead on the second is a good idea. If everything > did that then there might silence until the next second boundary, but > many cores would wake up to work for a short time. I had the same concern but the folks who suggested that said that this is the best strategy for short term jobs. Apparently cron et all work the same. I need to check why it is not anymore the full second, though. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From ralph at inputplus.co.uk Mon Mar 6 17:24:45 2017 From: ralph at inputplus.co.uk (Ralph Corderoy) Date: Mon, 06 Mar 2017 16:24:45 +0000 Subject: powertop(8) Points at gpg-agent. In-Reply-To: <87efyatnku.fsf@wheatstone.g10code.de> References: <20170217135952.3402B212CE@orac.inputplus.co.uk> <8760k5nu1p.fsf@wheatstone.g10code.de> <20170220133206.0A8D92141D@orac.inputplus.co.uk> <20170221095617.3E1281FE93@orac.inputplus.co.uk> <87efyatnku.fsf@wheatstone.g10code.de> Message-ID: <20170306162445.4CFFF1FE31@orac.inputplus.co.uk> Hi Werner, > > I wonder if aiming for dead on the second is a good idea. If > > everything did that then there might silence until the next second > > boundary, but many cores would wake up to work for a short time. > > I had the same concern but the folks who suggested that said that this > is the best strategy for short term jobs. Apparently cron et all work > the same. Here on Arch Linux, /usr/bin/crond is owned by cronie 1.5.1-1, and it sleeps for 60 s exactly, slowly creeping forwards. The sleep is sometimes interrupted by SIGCHLD, but that's very soon after it's started and the 59.xxx s remaining that its told is left becomes another 60 s sleep. $ sudo -i strace -tt -e nanosleep -p `pidof crond` strace: Process 303 attached 16:09:01.325441 nanosleep({tv_sec=60, tv_nsec=0}, 0x7fff5d22ac50) = 0 16:10:01.326133 nanosleep({tv_sec=60, tv_nsec=0}, 0x7fff5d22ac50) = 0 16:11:01.326724 nanosleep({tv_sec=60, tv_nsec=0}, 0x7fff5d22ac50) = 0 16:12:01.327254 nanosleep({tv_sec=60, tv_nsec=0}, 0x7fff5d22ac50) = 0 16:13:01.327842 nanosleep({tv_sec=60, tv_nsec=0}, 0x7fff5d22ac50) = 0 16:14:01.328426 nanosleep({tv_sec=60, tv_nsec=0}, 0x7fff5d22ac50) = 0 16:15:01.329013 nanosleep({tv_sec=60, tv_nsec=0}, 0x7fff5d22ac50) = 0 16:16:01.329637 nanosleep({tv_sec=60, tv_nsec=0}, 0x7fff5d22ac50) = 0 16:17:01.330289 nanosleep({tv_sec=60, tv_nsec=0}, 0x7fff5d22ac50) = 0 16:18:01.330832 nanosleep({tv_sec=60, tv_nsec=0}, 0x7fff5d22ac50) = 0 16:19:01.331389 nanosleep({tv_sec=60, tv_nsec=0}, 0x7fff5d22ac50) = 0 16:20:01.332925 nanosleep({tv_sec=60, tv_nsec=0}, {tv_sec=59, tv_nsec=732892671}) = ? ERESTART_RESTARTBLOCK (Interrupted by signal) 16:20:01.600374 --- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=27903, si_uid=0, si_status=0, si_utime=1, si_stime=0} --- 16:20:01.600779 nanosleep({tv_sec=60, tv_nsec=0}, 0x7fff5d22ac50) = 0 16:21:01.601394 nanosleep({tv_sec=60, tv_nsec=0}, Any thoughts on my other points in the earlier email https://lists.gnupg.org/pipermail/gnupg-users/2017-February/057745.html that talks about avoiding some of the wake ups altogether? -- Cheers, Ralph. https://plus.google.com/+RalphCorderoy From ndk.clanbo at gmail.com Mon Mar 6 19:23:26 2017 From: ndk.clanbo at gmail.com (NdK) Date: Mon, 6 Mar 2017 19:23:26 +0100 Subject: How U2F works In-Reply-To: <87varmtp8r.fsf@wheatstone.g10code.de> References: <878tortdre.fsf@fsij.org> <87varmtp8r.fsf@wheatstone.g10code.de> Message-ID: <2c310ce2-d2ad-6218-5db0-d7f43ff8b0b8@gmail.com> Il 06/03/2017 16:10, Werner Koch ha scritto: > An old argument against user certificates was the need to purchase a > device or a certificates. Now U2F requires that you purchase a device > anyway, thus this would void that argument. IIRC one of the selling points of U2F is that it should have been "anonymous": an attacker that compromises multiple servers shouldn't be able to determine if two users (on the two servers) are actually the same person (or even if two users of the same site share a single token). The only link would be the attestation certificate, but that should only be checked during enrollment and not stored anywhere (once the user is enrolled, the attestation cert is useless since only the site-specific pubkey is needed). With X509 (or GPG) certs the user's identity gets linked, for the joy of nosy orgs. @NIIBE : the sites don't send "proprietary JS" to the browser to access the token (needed code is public) but the browser must support U2F API. That's native in Chrome, but Firefox requires a plugin (and I don't know what's the status of other browsers). PS: it's not clear what happens when the attestation cert expires: does the token become useless for enrollment? PPS: the "attestation CA" could even be the GPG 'C' or 'S' key, that the server could check via WoT. That does not require 'C' or 'S' key to be on the token: the attestation certificate can be generated on an offline machine. BYtE, Diego. From gerd.von.egidy at intra2net.com Mon Mar 6 23:32:25 2017 From: gerd.von.egidy at intra2net.com (Gerd v. Egidy) Date: Mon, 06 Mar 2017 23:32:25 +0100 Subject: How U2F works In-Reply-To: <87varmtp8r.fsf@wheatstone.g10code.de> References: <878tortdre.fsf@fsij.org> <87varmtp8r.fsf@wheatstone.g10code.de> Message-ID: <2001383.tUnkEGPRVg@rdx.n.i2n> > Frankly, I don't really understand the use case for U2F? Why not using > plain user certificates which is supported by browser and servers for > ages? Is that because the web frameworks don't have good support for > this? I think this is because many people consider anything that is called a "certificate" complicated. Probably because in the past a lot of programs had poor or buggy support for it and they struggled with it. So they came up with a new brand name and standard. But I think they messed this up: when you want an attestated U2F device, there is no way to backup the private key or clone it to another U2F device. So whenever you sign up to a new service or website, you must have your primary and all backup U2F devices (each with it's own key) at hand to register them with the service. To have them at hand means I can't store them at a second secure location like a bank safe. Because I won't go to my bank safe just to be able to order at a new online store. Completely unpractical unless you restrict the usage just to a handful of key services. Or it is right back to "what was the name of your first pet" :( Kind regards, Gerd From gniibe at fsij.org Tue Mar 7 00:52:04 2017 From: gniibe at fsij.org (NIIBE Yutaka) Date: Tue, 07 Mar 2017 08:52:04 +0900 Subject: How U2F works In-Reply-To: <87varmtp8r.fsf@wheatstone.g10code.de> References: <878tortdre.fsf@fsij.org> <87varmtp8r.fsf@wheatstone.g10code.de> Message-ID: <87shmq3qvv.fsf@iwagami.gniibe.org> Werner Koch wrote: > Frankly, I don't really understand the use case for U2F? Why not using > plain user certificates which is supported by browser and servers for > ages? Is that because the web frameworks don't have good support for > this? Scalability, and some (or the) trust model which supports that. The common practice for (X.509) user certificates is they are issued by a specific network service provider, and it's useless for another network service provider. Users have to install each certificate issued by each network service provider. And this is not easy to manage such a thing. Ideally, we would have a good method to handle user certificates on client machines, and have a practice using X.509 user certificates by..., say, with "root CA"s. OpenPGP community would say, it could be done reliably in a way of distributed mechanism by OpenPGP certificates, right now. Right, technically, it's true. The question is: How about in practice? I think that user certificates (either, by X.509 or by OpenPGP) won't work well than something like U2F. I think that here, U2F offers a "solution", in clever and practical way. Well, let me explain from another angle. I live in a small town. In some cases, I buy things based on mutual trust, directly or indirectly. I use cash (or even credit card in some specific cases), but shop owners are basically trust me. We use money, Japanese Yen. But in a few cases, it is not needed in that form. For our own rice (most important food), I don't have to pay in the form of money. I live in such a town, intentionally. I used to live in Tokyo for many years. Shop onwers trust some credit card service company and Japan Bank as an issuer of paper money. They don't necessarily care about me or anyone, who is buying their products/services, as long as they can get paid. Money scales. Credit card scales. That's because they don't require direct mutual trust between a shop and a stranger who visits a shop. All that shop owner needs is... to trust money. That's my understanding. I think that most important factor is not users, here (it is related, though). Using U2F might be easier for a network service provider, when other network service providers have introduced such a feature in their service already. For an engineer or an administrator around web services, it would be just "easy", like installing a few modules, probably, while preparing X.509 user certificates requires complex and difficult things. >From an engineer who eats rice mainly. :-) -- From billdangerous at gmail.com Tue Mar 7 09:40:50 2017 From: billdangerous at gmail.com (Bill Dangerous) Date: Tue, 7 Mar 2017 09:40:50 +0100 Subject: From Masterkey to subkey Message-ID: Hi, Sometimes ago, I generated my master key without following the state of the art of the gpg, meaning using an offline master key, and only sign and enrypt with subkeys. I would like today to correct my mistake without loosing my key, so I need to transform this master key into a subkey. I followed this tutorial http://security.stackexchange.com/questions/32935/migrating-gpg-master-keys-as-subkeys-to-new-master-key, based on http://atom.smasher.org/gpg/gpg-migrate.txt. It works well, except for subkey usage. Indeed, my old master key which is now a subkey, has all the flags (SCEA), and I don't know how to change that. I would like to limit flags to SE. I tried to hack the code ( https://lists.gnupg.org/pipermail/gnupg-users/2009-May/036505.html), but it works only for master key flags and not subkey flags. I would like first to be sure that this process of migrating a master key to subkey is reliable ? Am I not breaking something, that I am going to regret ? Is there a way (even if hacking gpg code is needed), to change those subkey flags ? Regards, Bill -------------- next part -------------- An HTML attachment was scrubbed... URL: From rjh at sixdemonbag.org Tue Mar 7 15:08:39 2017 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Tue, 7 Mar 2017 09:08:39 -0500 Subject: From Masterkey to subkey In-Reply-To: References: Message-ID: <98ddb399-a181-a59b-aa93-5ec9553879bc@sixdemonbag.org> > Sometimes ago, I generated my master key without following the state of > the art of the gpg, meaning using an offline master key, and only sign > and enrypt with subkeys. Whoever told you this was badly misinformed. While you *can* do this, it is by no means a general recommendation. The only general recommendation we give is "unless you know what you're doing and why, stick with the defaults." You didn't make a mistake. If you have a need for an offline master key (if not having one will cause your local security policy to fail), then by all means do it. But otherwise, think twice: you're introducing a lot of additional complexity for not very much benefit. From peter at digitalbrains.com Tue Mar 7 15:26:47 2017 From: peter at digitalbrains.com (Peter Lebbing) Date: Tue, 7 Mar 2017 15:26:47 +0100 Subject: From Masterkey to subkey In-Reply-To: References: Message-ID: <5a226091-c2f2-8754-4a4f-d30df3cb2516@digitalbrains.com> On 07/03/17 09:40, Bill Dangerous wrote: > I would like today to correct my mistake without loosing my key, so I > need to transform this master key into a subkey. With GnuPG 2.1, I think this is easily doable. Which version of GnuPG are you using? With the older branches, this is quite difficult. I do however wonder why you want to do this in the first place. Your primary key should not have the Encrypt ability in the first place, and signature keys are easily exchanged without affecting old signatures. Is this about the certifications you already have on your old key? You could publish a key transition statement and ask people to re-certify. It's not as nice as just having the old certifications work, but that might not be desirable for other reasons. I doubt you would benefit from earlier certifications if you started issuing signatures with your new subkey that was formerly a primary. I think behaviour might be unreliable. How does the recipient GnuPG know whether it was issued by your old primary, in its capacity of the old primary, or by your new subkey? There is nothing in a signature that indicates this[1]. The GnuPG installation of one person might decide it is a signature by the old primary, and award validity to it based on certifications on the old key. A different GnuPG installation might decide it was the subkey of the new certificate that issued the signature, and use the validity of the new certificate. People having both keys might see either behaviour, and might see a new behaviour when they change something about their public keyring. Oh, and before you benefit from keeping your primary offline, you'd have to revoke the old key. Any GnuPG installation that concludes the signature is by the old primary will immediately flag the signature as BAD because it was issued after the key was revoked. This makes it even worse. In fact, this realization tells me another thing: you can't benefit both from earlier certifications and from having an offline master key, it is either-or. > Indeed, my old master key which is now a > subkey, has all the flags (SCEA), and I don't know how to change that. I > would like to limit flags to SE. Both look wrong to me. Why do you want to have the Encrypt capability on that key, do you have that on your old primary? It is considered bad practice to use the same key material for both encryption and signatures, since it opens the door to some sneaky stuff that is easily avoided by not using the same key for both. I'm not saying it is readily exploitable and I'm not saying it is not. > I would like first to be sure that this process of migrating a master > key to subkey is reliable ? Am I not breaking something, that I am going > to regret ? It sounds like a pretty bad idea to me. I expect recipients to see breaking signatures, and a primary key with the E capability should be retired anyway. Don't throw the key away! You'll still need it to decrypt things that were previously encrypted to it. But don't use it anymore. > Is there a way (even if hacking gpg code is needed), to change those > subkey flags ? Yes. Let's deal with the rest first. HTH, Peter. [1] There is "Signer's User ID" which could theoretically be used to differentiate. But this is not widely used, and I doubt it would work in practice. The purpose is to differentiate between different user id's on one certificate, not to differentiate between certificates. -- I use the GNU Privacy Guard (GnuPG) in combination with Enigmail. You can send me encrypted mail if you want some privacy. My key is available at -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From andrewg at andrewg.com Tue Mar 7 15:29:40 2017 From: andrewg at andrewg.com (Andrew Gallagher) Date: Tue, 7 Mar 2017 14:29:40 +0000 Subject: From Masterkey to subkey In-Reply-To: References: Message-ID: <7DA3BABA-E1BA-4360-BC98-2FC5A403E412@andrewg.com> > On 7 Mar 2017, at 08:40, Bill Dangerous wrote: > > Indeed, my old master key which is now a subkey, has all the flags (SCEA), and I don't know how to change that. I would like to limit flags to SE I would strongly recommend against that. I would create completely new subkeys, including (especially!) an E subkey with no other capabilities, and expire that weird subkey ASAP. You'll still be able to decrypt any messages encrypted to it, but it won't be used for any new messages. A From peter at digitalbrains.com Tue Mar 7 15:31:10 2017 From: peter at digitalbrains.com (Peter Lebbing) Date: Tue, 7 Mar 2017 15:31:10 +0100 Subject: From Masterkey to subkey In-Reply-To: <98ddb399-a181-a59b-aa93-5ec9553879bc@sixdemonbag.org> References: <98ddb399-a181-a59b-aa93-5ec9553879bc@sixdemonbag.org> Message-ID: On 07/03/17 15:08, Robert J. Hansen wrote: > Whoever told you this was badly misinformed. While you *can* do this, > it is by no means a general recommendation. Right, yes, and that :-). I wholeheartedly agree, but kinda went past that in my response. I'm more worried about the possibility of your old primary having "E" based on what you (Bill) said, which would go against the "state of the art" and "general recommendations", IMO. HTH, Peter. -- I use the GNU Privacy Guard (GnuPG) in combination with Enigmail. You can send me encrypted mail if you want some privacy. My key is available at -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From wk at gnupg.org Tue Mar 7 19:21:25 2017 From: wk at gnupg.org (Werner Koch) Date: Tue, 07 Mar 2017 19:21:25 +0100 Subject: From Masterkey to subkey In-Reply-To: (Bill Dangerous's message of "Tue, 7 Mar 2017 09:40:50 +0100") References: Message-ID: <87h935osm2.fsf@wheatstone.g10code.de> On Tue, 7 Mar 2017 09:40, billdangerous at gmail.com said: > I would like first to be sure that this process of migrating a master key > to subkey is reliable ? Am I not breaking something, that I am going to > regret ? Please see the other comments. > Is there a way (even if hacking gpg code is needed), to change those subkey > flags ? With 2.1 it is easy: gpg --edit-key THEKEY gpg> key N gpg> change-usage and follow the prompt. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From tlikonen at iki.fi Tue Mar 7 21:03:33 2017 From: tlikonen at iki.fi (Teemu Likonen) Date: Tue, 07 Mar 2017 22:03:33 +0200 Subject: From Masterkey to subkey In-Reply-To: <87h935osm2.fsf@wheatstone.g10code.de> (Werner Koch's message of "Tue, 07 Mar 2017 19:21:25 +0100") References: <87h935osm2.fsf@wheatstone.g10code.de> Message-ID: <87efy8zwfe.fsf@iki.fi> Werner Koch [2017-03-07 19:21:25+01] wrote: > On Tue, 7 Mar 2017 09:40, billdangerous at gmail.com said: >> Is there a way (even if hacking gpg code is needed), to change those >> subkey flags ? > > With 2.1 it is easy: > > gpg --edit-key THEKEY > gpg> key N > gpg> change-usage > > and follow the prompt. Interesting. It seems that the feature is not documented. I tested version 2.1.18 in Debian testing and neither the man page nor --edit-key's "help" command tells anything about the feature. -- /// Teemu Likonen - .-.. // // PGP: 4E10 55DC 84E9 DFF6 13D7 8557 719D 69D3 2453 9450 /// -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 454 bytes Desc: not available URL: From wk at gnupg.org Tue Mar 7 22:04:28 2017 From: wk at gnupg.org (Werner Koch) Date: Tue, 07 Mar 2017 22:04:28 +0100 Subject: From Masterkey to subkey In-Reply-To: <87efy8zwfe.fsf@iki.fi> (Teemu Likonen's message of "Tue, 07 Mar 2017 22:03:33 +0200") References: <87h935osm2.fsf@wheatstone.g10code.de> <87efy8zwfe.fsf@iki.fi> Message-ID: <87wpc0ol2b.fsf@wheatstone.g10code.de> On Tue, 7 Mar 2017 21:03, tlikonen at iki.fi said: > Interesting. It seems that the feature is not documented. I tested > version 2.1.18 in Debian testing and neither the man page nor > --edit-key's "help" command tells anything about the feature. One of the hidden commands to be revealed in case they are needed (think: bug in gpg creating keys with wrong capabilities) ;-) Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From jestedfa at microsoft.com Wed Mar 8 00:57:37 2017 From: jestedfa at microsoft.com (Jeffrey Stedfast) Date: Tue, 7 Mar 2017 23:57:37 +0000 Subject: Problems with GPGME returning "Not Implemented" or "Configuration error" In-Reply-To: <87zigytqlz.fsf@wheatstone.g10code.de> References: <87zigytqlz.fsf@wheatstone.g10code.de> Message-ID: <021A3DFB-9C53-4A96-91A3-8BF69AB7880C@microsoft.com> Gah I hate Outlook which makes replying inline impossible :\ Outlook will indent but not add ?> ? to quoted lines, so be aware of that as you read this email ( On 3/6/17, 9:41 AM, "Werner Koch" wrote: On Mon, 27 Feb 2017 15:20, jestedfa at microsoft.com said: > I'm working on re-implementing GMime to use libgpgme (1.8.0 on Fedora > 25) instead of using my own custom logic for fork()ing/exec()ing gpg & Great, we like the use of the GPGME API. I guess GMime is not used by Evolution ;-) Yea, I haven?t been involved in Evolution development in ~10+ years at this point? I think Evolution uses libNSS (Mozilla libs) for S/MIME, but for GMime, I?d like to use gpgsm instead. Which GnuPG and GPGME versions are you using? I?m using gnupg 2.1.13 and gpgme 1.8.0 > For some reason, gpgme_op_sign() is returning GPG_ERR_NOT_IMPLEMENTED That can have several reasons. I can't tell without having a log. I?ll see what I can do about getting you that log? > while gpgme_op_encrypt() is returning "Configuration error". Does it work on the command line? I would suggested to put "disable-crl-checks" into gpgsm.conf or even "disable-dirmngr". If that works you need, you need to make sure that CRLs and intermediate certificates can be downloaded. That may require to configure LDAP access. Adding ?disable-crl-checks? to my gpgsm.conf fixed encryption. That leaves signing and decrypting as both failing with ?Not Implemented?. It?s an improvement! >>From what I can deduce by scouring the web for information, it seems >>like NOT_IMPLEMENTED should never get returned unless I am using >>options that just haven't been implemented yet but that doesn't seem >>like it should be the case since I don't think I'm doing anything out >>of the ordinary. Reseting the context may also be a cause for this. Sadly, resetting the context did not help ( > For encrypting, I am getting "Configuration error" which I'm also > confused about because I don't know what configuration options could > be causing this. Probably dirmngr.conf. See above. What you should do is to enable debugging: If you are using gnupg 2.1 you should put --8<---------------cut here---------------start------------->8--- log-file socket:// debug ipc verbose --8<---------------cut here---------------end--------------->8--- into {gpg-agent,gpgsm,dirmngr}.conf . With older versions use have to use this (also work with 2.1, though): --8<---------------cut here---------------start------------->8--- log-file socket:///home/USER/.gnupg/S.log debug 1024 verbose --8<---------------cut here---------------end--------------->8--- then fire up an xterm and run watchgnupg --time-only --force ~/.gnupg/S.log You can see this log here: https://gist.github.com/jstedfast/38ab7fe65f0c769ba31bd5a807e2f374 and you see in real time what's going on at the gnupg level. To debug run your program using GPGME_DEBUG=4:/tmp/gpgme.h: ./testpg. gpgme.log gives a pretty detailed listing. Feel free to forward it to me. If you use a level 7 you will get a complete I/O listing. That?s really useful, thanks! You can see the gpgme log here: https://gist.github.com/jstedfast/c9fa718ef524a73de02daacc142beccc I spotted the fact that I was (incorrectly) using gpgme_op_decrypt_verify() when I think I should be using gpgme_op_decrypt(), so I fixed that but I still get ?Not Implemented?. I added a comment to the end of that gist to provide the new snippet that gpgme.log contained after the ?fix?. > All I can think of is that perhaps there is some leftover state from gpgme_op_import() or gpgme_op_export_ext() that is breaking the gpgme_op_sign() when run at a later point? Possible. I don't think we have good tests for this. Thanks so much for your help, Jeff From wk at gnupg.org Wed Mar 8 10:51:06 2017 From: wk at gnupg.org (Werner Koch) Date: Wed, 08 Mar 2017 10:51:06 +0100 Subject: Expanding web-of-trust with subkey In-Reply-To: <8737feky15.fsf@iki.fi> (Teemu Likonen's message of "Thu, 16 Feb 2017 16:31:18 +0200") References: <87bmu3fl7o.fsf@iki.fi> <8737ffl2bu.fsf@alice.fifthhorseman.net> <8737feky15.fsf@iki.fi> Message-ID: <874lz4nlkl.fsf@wheatstone.g10code.de> On Thu, 16 Feb 2017 15:31, tlikonen at iki.fi said: >> please be aware that if you switch from "trust-model direct" to >> "trust-model tofu+pgp", then your previous assignments of "trust" will >> transform into indications of "ownertrust". > > That has been my assumption. Thanks for verifying. I'll add a note to the an page. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From longsi0008 at gmail.com Thu Mar 9 19:44:19 2017 From: longsi0008 at gmail.com (Long Si) Date: Fri, 10 Mar 2017 02:44:19 +0800 Subject: private-keys-v1.d Message-ID: Hi Before migrating to a new system, I exported my GPG secret keys and then imported them. Both "gpg -k" and "gpg -K" shows both the public and private keys are imported properly. However, I note my ".gnupg/private-keys-v1.d" directory is empty, and I am unable to sign my emails with Evolution client, it kept reporting "secret keys not found". Fortunately, I kept a copy of my old directory and copied the two (.key) files over and now things are okay. Thus, I like to ask how do I generate the (.key) files from my exported, armoured text file created by "gpg --export-secret-keys"? Isn't creating a backup of my secret key enough to recreate the rest of the necessary files? Regards From wk at gnupg.org Fri Mar 10 10:33:21 2017 From: wk at gnupg.org (Werner Koch) Date: Fri, 10 Mar 2017 10:33:21 +0100 Subject: Problems with GPGME returning "Not Implemented" or "Configuration error" In-Reply-To: <021A3DFB-9C53-4A96-91A3-8BF69AB7880C@microsoft.com> (Jeffrey Stedfast's message of "Tue, 7 Mar 2017 23:57:37 +0000") References: <87zigytqlz.fsf@wheatstone.g10code.de> <021A3DFB-9C53-4A96-91A3-8BF69AB7880C@microsoft.com> Message-ID: <878todease.fsf@wheatstone.g10code.de> On Wed, 8 Mar 2017 00:57, jestedfa at microsoft.com said: > I spotted the fact that I was (incorrectly) using > gpgme_op_decrypt_verify() when I think I should be using > gpgme_op_decrypt(), so I fixed that but I still get ?Not Implemented?. The reason why it shows "Not implemented" is that you used gpgme_set_passphrase_cb () with GPGME_PROTOCOL_CMS. gpgsm does not support a passphrase callback in the same way as gpg does. In particular gpgme sets up a command line edit handler to push the passphrase via the callback to to gpg. gpgsm has no --command-fd option but only a --passphrase-fd option which can be used with --pinentry-mode=loopback. Right, this should be fixed. I think we already have a feature request for this. As a workaround, you should gpgme_set_passphrase_cb (ctx, NULL, NULL); after switching to GPGME_PROTOCOL_CMS. This will then use the pinentry and thus you need to provide a dummy pinentry for your test suite (or use no passphrase at all). Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From Alexander.Strobel at giepa.de Fri Mar 10 10:26:06 2017 From: Alexander.Strobel at giepa.de (Alexander Strobel) Date: Fri, 10 Mar 2017 10:26:06 +0100 Subject: Error searching key from keyserver in gpg 2.1.19 Message-ID: I have installed GnuPG 2.1.19 on my Windows 8.1 (x64) machine. When I search for a key on a keyserver it shows this error: gpg: error searching keyserver: Input/output error gpg: Suche auf dem Schl?sselserver fehlgeschlagen: Input/output error My commandline: gpg --keyserver hkp://subset.pool.sks-keyservers.net --search-keys 0xF3102BE7 When I do this with GnuPG 1.4.21 everything is ok. What's the problem here? Best regards Alex Strobel www.gpg4o.com From Pankaj.Chaurasia at smartusys.com Fri Mar 10 10:23:33 2017 From: Pankaj.Chaurasia at smartusys.com (Pankaj Kumar. Chaurasia) Date: Fri, 10 Mar 2017 09:23:33 +0000 Subject: Help Needed: I am able to decrypt file when I run package manually but when I run through sql sever agent, it is not decrypting. Message-ID: Hello Gnupg Users, I am writing this mail regarding the issue facing to decrypt file through my SSIS Package. Below is the command I am using: gpg2.exe --batch --yes --status-fd 2 --passphrase-fd 0 --armor --output E:\File.csv --decrypt E:\File.pgp When I run my SSIS package manually through visual studio it is decrypting the file properly. When I deploying the package on the same machine it is not decrypting. After spending to much time I come to know that the reason behind this is, I have imported the public key using command line, so it is imported for my user as I login on that machine with my windows user. But SQL Server agent job runs with MSSQL Agent Service account so I need to import the key for that service account. Could you guys please let me know how to import the public key for that account as I cannot login with that Service account. Thanks in Advance. Thanks & Regards, Pankaj K Chaurasia Sr. Database Developer Smart Utility Systems 0120-4208528 (O) | +91- 8109510013 (M) | +91- 9406929510 (M) pankaj.chaurasia at smartusys.com | www.smartusys.com [https://www.smartusys.com/emails/ISGW/signature/ISGW_EmailBanner.png] [facebook][linkedin] [twitter] [google] This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. P Please consider the environment before printing this email. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 1147 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 1240 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 1270 bytes Desc: image003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 1669 bytes Desc: image004.png URL: From jestedfa at microsoft.com Fri Mar 10 12:48:47 2017 From: jestedfa at microsoft.com (Jeffrey Stedfast) Date: Fri, 10 Mar 2017 11:48:47 +0000 Subject: Problems with GPGME returning "Not Implemented" or "Configuration error" In-Reply-To: <878todease.fsf@wheatstone.g10code.de> References: <87zigytqlz.fsf@wheatstone.g10code.de> <021A3DFB-9C53-4A96-91A3-8BF69AB7880C@microsoft.com> <878todease.fsf@wheatstone.g10code.de> Message-ID: Aha! This makes a lot of sense. Thanks Werner! Jeff > -----Original Message----- > From: Werner Koch [mailto:wk at gnupg.org] > Sent: Friday, March 10, 2017 4:33 AM > To: Jeffrey Stedfast > Cc: gnupg-users at gnupg.org > Subject: Re: Problems with GPGME returning "Not Implemented" or > "Configuration error" > > On Wed, 8 Mar 2017 00:57, jestedfa at microsoft.com said: > > > I spotted the fact that I was (incorrectly) using > > gpgme_op_decrypt_verify() when I think I should be using > > gpgme_op_decrypt(), so I fixed that but I still get ?Not Implemented?. > > The reason why it shows "Not implemented" is that you used > gpgme_set_passphrase_cb () with GPGME_PROTOCOL_CMS. gpgsm does > not support a passphrase callback in the same way as gpg does. In particular > gpgme sets up a command line edit handler to push the passphrase via the > callback to to gpg. gpgsm has no --command-fd option but only a -- > passphrase-fd option which can be used with --pinentry-mode=loopback. > > Right, this should be fixed. I think we already have a feature request for this. > > As a workaround, you should > > gpgme_set_passphrase_cb (ctx, NULL, NULL); > > after switching to GPGME_PROTOCOL_CMS. This will then use the pinentry > and thus you need to provide a dummy pinentry for your test suite (or use > no passphrase at all). > > > Shalom-Salam, > > Werner > > -- > Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. From marcel.wagner at gmx.de Fri Mar 10 23:34:14 2017 From: marcel.wagner at gmx.de (Marcel Wagner) Date: Fri, 10 Mar 2017 23:34:14 +0100 Subject: Is the header file gpgme.h complete? Message-ID: I try to generate a language binding for the gpgme library from the gpgme.h header file. The generator creates a binding from the header file, but it seems that some functions are missing. For example the context functions are missing. I checked the gpgme.h file and with my old C/C++ know how, it seems there are forward declarations, for example gpgme_context, but the struct is never defined? I looked at the source code of the gpgme lib and find this struct in a context.h header file, but this is not included in gpgme.h? My question is now, is the gpgme.h file complete? Or is there something missing? Thanks for your help. Regards, Marcel Wagner From wk at gnupg.org Sat Mar 11 12:38:38 2017 From: wk at gnupg.org (Werner Koch) Date: Sat, 11 Mar 2017 12:38:38 +0100 Subject: Is the header file gpgme.h complete? In-Reply-To: (Marcel Wagner's message of "Fri, 10 Mar 2017 23:34:14 +0100") References: Message-ID: <871su4cabl.fsf@wheatstone.g10code.de> Hi! On Fri, 10 Mar 2017 23:34, marcel.wagner at gmx.de said: > lib and find this struct in a context.h header file, but this is not > included in gpgme.h? My question is now, is the gpgme.h file complete? Yes it is complete. Anonymous structures are the standard way in C to hide implementation details. Obviously you can only have a pointer to such an object and that is why the corresponding typedef defines a pointer to the structure. For a typedef it is sufficient to have just the name of the structure (i.e. an anonymous structure). Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From wk at gnupg.org Sat Mar 11 12:40:09 2017 From: wk at gnupg.org (Werner Koch) Date: Sat, 11 Mar 2017 12:40:09 +0100 Subject: Error searching key from keyserver in gpg 2.1.19 In-Reply-To: (Alexander Strobel's message of "Fri, 10 Mar 2017 10:26:06 +0100") References: Message-ID: <87wpbwavom.fsf@wheatstone.g10code.de> On Fri, 10 Mar 2017 10:26, Alexander.Strobel at giepa.de said: > What's the problem here? Please add verbose debug network,dns,ipc And a log file option to dirmngr.conf and check the log. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From jestedfa at microsoft.com Sat Mar 11 15:02:17 2017 From: jestedfa at microsoft.com (Jeffrey Stedfast) Date: Sat, 11 Mar 2017 14:02:17 +0000 Subject: Test mail from Outlook Message-ID: <43387B6C-C35B-4448-8B55-35763D94CAC4@microsoft.com> Just a simple test message as asked by Werner to test something? Jeff From wk at gnupg.org Sat Mar 11 18:27:25 2017 From: wk at gnupg.org (Werner Koch) Date: Sat, 11 Mar 2017 18:27:25 +0100 Subject: ADMIN: Some mail addresses are now rewritten (was: Test mail from Outlook) In-Reply-To: <43387B6C-C35B-4448-8B55-35763D94CAC4@microsoft.com> (Jeffrey Stedfast via Gnupg-users's message of "Sat, 11 Mar 2017 14:02:17 +0000") References: <43387B6C-C35B-4448-8B55-35763D94CAC4@microsoft.com> Message-ID: <87varf911e.fsf@wheatstone.g10code.de> Hi! You may have noted that the From address has been rewritten to show the list address instead of your address. In addition a reply-to header has been set so that your address is also known. The reason for this is that some mail sites now have a DMARC reject policy which leads to a bounce for all subscribers whose mail provider honors this DMARC policy - for example gmail. After a few bounces message delivery to those subscribers will blocked by our Mailman. I have meanwhile unblocked all those addresses but the mails since Thursday or Friday have not been delivered to the affected accounts. The mitigation is to either use the list address as From: address or a modify the From: address to make it invalid (e.g. append the reserved domain "invalid"). Mailman offers the first option and that is what is now in use for every poster which an address where a reject policy is is advertised. The problem with this rewriting is that it breaks quoting. For example here is how I would have replied to Jeff's test mail: On Sat, 11 Mar 2017 15:02, gnupg-users at gnupg.org said: > Just a simple test message as asked by Werner to test something? Thank you. Thus I think marking the address invalid would have been a better choice for Mailman - but there is no option for this yet. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From jhs at berklix.com Sun Mar 12 12:44:10 2017 From: jhs at berklix.com (Julian H. Stacey) Date: Sun, 12 Mar 2017 12:44:10 +0100 Subject: Test mail from Outlook In-Reply-To: Your message "Sat, 11 Mar 2017 14:02:17 +0000." <43387B6C-C35B-4448-8B55-35763D94CAC4@microsoft.com> Message-ID: <201703121144.v2CBiAGn074894@fire.js.berklix.net> > Just a simple test message as asked by Werner to test something??? List owner[s] could ask for test@ lists to be added on domains: http://lists.gnupg.org/mailman/listinfo/ # gnupg-users at gnupg.org https://mail.python.org/mailman/listinfo/ # mailman-users at python.org Examples of domains with test lists: https://lists.freebsd.org/mailman/listinfo/freebsd-test http://mailman.berklix.org/mailman/listinfo/test Cheers, Julian -- Julian Stacey, BSD Linux Unix Sys Eng Consultant Munich Reply below, Prefix '> '. Plain text, No .doc, base64, HTML, quoted-printable. http://berklix.eu/brexit/#stolen_votes http://berklix.eu/brexit/#eu_passports From rjh at sixdemonbag.org Sun Mar 12 17:36:17 2017 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Sun, 12 Mar 2017 12:36:17 -0400 Subject: Interleaving issue Message-ID: <1024bda4-f796-788f-1ecd-b66784dbed6f@sixdemonbag.org> This is a bit odd: ===== quorra:~ rjh$ gpg --check-sig b44427c7 pub rsa3072/1DCBDC01B44427C7 2015-07-16 [SC] CC11BE7CBBED77B120F37B011DCBDC01B44427C7 uid [ultimate] Robert J. Hansen sig!3 1DCBDC01B44427C7 2016-07-02 Robert J. Hansen sig! 23806BE5D6B98E10 2015-07-16 Robert J. Hansen sig!3 D037CE8EEFA13249 2015-07-17 Phil Stracchino sig!3 DB1187B9DD5F693B 2015-07-18 Patrick Brunschwig sig!3 1DCBDC01B44427C7 2015-07-16 Robert J. Hansen sig!3 4D1E900E14C1CC04 2017-02-18 Phil Pennock uid [ultimate] Robert J. Hansen sig!3 1DCBDC01B44427C7 2016-07-02 Robert J. Hansen sig!3 4D1E900E14C1CC04 2017-02-18 Phil Pennock uid [ultimate] Robert J. Hansen sig!3 1DCBDC01B44427C7 2015-07-16 Robert J. Hansen sig! 23806BE5D6B98E10 2015-07-16 Robert J. Hansen sig!3 D037CE8EEFA13249 2015-07-17 Phil Stracchino sig!3 DB1187B9DD5F693B 2015-07-18 Patrick Brunschwig sig!3 4D1E900E14C1CC04 2017-02-18 Phil Pennock sub rsa3072/DC0F82625FA6AADE 2015-07-16 [E] sig! 1DCBDC01B44427C7 2015-07-16 Robert J. Hansen ===== Let me draw attention to: ===== quorra:~ rjh$ gpg --check-sig b44427c7 ... sig!3 1DCBDC01B44427C7 2015-07-16 Robert J. Hansen ... ===== It would appear GnuPG is interleaving outputs. This is on a macOS Sierra system with GnuPG 2.1.19. It's reproducible, too. From antony at blazrsoft.com Sun Mar 12 18:09:28 2017 From: antony at blazrsoft.com (antony at blazrsoft.com) Date: Sun, 12 Mar 2017 13:09:28 -0400 Subject: ADMIN: Some mail addresses are now rewritten (was: Test mail from Outlook) In-Reply-To: <87varf911e.fsf@wheatstone.g10code.de> References: <43387B6C-C35B-4448-8B55-35763D94CAC4@microsoft.com> <87varf911e.fsf@wheatstone.g10code.de> Message-ID: <1545682D-44BD-4812-BB82-D98FEF292187@blazrsoft.com> On March 11, 2017 12:27:25 PM EST, Werner Koch wrote: >The reason for this is that some mail sites now have a DMARC reject >policy which leads to a bounce for all subscribers whose mail provider >honors this DMARC policy - for example gmail. After a few bounces >message delivery to those subscribers will blocked by our Mailman. I noticed I was having issues with mail from mailing lists when I specified a DMARC reject policy for my domain, so I ended up changing it to unspecified for the time being to allow the receiver to decide how to deal with a DMARC failure. Not ideal, but DMARC (and DKIM signing for that matter) and mailing lists don't play nice together. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. From Alexander.Strobel at giepa.de Mon Mar 13 09:48:08 2017 From: Alexander.Strobel at giepa.de (Alexander Strobel) Date: Mon, 13 Mar 2017 09:48:08 +0100 Subject: [Solved] Re: Error searching key from keyserver in gpg 2.1.19 In-Reply-To: <87wpbwavom.fsf@wheatstone.g10code.de> References: <87wpbwavom.fsf@wheatstone.g10code.de> Message-ID: Am 11.03.2017 um 12:40 schrieb Werner Koch: > On Fri, 10 Mar 2017 10:26, Alexander.Strobel at giepa.de said: > >> What's the problem here? > > [Troubleshooting advisory] D'oh The problem was sitting before the monitor. GnuPG 2.1 was blocked by my firewall. GnuPG returns the key from "subset.pool.sks-keyservers.net" and "pool.sks-keyservers.net". Thank you for your help! Best regards Alex Strobel -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From ryru at addere.ch Mon Mar 13 13:47:33 2017 From: ryru at addere.ch (Ryru) Date: Mon, 13 Mar 2017 13:47:33 +0100 Subject: Security doubts on 3DES default Message-ID: <4960a07f-b61a-4d43-9baa-0075ef2e3230@addere.ch> Hello List I'm new to this list and joined because I have some security doubts regarding encryption preferences (setpref/showpref). According to the gpg2 man page, 3DES is added always as kind of least common denominator: 8<--- When setting preferences, you should list the algorithms in the order which you'd like to see them used by someone else when encrypting a message to your key. If you don't include 3DES, it will be automatically added at the end. Note that there are many factors that go into choosing an algorithm (for example, your key may not be the only recipient), and so the remote OpenPGP application being used to send to you may or may not follow your exact chosen order for a given message. It will, however, only choose an algorithm that is present on the preference list of every recipient key. See also the INTEROPERABILITY WITH OTHER OPENPGP PROGRAMS section below. --->8 In my opinion this design decision can lead to serious security troubles. If someone, knowingly or not, removed all his/her symmetric encryption algorithms in his/her public key, our conversation would only be 3DES encrypted. In a situation in which there are several recipients, e.g. a encrypted mailing list, one participating public key/person can downgrade the whole encrypted conversation to every recipient to 3DES instead of lets say AES256. I think the same goes for the hashing algorithm SHA1. Is my understanding correct or do I miss an important fact? What are your thoughts about this behaviour? Wouldn't it be great to raise the minimum encryption and hashing level to a more secure cipher? Thanks in advance and best regards Pascal From kristian.fiskerstrand at sumptuouscapital.com Mon Mar 13 16:15:18 2017 From: kristian.fiskerstrand at sumptuouscapital.com (Kristian Fiskerstrand) Date: Mon, 13 Mar 2017 16:15:18 +0100 Subject: Security doubts on 3DES default In-Reply-To: <4960a07f-b61a-4d43-9baa-0075ef2e3230@addere.ch> References: <4960a07f-b61a-4d43-9baa-0075ef2e3230@addere.ch> Message-ID: On 03/13/2017 01:47 PM, Ryru wrote: > Is my understanding correct or do I miss an important fact? What are > your thoughts about this behaviour? See section 13.2 of RFC4880, fyi the behavior changes in the context of RFC6637. My thoughts; concerns about 3DES are premature. The focus on algorithms in general likely so, the likelihood of operational security being the issue is far greater -- ---------------------------- Kristian Fiskerstrand Blog: https://blog.sumptuouscapital.com Twitter: @krifisk ---------------------------- Public OpenPGP keyblock at hkp://pool.sks-keyservers.net fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 ---------------------------- Qui audet vincit Who dares wins -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From rjh at sixdemonbag.org Mon Mar 13 16:17:07 2017 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Mon, 13 Mar 2017 11:17:07 -0400 Subject: Security doubts on 3DES default In-Reply-To: <4960a07f-b61a-4d43-9baa-0075ef2e3230@addere.ch> References: <4960a07f-b61a-4d43-9baa-0075ef2e3230@addere.ch> Message-ID: <024101d29c0c$e1b127f0$a51377d0$@sixdemonbag.org> > According to the gpg2 man page, 3DES is added always as kind of least > common denominator: This is required behavior per RFC4880. Your concern should be addressed to the IETF OpenPGP working group, not to GnuPG. > In my opinion this design decision can lead to serious security troubles. If > someone, knowingly or not, removed all his/her symmetric encryption > algorithms in his/her public key, our conversation would only be 3DES > encrypted. There is no security risk with 3DES unless you (foolishly) choose to encrypt vast quantities of data (multiple gigabytes) with the same key. RFC4880 requires 3DES be used with three independent subkeys, giving it a technical keyspace of 192 bits, the same as AES192. However, 24 of those bits are used for parity and contribute nothing to the security of the system, meaning it comes in at 168 bits of effective key. This is a keyspace about a trillion times larger than AES128's. There are a couple of *theoretical* attacks on 3DES that reduce it to about a "mere" 112 bits (still unassailable, but less strong than we'd like). The best known attack requires a billion known plaintexts and 100,000,000,000,000,000 gigabytes of RAM. 3DES is even somewhat resistant to quantum computation, as a 168-bit keyspace is still an 84-bit keyspace even after hitting it with Grover's algorithm and a large quantum computer. An 84-bit keyspace can be brute-forced by people willing to throw huge amounts of resources at the problem, but it'd be tremendously annoying. A few years ago when distributed.net tackled RC5-64 (with a keyspace a millionth the size of a quantum-attacked 3DES) it took them a large distributed cracking effort and eighteen months of time. I don't know who told you that 3DES was insecure. They misled you. It is not insecure. It is slow, it is ungainly, it has all the aesthetics of a Soviet worker's housing bloc, and we have better ciphers available to us. But 3DES has also been turning brilliant cryptanalysts into burned-out alcoholic wrecks for 40 years. > I think the same goes for the hashing algorithm SHA1. Again, required per the spec, and this can be prevented by having one person on the list use a DSA-2048/-3072 key, which forbids SHA-1 usage. > Is my understanding correct or do I miss an important fact? You're missing the boat on the security of 3DES. You're correct that SHA-1 is unsuitable for use as a hashing algorithm and that usage of it may be mandated in certain situations. > What are your thoughts about this behaviour? Take it up with the IETF OpenPGP working group, not GnuPG. Get them to change the RFC. > Wouldn't it be great to raise the minimum encryption and hashing level to a > more secure cipher? The current opinion in the IETF OpenPGP working group is the next iteration of the standard will probably settle on AES256 and SHA256 as replacement MUSTs for the current 3DES/SHA-1. (Other hashes, such as BLAKE2, SHA512, and SHA-3/Keccak, are also being discussed as optionals.) However, when this next iteration will be released is anyone's guess. The group works painfully slowly. From wk at gnupg.org Mon Mar 13 17:38:09 2017 From: wk at gnupg.org (Werner Koch) Date: Mon, 13 Mar 2017 17:38:09 +0100 Subject: Interleaving issue In-Reply-To: <1024bda4-f796-788f-1ecd-b66784dbed6f@sixdemonbag.org> (Robert J. Hansen's message of "Sun, 12 Mar 2017 12:36:17 -0400") References: <1024bda4-f796-788f-1ecd-b66784dbed6f@sixdemonbag.org> Message-ID: <87o9x55dzi.fsf@wheatstone.g10code.de> On Sun, 12 Mar 2017 17:36, rjh at sixdemonbag.org said: > sig!3 1DCBDC01B44427C7 2015-07-16 Robert J. Hansen 14 good signatures This is a diagnostic which goes to stderr. The former is fully buffered, the latter is line buffered. From a technical view this is all correct but I agree that it is a bit annoying. I'll add a fflush right before the stats output which solves it for this case. In the meantime you may run stdbuf -oL gpg GPGARGS to also line buffer stdout. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From 2014-667rhzu3dc-lists-groups at riseup.net Mon Mar 13 23:50:53 2017 From: 2014-667rhzu3dc-lists-groups at riseup.net (MFPA) Date: Mon, 13 Mar 2017 22:50:53 +0000 Subject: Security doubts on 3DES default In-Reply-To: <024101d29c0c$e1b127f0$a51377d0$@sixdemonbag.org> References: <4960a07f-b61a-4d43-9baa-0075ef2e3230@addere.ch> <024101d29c0c$e1b127f0$a51377d0$@sixdemonbag.org> Message-ID: <171704821.20170313225053@riseup.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Monday 13 March 2017 at 3:17:07 PM, in , Robert J. Hansen wrote:- > Again, required per the spec, and this can be > prevented by having one person > on the list use a DSA-2048/-3072 key, which forbids > SHA-1 usage. Really? many of the messages to the PGPNET discussion group [0] have SHA-1 signatures. Messages are signed and encrypted to about 30 keys, one of which is DSA-2048. Showpref on that DSA-2048 key gives Digest: SHA1, SHA256, RIPEMD160. [0] or . - -- Best regards MFPA During an eruption - move away from the volcano - not towards it -----BEGIN PGP SIGNATURE----- iNUEARYKAH0WIQQzrO1O6RNO695qhQYXErxGGvd45AUCWMciEF8UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0MzNB Q0VENEVFOTEzNEVFQkRFNkE4NTA2MTcxMkJDNDYxQUY3NzhFNAAKCRAXErxGGvd4 5FpqAP4oLgKKg22wPXEDbTwkb6VzPgxjU4TL0lHcvT6usOBJUwEA9Ao6k4c55mVf YwCI3RL3YEnIWC5whHeq0wmJwdSgTQmJAZMEAQEKAH0WIQSzrn7KmoyLMCaloPVr fHTOsx8l8AUCWMciEF8UgAAAAAAuAChpc3N1ZXItZnByQG5vdGF0aW9ucy5vcGVu cGdwLmZpZnRoaG9yc2VtYW4ubmV0QjNBRTdFQ0E5QThDOEIzMDI2QTVBMEY1NkI3 Qzc0Q0VCMzFGMjVGMAAKCRBrfHTOsx8l8G5yCACI+IwB8NmwMamZx1ZSnIbXLKLL fweWhnqvXIy8IKHc51h/sAYFbEu7S8XvHCXjDKJWeUJJja/jfhQG62BzYmhMOSYZ OLd0op3Cthk9sHBQ/FO2gVkJM88c0M8MqemK7dGtenIHOV23ahjQbQrXr0pXqDfj 9vctTPmCnoGQhp5D+En7E3hiH5a6qdfFa4CCLSeCbs+j7scur55R6IRQCiLSEAXL QoKJ8+fFecqlSScpgv5o75JvXxmJOmUcuXKfK5LDH0ZGt3C3tJbYHOQFAfZUua6D XO7jpxLo7N4XOhkCv9H/XVAb5y17w/7RVNv0xuBij7hkr7ac9gxakBgRXB5c =/wO3 -----END PGP SIGNATURE----- From rjh at sixdemonbag.org Tue Mar 14 00:02:48 2017 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Mon, 13 Mar 2017 19:02:48 -0400 Subject: Security doubts on 3DES default In-Reply-To: <171704821.20170313225053@riseup.net> References: <4960a07f-b61a-4d43-9baa-0075ef2e3230@addere.ch> <024101d29c0c$e1b127f0$a51377d0$@sixdemonbag.org> <171704821.20170313225053@riseup.net> Message-ID: <8a90f560-88f0-c3c8-4598-78080966d743@sixdemonbag.org> >> Again, required per the spec, and this can be >> prevented by having one person >> on the list use a DSA-2048/-3072 key, which forbids >> SHA-1 usage. > > Really? many of the messages to the PGPNET discussion group [0] have > SHA-1 signatures. Messages are signed and encrypted to about 30 keys, > one of which is DSA-2048. Showpref on that DSA-2048 key gives > Digest: SHA1, SHA256, RIPEMD160. I was speaking a bit too glibly; I'm sorry about that. If I'm sending to 30 people it's quite likely I'll wind up using CAST or 3DES, since that's the lowest common denominator. Cipher preferences have a complex find-the-best-option algorithm that finds what all recipients can use, then chooses one from among them -- so finding a "common denominator" of algorithms is important. But lowest common denominator for signatures is ... it's uncommon to encounter such a situation; in fact, in 25 years of using PGP I don't think I've ever encountered it. If I sign a message with TIGER192 and you can't verify it, tough luck. Given this, I don't know how you'd come up with a real-world case where you'd need a common hash algorithm set for signing purposes. But if there were such a case where there was a lowest common denominator hash algorithm, DSA-2048 requires a 224-bit hash (and -3072 requires 256), so inclusion of either of those would preclude any 160-bit hash being used; they could not appear in a common algorithm set. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 630 bytes Desc: OpenPGP digital signature URL: From 2014-667rhzu3dc-lists-groups at riseup.net Tue Mar 14 00:57:16 2017 From: 2014-667rhzu3dc-lists-groups at riseup.net (MFPA) Date: Mon, 13 Mar 2017 23:57:16 +0000 Subject: Security doubts on 3DES default In-Reply-To: <8a90f560-88f0-c3c8-4598-78080966d743@sixdemonbag.org> References: <4960a07f-b61a-4d43-9baa-0075ef2e3230@addere.ch> <024101d29c0c$e1b127f0$a51377d0$@sixdemonbag.org> <171704821.20170313225053@riseup.net> <8a90f560-88f0-c3c8-4598-78080966d743@sixdemonbag.org> Message-ID: <159716701.20170313235716@riseup.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On Monday 13 March 2017 at 11:02:48 PM, in , Robert J. Hansen wrote:- > I don't > know how you'd > come up with a real-world case where you'd need a > common hash algorithm > set for signing purposes. GnuPG presumably has a reason for defaulting to SHA-1 signatures on a lot of the messages encrypted to the 30 members' keys on PGPNET. Some people whose PGPNET group messages have SHA-1 signatures report that non-group messages they sign and encrypt have SHA-256 signatures. For what its worth, forcing SHA-256 signatures with a "digest-algo" line in gpg.conf doesn't cause anybody to shout that there is a problem. But GnuPG says "gpg: WARNING: forcing digest algorithm SHA512 (10) violates recipient preferences". - -- Best regards MFPA After all is said and done, a lot more will be said than done. -----BEGIN PGP SIGNATURE----- iNUEARYKAH0WIQQzrO1O6RNO695qhQYXErxGGvd45AUCWMcx3V8UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0MzNB Q0VENEVFOTEzNEVFQkRFNkE4NTA2MTcxMkJDNDYxQUY3NzhFNAAKCRAXErxGGvd4 5IjuAP9TeNXQReTgAda3IoJYh4b5RzgZMcRR3oILvKAlVo0RFQEA2safGRSwmmHg b9JMcHEtCHNmR25N1JFouT+Oyj3YIQ2JAZMEAQEKAH0WIQSzrn7KmoyLMCaloPVr fHTOsx8l8AUCWMcx3V8UgAAAAAAuAChpc3N1ZXItZnByQG5vdGF0aW9ucy5vcGVu cGdwLmZpZnRoaG9yc2VtYW4ubmV0QjNBRTdFQ0E5QThDOEIzMDI2QTVBMEY1NkI3 Qzc0Q0VCMzFGMjVGMAAKCRBrfHTOsx8l8ObICACA4cPYiqk9XkUIy0CNV5BMo4yr lLw6O9zYh2CQnC5k0A1xnVPDg3ZQLZKufuTP2DUuglKk7f5aEosGkDgm7ukQm8Il Xkx1Nm7kULTDSZwW0YAXu3IswI8pyUZIyztHps3RYzT2iRVJp2p0P3OJjHTCdfIe +nLImyOKHV442nd7ylIqbFZ0431O/KWqwFF+OSsg0VJZo0x+mAm0IY6RQuvf3DIO 90BMdh9KmPPeMd2Hm2/x5qN/p/gQhW9xWs1PH1vkDp7dM0OPUMlR4WZCbECPmLuD MewuH8XK9nG478Z1TFjH8sS2XuDWp0H32C77tkrERAMX3WM/snH7k30pQN+u =HUGl -----END PGP SIGNATURE----- From dkg at fifthhorseman.net Tue Mar 14 02:35:01 2017 From: dkg at fifthhorseman.net (Daniel Kahn Gillmor) Date: Mon, 13 Mar 2017 21:35:01 -0400 Subject: private-keys-v1.d In-Reply-To: References: Message-ID: <87pohktzcq.fsf@alice.fifthhorseman.net> On Thu 2017-03-09 13:44:19 -0500, Long Si wrote: > Before migrating to a new system, I exported my GPG secret keys and > then imported them. what version of gpg did you have on the old system? what version on the new system? the steps you took sound reasonable to me, as long as the new system had gpg 2.1.x, so i'm a bit puzzled as to why the import failed for you. with a bit more info, maybe we can get to the bottom of things, --dkg From ryru at addere.ch Tue Mar 14 21:25:47 2017 From: ryru at addere.ch (Ryru) Date: Tue, 14 Mar 2017 21:25:47 +0100 Subject: Security doubts on 3DES default In-Reply-To: <024101d29c0c$e1b127f0$a51377d0$@sixdemonbag.org> References: <4960a07f-b61a-4d43-9baa-0075ef2e3230@addere.ch> <024101d29c0c$e1b127f0$a51377d0$@sixdemonbag.org> Message-ID: Thank you Robert for your response and point of view. On 03/13/2017 04:17 PM, Robert J. Hansen wrote: >> According to the gpg2 man page, 3DES is added always as kind of least >> common denominator: > > This is required behavior per RFC4880. Your concern should be addressed to > the IETF OpenPGP working group, not to GnuPG. Just because it's required behaviour doesn't mean it's (still) good. ;-) But I will try contact them. Apart from that, as GnuPG is in a kind of symbiosis with OpenPGP/RFC4880, I think it's important to discuss this on this mailing list (as well). >> In my opinion this design decision can lead to serious security troubles. > If >> someone, knowingly or not, removed all his/her symmetric encryption >> algorithms in his/her public key, our conversation would only be 3DES >> encrypted. > > There is no security risk with 3DES unless you (foolishly) choose to encrypt > vast quantities of data (multiple gigabytes) with the same key. > > RFC4880 requires 3DES be used with three independent subkeys, giving it a > technical keyspace of 192 bits, the same as AES192. However, 24 of those > bits are used for parity and contribute nothing to the security of the > system, meaning it comes in at 168 bits of effective key. This is a > keyspace about a trillion times larger than AES128's. > > There are a couple of *theoretical* attacks on 3DES that reduce it to about > a "mere" 112 bits (still unassailable, but less strong than we'd like). The > best known attack requires a billion known plaintexts and > 100,000,000,000,000,000 gigabytes of RAM. > > 3DES is even somewhat resistant to quantum computation, as a 168-bit > keyspace is still an 84-bit keyspace even after hitting it with Grover's > algorithm and a large quantum computer. An 84-bit keyspace can be > brute-forced by people willing to throw huge amounts of resources at the > problem, but it'd be tremendously annoying. A few years ago when > distributed.net tackled RC5-64 (with a keyspace a millionth the size of a > quantum-attacked 3DES) it took them a large distributed cracking effort and > eighteen months of time. > > I don't know who told you that 3DES was insecure. They misled you. It is > not insecure. It is slow, it is ungainly, it has all the aesthetics of a > Soviet worker's housing bloc, and we have better ciphers available to us. I agree with you, we have better options than 3DES so we should switch to better ciphers as soon as possible. > But 3DES has also been turning brilliant cryptanalysts into burned-out > alcoholic wrecks for 40 years. > >> I think the same goes for the hashing algorithm SHA1. > > Again, required per the spec, and this can be prevented by having one person > on the list use a DSA-2048/-3072 key, which forbids SHA-1 usage. > >> Is my understanding correct or do I miss an important fact? > > You're missing the boat on the security of 3DES. You're correct that SHA-1 > is unsuitable for use as a hashing algorithm and that usage of it may be > mandated in certain situations. I think it's a question of time till 3DES is broken, like it was with SHA-1. To be at least one step ahead of such a mess should be the goal. > >> What are your thoughts about this behaviour? > > Take it up with the IETF OpenPGP working group, not GnuPG. Get them to > change the RFC. As mentioned, I'll try to reach them. The support from the GnuPG community, on this topic, would be appreciated. > >> Wouldn't it be great to raise the minimum encryption and hashing level to > a >> more secure cipher? > > The current opinion in the IETF OpenPGP working group is the next iteration > of the standard will probably settle on AES256 and SHA256 as replacement > MUSTs for the current 3DES/SHA-1. (Other hashes, such as BLAKE2, SHA512, > and SHA-3/Keccak, are also being discussed as optionals.) Where have you found this information? I only found this draft[0] which still contains 3DES and SHA-1. Thanks in advance and best regards Pascal [0] https://tools.ietf.org/html/draft-ietf-openpgp-rfc4880bis-01 From rjh at sixdemonbag.org Tue Mar 14 21:54:52 2017 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Tue, 14 Mar 2017 16:54:52 -0400 Subject: Security doubts on 3DES default In-Reply-To: References: <4960a07f-b61a-4d43-9baa-0075ef2e3230@addere.ch> <024101d29c0c$e1b127f0$a51377d0$@sixdemonbag.org> Message-ID: > Apart from that, as GnuPG is in a kind of symbiosis with > OpenPGP/RFC4880, I think it's important to discuss this on this mailing > list (as well). So long as you understand GnuPG will not make any changes that break RFC conformance... and dropping SHA1/3DES breaks RFC conformance. > I agree with you, we have better options than 3DES so we should switch > to better ciphers as soon as possible. Everyone agrees. GnuPG for many years has defaulted to AES. 3DES exists for RFC conformance. We've migrated away from 3DES as far as we can; any further requires a change to the RFC. > I think it's a question of time till 3DES is broken This opinion is not shared by the cryptanalytic community as a whole. We are nowhere near a break in 3DES. > As mentioned, I'll try to reach them. The support from the GnuPG > community, on this topic, would be appreciated. We're already in the working group trying to push this forward. > Where have you found this information? I only found this draft[0] which > still contains 3DES and SHA-1. The WG has a mailing list where these things are discussed. Also, many WG members have private asides with other WG members. From 2014-667rhzu3dc-lists-groups at riseup.net Wed Mar 15 01:38:45 2017 From: 2014-667rhzu3dc-lists-groups at riseup.net (MFPA) Date: Wed, 15 Mar 2017 00:38:45 +0000 Subject: GnuPG 2.1.19 crashing when listing keys, if tofu-default-policy is "ask" Message-ID: <1519215302.20170315003845@riseup.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi I have been having GnuPG crash with the following message when listing keys:- gpg --list-keys gpg: Ohhhh jeeee: Assertion "conflict_set" in get_trust failed (/home/wk/b-w32/speedo/PLAY-release/gnupg-w32-2.1.19/g10/tofu.c:2787) This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. An internet search on the message leads me to a Debian bug report [0]. I am using GnuPG version 2.1.19 on Windows, running the pre-compiled Windows binaries linked from the release announcement. I have the "with-fingerprint" option in gpg.conf; commenting it out makes no difference. I also have "tofu-default-policy ask"; changing "ask" to "unknown" makes the problem go away. [0] - -- Best regards MFPA Something must be done. This is something. Therefore, we must do it. -----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEs65+ypqMizAmpaD1a3x0zrMfJfAFAljIjO9fFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEIz QUU3RUNBOUE4QzhCMzAyNkE1QTBGNTZCN0M3NENFQjMxRjI1RjAACgkQa3x0zrMf JfBeeQgAggZsNk8f1fXFkPM0qrhg7j8pMWfBP5UFUCXE5iom01jwwCx57gzITcOl fMHEWLkW7acCqfWDxrevEpAyiQ+K9dpbOUIgimf8YhhlnF9XUytcHEGopgNq9C5/ h2XeD2UcjY51WPS2Qr+KxMKGZ5QAUEgQuqhoLF4kEzDC4RySg3xU7mfRccah7Qdd tmZwiAfe8Jjd3CgmWQJhBbBz+OTEt3kQ/D/sLJQl54SO4sy+Wmyx62QR8bK1YXQZ Q0MMadgMXV0p6EtE71JDuVNctptmFFyEIQwLJownLzoaVC1SXSJLcc+h3Q1oz1k+ 03r2DoEdEepo+Prx0iN9m9WZQ2xH1ojVBAEWCgB9FiEEM6ztTukTTuveaoUGFxK8 Rhr3eOQFAljIjPZfFIAAAAAALgAoaXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBn cC5maWZ0aGhvcnNlbWFuLm5ldDMzQUNFRDRFRTkxMzRFRUJERTZBODUwNjE3MTJC QzQ2MUFGNzc4RTQACgkQFxK8Rhr3eOSBvgEAl+FP34lKrWqeuNBar/fYEdUEIHsu 3hwLbB5gfOXXS3oA/1AHZ4ULp2/YVsyeYSZDsU0O1DSyxRP1+j1Eq92eCQMA =SXiX -----END PGP SIGNATURE----- From miro.rovis at croatiafidelis.hr Wed Mar 15 10:14:06 2017 From: miro.rovis at croatiafidelis.hr (Miroslav Rovis) Date: Wed, 15 Mar 2017 10:14:06 +0100 Subject: HTTPS keyservers (with SSL-keys recording), WAS: help In-Reply-To: References: <974a1560e5198f59f241336baeb09e1f@riseup.net> Message-ID: <20170315091406.GA3453@g0n.xdwgrp> My reply is really to one issue of all, but the discussion is noteworthy, and also it took place 2 1/2 weeks ago, so I leave the whole email quoted. On 170228-00:35+0100, Damien Goutte-Gattat wrote: > Hi, > > On 02/27/2017 04:07 PM, rsvx at riseup.net wrote: > > I'll use my master key offline. Following this guidelines: > > https://incenp.org/notes/2015/using-an-offline-gnupg-master-key.html > > > > I also implemented the Appelbaum's config.(Riseup Best Practices) Will > > it work properly if the Master Key isn't on my machine? > > It should. > > Note, however, that Riseup's Best Practices [1] and proposed > configuration file [2] are partially obsolete, *especially* if you are > using GnuPG 2.1. Many of the proposed options and advices are not needed > anymore, as GnuPG already does The Right Thing. > > > > And the following faults are coming: > > gpg: keyserver option 'ca-cert-file' is obsolete; please use > > 'hkp-cacert' in dirmngr.conf > > If you're using the sks-keyservers.net pool you no longer need to > provide GnuPG with the CA certificate file, as it is now bundled with > GnuPG (>= 2.1.11) and automatically used when needed. (And with GnuPG >= > 2.1.16 you will no longer even need to explicity set the keyserver > option, as hkps.pool.sks-keyservers.net is already the default.) > > > > gpg: keyserver option 'no-try-dns-srv' is unknown > > This option no longer exists, but I *think* that if you really want to, > you can disable SRV lookups by explicitly specifying a port number when > setting the keyserver, as in: > > keyserver hkps.pool.sks-keyservers.net:443 Nope! The port is 11371. I just tried apply your suggestion (because I'd very much like two things, see below), and I added to my: ~/.gnupg/dirmngr.conf the line: keyserver hkps.pool.sks-keyservers.net:443 but this are the HTTP Requests full uri that I found in my traces: 125 http://pool.sks-keyservers.net:11371/pks/lookup?op=get&options=mr&search=0x3F533109A9509B14 153 http://pool.sks-keyservers.net:11371/pks/lookup?op=get&options=mr&search=0xCBB15A68EF3AC804875D5C4E153FE398821C8394 234 http://pool.sks-keyservers.net:11371/pks/lookup?op=get&options=mr&search=0xB34135EC5C5D05CF0FBCC8D583864DFC21ABA4A6 1046 http://pool.sks-keyservers.net:11371/pks/lookup?op=get&options=mr&search=0x19419825DE14BEA8 1076 http://pool.sks-keyservers.net:11371/pks/lookup?op=get&options=mr&search=0x9011A67E3A73CDF575FA841C7BCC5A972762EBA1 1110 http://pool.sks-keyservers.net:11371/pks/lookup?op=get&options=mr&search=0x8EB8BFEFAA18B872 -- those were just some keys from the public mailing lists, I think I used Mutt ML this time -- ( gotten with the unfinished, but mostly working, script of mine: https://github.com/miroR/tshark-hosts-conv , the number in front is the packet the request it appears in ) > -- > [1] https://riseup.net/en/security/message-security/openpgp/best-practices > [2] > https://raw.githubusercontent.com/ioerror/duraconf/master/configs/gnupg/gpg.conf > And the two things that I would very much like to see (in not too distant future), is, 1) of course, HKP in secure conversation client-server, not in plaintext, over the internet 2) secure HKP decryptable for end user, at his configuration and request. Pls. see this youtube-dl issue: Write TLS session keys to $SSLKEYLOGFILE #11614 https://github.com/rg3/youtube-dl/issues/11614 (of course devs will find real read in the links therefrom, but I'm not one, I give what I can follow) and know that Wget program has implemented that decryptability for end user (just like some big browsers do if you set up $SSLKEYLOGFILE...) I record SSL-keys all the time, and I believe every communication in/with my machine must be permitted by me, and open to my inspection, else, it's getting very close to doing/allowing things to be done behind my back... A very good example of things possibly being done, allowed to be done behind my back is dbus, the core of all big Desktop Environments, the best and sine qua non friend of SystemDestruction or systemd... Just look it up, and apparently, that's the normal communication setup by dbus (see below about that too): Re: How to avoid stealth installation of systemd? http://forums.debian.net/viewtopic.php?f=20&t=116770&start=45#p552566 where find: $ ps aux | grep ssh root 2184 0.0 0.0 54976 1004 ? Ss Sep06 0:00 /usr/sbin/sshd mr 2447 0.0 0.0 10592 32 ? Ss Sep06 0:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session x-session-manager mr 15141 0.0 0.0 19980 1796 pts/9 S+ 21:48 0:00 grep ssh $ I really hope GnuPG will go the SSL way for getting the keys, and the decryptable-for-user way, to get it all open, at user's request/configuration (not by default! nobody does it by default any more, can be hijacked from non-advanced users). I learned that recently from people at secure-os that this way is how dbus regularly works! Quoting: > Both ssh-agent and dbus must be wrapped around X11 in order to do > their job, and that is just what that process is doing. It is allowing > you to have a functional dbus and convenient ssh key storage while > using your desktop. You can do without these conveniences, but maybe > not with debian... so what you saw here is regular behavior, unlikely > to be in any way interacting with the Internet. (not a quote from email to which this email is a reply to) ( I'll reply to the > unlikely to be in any way interacting with the Internet part there, when I find time. ) BTW, I was happy to learn that GnuPG programmers didn't trust dbus for IPC either. Regards! -- Miroslav Rovis Zagreb, Croatia https://www.CroatiaFidelis.hr -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: Digital signature URL: From justus at g10code.com Wed Mar 15 12:11:53 2017 From: justus at g10code.com (Justus Winter) Date: Wed, 15 Mar 2017 12:11:53 +0100 Subject: GnuPG 2.1.19 crashing when listing keys, if tofu-default-policy is "ask" In-Reply-To: <1519215302.20170315003845@riseup.net> References: <1519215302.20170315003845@riseup.net> Message-ID: <87r31yokue.fsf@europa.jade-hamburg.de> Hi, MFPA <2014-667rhzu3dc-lists-groups at riseup.net> writes: > I have been having GnuPG crash with the following message when listing > keys:- > > gpg --list-keys > gpg: Ohhhh jeeee: Assertion "conflict_set" in get_trust failed > (/home/wk/b-w32/speedo/PLAY-release/gnupg-w32-2.1.19/g10/tofu.c:2787) > This application has requested the Runtime to terminate it in an unusual > way. > Please contact the application's support team for more information. https://bugs.gnupg.org/gnupg/issue2959 Justus -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 487 bytes Desc: not available URL: From wk at gnupg.org Wed Mar 15 12:13:18 2017 From: wk at gnupg.org (Werner Koch) Date: Wed, 15 Mar 2017 12:13:18 +0100 Subject: Security doubts on 3DES default In-Reply-To: (Robert J. Hansen's message of "Tue, 14 Mar 2017 16:54:52 -0400") References: <4960a07f-b61a-4d43-9baa-0075ef2e3230@addere.ch> <024101d29c0c$e1b127f0$a51377d0$@sixdemonbag.org> Message-ID: <87zigmztbl.fsf@wheatstone.g10code.de> On Tue, 14 Mar 2017 21:54, rjh at sixdemonbag.org said: > So long as you understand GnuPG will not make any changes that break RFC > conformance... and dropping SHA1/3DES breaks RFC conformance. Well, it is possible to use --weak-digest SHA1 --disable-cipher-algo 3DES with gpg. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From wk at gnupg.org Wed Mar 15 16:36:42 2017 From: wk at gnupg.org (Werner Koch) Date: Wed, 15 Mar 2017 16:36:42 +0100 Subject: GnuPG 2.1.19 crashing when listing keys, if tofu-default-policy is "ask" In-Reply-To: <87r31yokue.fsf@europa.jade-hamburg.de> (Justus Winter's message of "Wed, 15 Mar 2017 12:11:53 +0100") References: <1519215302.20170315003845@riseup.net> <87r31yokue.fsf@europa.jade-hamburg.de> Message-ID: <87innazh4l.fsf@wheatstone.g10code.de> On Wed, 15 Mar 2017 12:11, justus at g10code.com said: > https://bugs.gnupg.org/gnupg/issue2959 This bug was reported by dkg a month ago but we unfortunately missed to fix it for 2.1.19. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From wk at gnupg.org Wed Mar 15 16:46:58 2017 From: wk at gnupg.org (Werner Koch) Date: Wed, 15 Mar 2017 16:46:58 +0100 Subject: HTTPS keyservers (with SSL-keys recording) In-Reply-To: <20170315091406.GA3453@g0n.xdwgrp> (Miroslav Rovis's message of "Wed, 15 Mar 2017 10:14:06 +0100") References: <974a1560e5198f59f241336baeb09e1f@riseup.net> <20170315091406.GA3453@g0n.xdwgrp> Message-ID: <87efxyzgnh.fsf_-_@wheatstone.g10code.de> On Wed, 15 Mar 2017 10:14, miro.rovis at croatiafidelis.hr said: > keyserver hkps.pool.sks-keyservers.net:443 I guess we should better default to hkps:// if a scheme is not given. I have not checked whether this is already the case. > I record SSL-keys all the time, and I believe every communication > in/with my machine must be permitted by me, and open to my inspection, I didn't understand the need for recording session keys - in general we try hard not to leave any trace of session keys. BTW, we should not use the term SSL anymore. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From hebbar.ramachandra at gmail.com Wed Mar 15 15:27:08 2017 From: hebbar.ramachandra at gmail.com (Ramachandra Hebbar) Date: Wed, 15 Mar 2017 15:27:08 +0100 Subject: Need help: gpg: public key decryption failed: Wrong secret key used Message-ID: Hello Experts, We are implementing PGP solution using GnuPG. We have hit one issue, below is the error, gpg: public key decryption failed: Wrong secret key used gpg: decryption failed: No secret key I'm trying to encrypt sample test message without using armor (--no-armor). I'm getting above message. But with armor i don't see this issue with same key pair. We are having 2.3.3 version of Gpg4Win. Need this help to go forward. Already tried following with no luck, 1. Killed gpg-agent & restarted 2. Writing the encrypted content to file. Then tried decryption directly in Kleopatra tool it works but i get same error as above -- Thanks in advance, Ramachandra Hebbar -------------- next part -------------- An HTML attachment was scrubbed... URL: From geniegate at yahoo.com Wed Mar 15 22:14:37 2017 From: geniegate at yahoo.com (Jamie H.) Date: Wed, 15 Mar 2017 21:14:37 +0000 (UTC) Subject: Question about signing keys and trust. References: <562649904.943824.1489612477344.ref@mail.yahoo.com> Message-ID: <562649904.943824.1489612477344@mail.yahoo.com> Hello! It's been a few years since I've messed with gpg, but I have an application that needs something kind of like distributed groups. Lets say I have: "key group" (which is owned by who-cares, it's a public key only that represents a group of people) I have a person, lets say William Smith who has his key signed by who-cares William Smith then signs Betty Boop with his key. So William Smith and Betty Boop are sort of like members of "key group" because Betty Boop has a signature by someone who has their key signed by the key group, and if Betty Boop signs someone, up to n-depth, then those people become members of "key group". No one has authority to add or remove people, except other members of the same group. ... fast forward .. In the application, lets say it's a spam fighting tool, a Betty Boop marks a message as spam. I trust members of "key group" to mark spam, but I don't trust them with everything, just marking spam, so the spam message is deleted. Popeye, who is a member of "alien group" marks something as spam too, but since popeye doesn't have a key signed by someone in "key group", I do not trust him to flag messages as spam, so I just ignore it. Basically, I'm trying to implement something akin to a distributed group system where members of a group can (to a configurable point) include others and I had thought perhaps I could coax GPG into doing this, since I'll also need to do a lot of other stuff with GPG, it just makes sense to try and use the key system for it if I can. Problem is I can't see how! Is there a way I can look at someones public key and (without importing anything into my personal key files) list in a kind of chain fashion how many other signers there were? In the above, I'll have access to the public keys of Betty Boop, Popeye, William Smith and "key group". I admit, GPG probably wasn't designed for this, and I don't really get the whole trust level thing.. and if it's impossible or impractical I'll find another way, but it would be convenient. Any pointers on where I should look? Much appreciated! Jamie From rjh at sixdemonbag.org Thu Mar 16 01:44:41 2017 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Wed, 15 Mar 2017 20:44:41 -0400 Subject: Security doubts on 3DES default In-Reply-To: <87zigmztbl.fsf@wheatstone.g10code.de> References: <4960a07f-b61a-4d43-9baa-0075ef2e3230@addere.ch> <024101d29c0c$e1b127f0$a51377d0$@sixdemonbag.org> <87zigmztbl.fsf@wheatstone.g10code.de> Message-ID: <815bf6f8-eb96-b459-67f5-215501493bfb@sixdemonbag.org> > --weak-digest SHA1 --disable-cipher-algo 3DES Yeah, but that's ... *bad*. Breaks most of the Web of Trust, makes most cert sigs meaningless, removes the fallback cipher ... I think this is a great example of a cure worse than the disease. :) Phil Pennock made a post a bit ago detailing his experiment with disabling SHA1. It was informative, to say the least. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 659 bytes Desc: OpenPGP digital signature URL: From miro.rovis at croatiafidelis.hr Thu Mar 16 06:55:56 2017 From: miro.rovis at croatiafidelis.hr (Miroslav Rovis) Date: Thu, 16 Mar 2017 06:55:56 +0100 Subject: HTTPS keyservers (with SSL-keys recording) In-Reply-To: <87efxyzgnh.fsf_-_@wheatstone.g10code.de> References: <974a1560e5198f59f241336baeb09e1f@riseup.net> <20170315091406.GA3453@g0n.xdwgrp> <87efxyzgnh.fsf_-_@wheatstone.g10code.de> Message-ID: <20170316055555.GA8080@g0n.xdwgrp> On 170315-16:46+0100, Werner Koch wrote: > On Wed, 15 Mar 2017 10:14, miro.rovis at croatiafidelis.hr said: > > > keyserver hkps.pool.sks-keyservers.net:443 > > I guess we should better default to hkps:// if a scheme is not given. which is, IIUC, HTTPS key protocol, like hkp:// is HTTP key protocol. > I have not checked whether this is already the case. No, it's not implemented, or if it is, it's not by default in my Gentoo. But if it's local configuration, I'm not an expert to know what to configure to get it implemented. > > I record SSL-keys all the time, and I believe every communication > > in/with my machine must be permitted by me, and open to my inspection, > > I didn't understand the need for recording session keys - in general we > try hard not to leave any trace of session keys. How do you solve issues that arise then? How do you guard your system if you don't have an option to inspect what it happening in your system? There's no defence generally without knowing what happens on your turf, not really, ever! > BTW, we should not use the term SSL anymore. BTW, my original title to that Youtube-dl issue contained SSL-key, not TLS-key recording, the maintainer there changed that title... It's very hard for me to contradict someone of your format, Werner, but other smart people say the name change has been purely political, without any technical merit to it... So allow me to point to you others that contradict to you, and IMO rebellion against senseless practices is a good thing(TM): https://wiki.wireshark.org/SSL and if you try: https://wiki.wireshark.org/TLS you get "This page does not exist yet." > > Shalom-Salam, Peace! > Werner > > -- > Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. Deutch schreiben, lesen und schprechen I m?chte lernen... Aber kein zeit f?r jetzt... ( I like German, and German-speaking nations, culture and way of life a lot. ) Sincere respect and regards to you and your team! -- Miroslav Rovis Zagreb, Croatia https://www.CroatiaFidelis.hr -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: Digital signature URL: From bill at cse.ucdavis.edu Thu Mar 16 04:46:53 2017 From: bill at cse.ucdavis.edu (Bill Broadley) Date: Wed, 15 Mar 2017 20:46:53 -0700 Subject: ADMIN: Some mail addresses are now rewritten In-Reply-To: <87varf911e.fsf@wheatstone.g10code.de> References: <43387B6C-C35B-4448-8B55-35763D94CAC4@microsoft.com> <87varf911e.fsf@wheatstone.g10code.de> Message-ID: <3e613056-8b46-4ef2-7466-164de910cbac@cse.ucdavis.edu> On 03/11/2017 09:27 AM, Werner Koch wrote: > Hi! > > You may have noted that the From address has been rewritten to show the > list address instead of your address. In addition a reply-to header has > been set so that your address is also known. IMO reply should go to the send and reply-list/group reply should go to the list. Sure people make mistakes, but it's still the most reasonable behavior. > The reason for this is that some mail sites now have a DMARC reject > policy which leads to a bounce for all subscribers whose mail provider > honors this DMARC policy - for example gmail. After a few bounces > message delivery to those subscribers will blocked by our Mailman. I've been dealing with this. After watching these kinds of problems in multiple environments I think what should happen with mailman, dkim, SPF, etc is: A) If mailman is going to leave DKIM headers intact then the email should be forwarded without modifications to the body/signature. So readers of the mailing list should be able to DKIM verify the centor B) if mailman is going to modify the email then it should: 1) resign with it's DKIM key (for gnupg.org in this case) 2) allow mailing list users to set a flag saying "Do not accept email from me unless properly signed with DKIM" 3) Upon finding properly signed DKIM messages that will be stripped/resigned mailman should add a new header. DKIM-verified-by-mailman or similar. I realize this isn't the best place to discuss such things, but welcome any input. I'm watching the mailman list, on a #dmarc IRC channel, or similar. But finding a place that discusses standards that impact so many different pieces is tricky. > The problem with this rewriting is that it breaks quoting. For example > here is how I would have replied to Jeff's test mail: > > On Sat, 11 Mar 2017 15:02, gnupg-users at gnupg.org said: > > > Just a simple test message as asked by Werner to test something? > > Thank you. > > Thus I think marking the address invalid would have been a better choice > for Mailman - but there is no option for this yet. Not sure I follow, I hit group reply in Thunderbird and at the top of this message is: On 03/11/2017 09:27 AM, Werner Koch wrote: > Hi! Which is exactly what I expected. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: From wk at gnupg.org Thu Mar 16 12:08:08 2017 From: wk at gnupg.org (Werner Koch) Date: Thu, 16 Mar 2017 12:08:08 +0100 Subject: ADMIN: Some mail addresses are now rewritten In-Reply-To: <3e613056-8b46-4ef2-7466-164de910cbac@cse.ucdavis.edu> (Bill Broadley via Gnupg-users's message of "Wed, 15 Mar 2017 20:46:53 -0700") References: <43387B6C-C35B-4448-8B55-35763D94CAC4@microsoft.com> <87varf911e.fsf@wheatstone.g10code.de> <3e613056-8b46-4ef2-7466-164de910cbac@cse.ucdavis.edu> Message-ID: <87r31xwkbr.fsf@wheatstone.g10code.de> On Thu, 16 Mar 2017 04:46, gnupg-users at gnupg.org said: > IMO reply should go to the send and reply-list/group reply should go to the > list. Sure people make mistakes, but it's still the most reasonable behavior. There are two schools on this matter. This here is a privacy related list and thus we want to avoid accidently posting a PM to the list. > I've been dealing with this. After watching these kinds of problems in multiple > environments I think what should happen with mailman, dkim, SPF, etc is: We can only use what Mailman provides ;-) > Not sure I follow, I hit group reply in Thunderbird and at the top of this > message is: > > On 03/11/2017 09:27 AM, Werner Koch wrote: Right, because my From header has not been rewritten (no reject DMARC policy at gnupg.org). But if you look above you can notice that Gnus took the ML address - should be easy to fix but right now I don't have spare cycles. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From dkg at fifthhorseman.net Wed Mar 15 22:16:28 2017 From: dkg at fifthhorseman.net (Daniel Kahn Gillmor) Date: Wed, 15 Mar 2017 17:16:28 -0400 Subject: Security doubts on 3DES default In-Reply-To: <87zigmztbl.fsf@wheatstone.g10code.de> References: <4960a07f-b61a-4d43-9baa-0075ef2e3230@addere.ch> <024101d29c0c$e1b127f0$a51377d0$@sixdemonbag.org> <87zigmztbl.fsf@wheatstone.g10code.de> Message-ID: <8737eeqlzn.fsf@alice.fifthhorseman.net> On Wed 2017-03-15 07:13:18 -0400, Werner Koch wrote: > On Tue, 14 Mar 2017 21:54, rjh at sixdemonbag.org said: > >> So long as you understand GnuPG will not make any changes that break RFC >> conformance... and dropping SHA1/3DES breaks RFC conformance. > > Well, it is possible to use > > --weak-digest SHA1 --disable-cipher-algo 3DES > > with gpg. and some of us have experimented with running this kind of configuration (at the very least with --weak-digest SHA1) for quite some time now. take rjh's caveat with a grain of salt -- GnuPG's interest is in protecting its users. If the project knows something is bad, we're going to try to protect users from it. that said, data in a store-and-forward format (or for persistent backups) makes it tricky to fully remove something. Should GnuPG refuse to decrypt a symmetrically-encrypted message that uses 3DES ? probably not, but it should probably decline to generate such a thing, in the way that it defaults to generating signatures using SHA256 these days. --dkg From rjh at sixdemonbag.org Thu Mar 16 15:21:57 2017 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Thu, 16 Mar 2017 10:21:57 -0400 Subject: Security doubts on 3DES default In-Reply-To: <8737eeqlzn.fsf@alice.fifthhorseman.net> References: <4960a07f-b61a-4d43-9baa-0075ef2e3230@addere.ch> <024101d29c0c$e1b127f0$a51377d0$@sixdemonbag.org> <87zigmztbl.fsf@wheatstone.g10code.de> <8737eeqlzn.fsf@alice.fifthhorseman.net> Message-ID: <00cb01d29e60$ac185310$0448f930$@sixdemonbag.org> > take rjh's caveat with a grain of salt -- GnuPG's interest is in protecting its > users. If the project knows something is bad, we're going to try to protect > users from it. In my defense, I never said GnuPG wasn't going to try to protect users from dangerous things. I said that until the RFC changes, 3DES and SHA1 will remain in the codebase -- which is, I think, the correct position to take. > probably not, > but it should probably decline to generate such a thing, in the way that it > defaults to generating signatures using SHA256 these days. Why? What's the reasoning for refusing to encrypt using 3DES? I can see "we should refuse to put 3DES in any non-final position in key or cipher preferences" -- that would make sense: it's the cipher of last resort, and putting it in non-final position kind of breaks that guideline -- but I'm unaware of any reason why we should not permit using 3DES as a symmetric cipher. 3DES is slow and obnoxious but it's not unsafe. At 168 bits of key material it's actually stronger than AES128. (I'm discounting the theoretical attacks on 3DES, as they require many orders of magnitude more memory than exist in the entire world.) From peter at digitalbrains.com Thu Mar 16 15:55:53 2017 From: peter at digitalbrains.com (Peter Lebbing) Date: Thu, 16 Mar 2017 15:55:53 +0100 Subject: Security doubts on 3DES default In-Reply-To: <00cb01d29e60$ac185310$0448f930$@sixdemonbag.org> References: <4960a07f-b61a-4d43-9baa-0075ef2e3230@addere.ch> <024101d29c0c$e1b127f0$a51377d0$@sixdemonbag.org> <87zigmztbl.fsf@wheatstone.g10code.de> <8737eeqlzn.fsf@alice.fifthhorseman.net> <00cb01d29e60$ac185310$0448f930$@sixdemonbag.org> Message-ID: <475f90d9-395e-5e48-3120-c78fd972c235@digitalbrains.com> On 16/03/17 15:21, Robert J. Hansen wrote: > -- but I'm unaware of any reason why we should not permit using 3DES as a > symmetric cipher. Perhaps we should either retire ciphers with a 64-bit block length or make OpenPGP mandatorily rekey after a few gigabytes of data, so it's no longer up to the user to be prudent with large amounts of data. In this stage of the game, it might make more sense to just retire those ciphers. Peter. -- I use the GNU Privacy Guard (GnuPG) in combination with Enigmail. You can send me encrypted mail if you want some privacy. My key is available at -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From rjh at sixdemonbag.org Thu Mar 16 16:13:14 2017 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Thu, 16 Mar 2017 11:13:14 -0400 Subject: Security doubts on 3DES default In-Reply-To: <475f90d9-395e-5e48-3120-c78fd972c235@digitalbrains.com> References: <4960a07f-b61a-4d43-9baa-0075ef2e3230@addere.ch> <024101d29c0c$e1b127f0$a51377d0$@sixdemonbag.org> <87zigmztbl.fsf@wheatstone.g10code.de> <8737eeqlzn.fsf@alice.fifthhorseman.net> <00cb01d29e60$ac185310$0448f930$@sixdemonbag.org> <475f90d9-395e-5e48-3120-c78fd972c235@digitalbrains.com> Message-ID: <00f801d29e67$d622f140$8268d3c0$@sixdemonbag.org> > Perhaps we should either retire ciphers with a 64-bit block length or make > OpenPGP mandatorily rekey after a few gigabytes of data, so it's no longer > up to the user to be prudent with large amounts of data. In the next draft of the RFC, I'd like to see 64-bit-block ciphers go the way of the dodo. From wk at gnupg.org Thu Mar 16 20:37:32 2017 From: wk at gnupg.org (Werner Koch) Date: Thu, 16 Mar 2017 20:37:32 +0100 Subject: Security doubts on 3DES default In-Reply-To: <475f90d9-395e-5e48-3120-c78fd972c235@digitalbrains.com> (Peter Lebbing's message of "Thu, 16 Mar 2017 15:55:53 +0100") References: <4960a07f-b61a-4d43-9baa-0075ef2e3230@addere.ch> <024101d29c0c$e1b127f0$a51377d0$@sixdemonbag.org> <87zigmztbl.fsf@wheatstone.g10code.de> <8737eeqlzn.fsf@alice.fifthhorseman.net> <00cb01d29e60$ac185310$0448f930$@sixdemonbag.org> <475f90d9-395e-5e48-3120-c78fd972c235@digitalbrains.com> Message-ID: <8760j9ui6b.fsf@wheatstone.g10code.de> On Thu, 16 Mar 2017 15:55, peter at digitalbrains.com said: > Perhaps we should either retire ciphers with a 64-bit block length or > make OpenPGP mandatorily rekey after a few gigabytes of data, so it's no > longer up to the user to be prudent with large amounts of data. Those who have large amounts of data to encrypt will anyway use a fast cipher and this means AES. Thus the 64 bit block length is in practice only a theoretical problem. A more practical problem is how to protect against arbitrary I/O or storage errors. Thus in the end you will store the data anyway in chunks. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From neal at walfield.org Fri Mar 17 15:02:10 2017 From: neal at walfield.org (Neal H. Walfield) Date: Fri, 17 Mar 2017 15:02:10 +0100 Subject: GnuPG 2.1.19 crashing when listing keys, if tofu-default-policy is "ask" In-Reply-To: <1519215302.20170315003845@riseup.net> References: <1519215302.20170315003845@riseup.net> Message-ID: <87wpbo0zod.wl-neal@walfield.org> Hi, At Wed, 15 Mar 2017 00:38:45 +0000, MFPA wrote: > I have been having GnuPG crash with the following message when listing > keys:- > > gpg --list-keys > gpg: Ohhhh jeeee: Assertion "conflict_set" in get_trust failed > (/home/wk/b-w32/speedo/PLAY-release/gnupg-w32-2.1.19/g10/tofu.c:2787) > This application has requested the Runtime to terminate it in an unusual > way. > Please contact the application's support team for more information. > > > > An internet search on the message leads me to a Debian bug report [0]. > > I am using GnuPG version 2.1.19 on Windows, running the pre-compiled > Windows binaries linked from the release announcement. > > I have the "with-fingerprint" option in gpg.conf; commenting it out > makes no difference. > > I also have "tofu-default-policy ask"; changing "ask" to "unknown" > makes the problem go away. Thanks for the report and the analysis. I've just (hopefully) fixed this in b1106b4. Sorry about that! :) Neal From paolo.bolzoni.brown at gmail.com Thu Mar 16 23:47:01 2017 From: paolo.bolzoni.brown at gmail.com (Paolo Bolzoni) Date: Thu, 16 Mar 2017 23:47:01 +0100 Subject: Simple program to get sha256 hash Message-ID: Dear list, Today I wanted to play a bit with libgcrypt and I wanted to make a small program to return the sha256 hash of a string passed as argument. The program compiles, links, and gives an output. However, the output is different than what I get using sha256sum from coreutils! Here is what I see in my shell: $ gcc -o ssha ./hash.cpp -lgcrypt $ ./ssha blablabla a6898dd93b4c6a87e978aea8547fdc3901b7b94d96636e03d5a6194f4491c571 $ sha256sum <<< 'blablabla' a5edca3a5b8fb54ae61d236a5274626ba6a38781573e02202000158faa707191 - $ hash.cpp contains the code I copied in the bottom of the email. What am I missing? Isn't expected to have the same hash code? Yours faithfully, Paolo ---------- >8 #include #include int main(int argc, char** argv) { if (argc < 2) return 1; gcry_md_hd_t context; gcry_md_open(&context, GCRY_MD_SHA256, 0); char* c = argv[1]; while (*c != '\0') { ++c; gcry_md_putc(context, *c); } unsigned char* csha = gcry_md_read(context, GCRY_MD_SHA256); for (int i = 0; i < 32; ++i) { printf("%02x", csha[i]); } printf("\n"); gcry_md_close(context); } From Pankaj.Chaurasia at smartusys.com Fri Mar 17 07:02:46 2017 From: Pankaj.Chaurasia at smartusys.com (Pankaj Kumar. Chaurasia) Date: Fri, 17 Mar 2017 06:02:46 +0000 Subject: Help Needed: I am able to decrypt file when I run package manually but when I run through sql sever agent, it is not decrypting. Message-ID: Any clue guys. I am using version 2.3.3. Thanks & Regards, Pankaj K Chaurasia Sr. Database Developer Smart Utility Systems 0120-4208528 (O) | +91- 8109510013 (M) | +91- 9406929510 (M) pankaj.chaurasia at smartusys.com | www.smartusys.com [csWeekSIg0.1.3] [facebook][linkedin] [twitter] [google] This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. P Please consider the environment before printing this email. From: Pankaj Kumar. Chaurasia Sent: Friday, March 10, 2017 2:53 PM To: 'gnupg-users at gnupg.org' Subject: Help Needed: I am able to decrypt file when I run package manually but when I run through sql sever agent, it is not decrypting. Hello Gnupg Users, I am writing this mail regarding the issue facing to decrypt file through my SSIS Package. Below is the command I am using: gpg2.exe --batch --yes --status-fd 2 --passphrase-fd 0 --armor --output E:\File.csv --decrypt E:\File.pgp When I run my SSIS package manually through visual studio it is decrypting the file properly. When I deploying the package on the same machine it is not decrypting. After spending to much time I come to know that the reason behind this is, I have imported the public key using command line, so it is imported for my user as I login on that machine with my windows user. But SQL Server agent job runs with MSSQL Agent Service account so I need to import the key for that service account. Could you guys please let me know how to import the public key for that account as I cannot login with that Service account. Thanks in Advance. Thanks & Regards, Pankaj K Chaurasia Sr. Database Developer Smart Utility Systems 0120-4208528 (O) | +91- 8109510013 (M) | +91- 9406929510 (M) pankaj.chaurasia at smartusys.com | www.smartusys.com [https://www.smartusys.com/emails/ISGW/signature/ISGW_EmailBanner.png] [facebook][linkedin] [twitter] [google] This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. P Please consider the environment before printing this email. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 76121 bytes Desc: image005.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image006.png Type: image/png Size: 1147 bytes Desc: image006.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image007.png Type: image/png Size: 1240 bytes Desc: image007.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image008.png Type: image/png Size: 1270 bytes Desc: image008.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image009.png Type: image/png Size: 1669 bytes Desc: image009.png URL: From dougb at dougbarton.us Fri Mar 17 07:34:31 2017 From: dougb at dougbarton.us (Doug Barton) Date: Thu, 16 Mar 2017 23:34:31 -0700 Subject: ADMIN: Some mail addresses are now rewritten In-Reply-To: <3e613056-8b46-4ef2-7466-164de910cbac@cse.ucdavis.edu> References: <43387B6C-C35B-4448-8B55-35763D94CAC4@microsoft.com> <87varf911e.fsf@wheatstone.g10code.de> <3e613056-8b46-4ef2-7466-164de910cbac@cse.ucdavis.edu> Message-ID: <758a5068-992b-ff5a-9be9-f181c6118748@dougbarton.us> The appropriate place is the IETF, and/or lists related to the development of mailing list software. Doug On 03/15/2017 08:46 PM, Bill Broadley via Gnupg-users wrote: > But > finding a place that discusses standards that impact so many different pieces is > tricky. From dougb at dougbarton.us Fri Mar 17 08:29:55 2017 From: dougb at dougbarton.us (Doug Barton) Date: Fri, 17 Mar 2017 00:29:55 -0700 Subject: Question about signing keys and trust. In-Reply-To: <562649904.943824.1489612477344@mail.yahoo.com> References: <562649904.943824.1489612477344.ref@mail.yahoo.com> <562649904.943824.1489612477344@mail.yahoo.com> Message-ID: <790550b5-b7a5-d65b-d663-79a73e3715fb@dougbarton.us> On 03/15/2017 02:14 PM, Jamie H. via Gnupg-users wrote: > Hello! > > It's been a few years since I've messed with gpg, but I have an > application that needs something kind of like distributed groups. > > Lets say I have: "key group" (which is owned by who-cares, it's a > public key only that represents a group of people) The fact that more than one person has access to the key seems superfluous to your use case. > I have a person, lets say William Smith who has his key signed by > who-cares > > William Smith then signs Betty Boop with his key. > > > So William Smith and Betty Boop are sort of like members of "key > group" because Betty Boop has a signature by someone who has their > key signed by the key group, and if Betty Boop signs someone, up to > n-depth, then those people become members of "key group". No one has > authority to add or remove people, except other members of the same > group. This very unclear, but perhaps you have a more detailed implementation plan in mind, and this is just a summary. > ... fast forward .. > > In the application, lets say it's a spam fighting tool, a Betty Boop > marks a message as spam. > > I trust members of "key group" to mark spam, but I don't trust them > with everything, just marking spam, so the spam message is deleted. > > Popeye, who is a member of "alien group" marks something as spam too, > but since popeye doesn't have a key signed by someone in "key group", > I do not trust him to flag messages as spam, so I just ignore it. This bit is clear, but if a spam detection tool is what you're developing, sharing the responsibility for flagging something as spam is a very bad idea. There has been a lot of e-ink spilled on this problem from all of the major mail providers. Essentially, users are incredibly bad at reliably tagging *their own mail* as spam, or not-spam. At best an individual's opinion on whether something is spam or not should be taken as one lightly weighted value in the overall determination. Developing a complex system of trusting users' opinions on this topic would be a waste of your time. > Problem is I can't see how! Is there a way I can look at someones > public key and (without importing anything into my personal key > files) list in a kind of chain fashion how many other signers there > were? Sort of. You can use --list-packets, but it would be very painful. It would actually be easier to import these keys onto their own rings using the no-default-keyring option. You probably also want to use no-import-clean option so that you can see all the signatures, including those from keys you have not already imported yet. It's not *too* complicated to do this kind of stuff, but you have to really read the man page and understand how the pieces fit together. I would also recommend that you use GNUPGHOME to create a separate environment from your own personal one. > I admit, GPG probably wasn't designed for this, and I don't really > get the whole trust level thing.. and if it's impossible or > impractical I'll find another way, but it would be convenient. Trust is completely different from what you're describing here. (Unfortunately the term 'trust' is badly abused in PGP circles, and has at least 4 different meanings depending on context.) You don't care about the trust *level* at all. Your only concern is whether or not the key you're examining is included in the web of trust for your tool. If your "group key" that you described above is the apex of the tree, you want to examine the key you have to see if it has a chain of trust back to that apex key. For keys which are close to the top, that would not be too expensive of an operation. But as your pool grows it could become quite expensive, as you'd have to check if signatures/keys have been revoked, expired, etc. Another problem you have is that there is no way for the administrator of the system to decertify a user (kick them out of the group, so to speak). You would require the cooperation of every user in every chain of trust back to the apex key, and every other member of the group not to add them back. As you point out, PGP is not really designed for this sort of thing. :) That said, you may be able to learn some stuff from the software for this site: http://pgp2.cs.uu.nl/wotsap/ hope this helps, Doug From sivmu at web.de Fri Mar 17 22:39:38 2017 From: sivmu at web.de (sivmu at web.de) Date: Fri, 17 Mar 2017 22:39:38 +0100 Subject: dirmngr failes with missing file Message-ID: When gpg -recv-key ID is used with the line hkps://hkps.pool.sks-keyservers.net enabled in dirmngr.conf, it failes with an error message saying dirmngr not found. The solution to this is to add the empty file ~/.gnupg/dirmngr_ldapservers.conf Shouldn't this be added automatically to avoid this error? From ralph at inputplus.co.uk Fri Mar 17 23:15:43 2017 From: ralph at inputplus.co.uk (Ralph Corderoy) Date: Fri, 17 Mar 2017 22:15:43 +0000 Subject: Simple program to get sha256 hash In-Reply-To: References: Message-ID: <20170317221543.8C5C01F968@orac.inputplus.co.uk> Hi Paolo, > $ gcc -o ssha ./hash.cpp -lgcrypt > $ ./ssha blablabla > a6898dd93b4c6a87e978aea8547fdc3901b7b94d96636e03d5a6194f4491c571 You're feeding it nine bytes here. > $ sha256sum <<< 'blablabla' > a5edca3a5b8fb54ae61d236a5274626ba6a38781573e02202000158faa707191 - And ten bytes here. $ wc -c << I copied my key to a OpenPGP card and was able to create signatures and authentication via SSH using the card. Now moving the the Mac I am stuck with pinentry-mac, because it keeps asking me for another card. gpg --delete-secret-keys 0x64C2F99E904F1906 gpg2 --card-status gpg2 --clearsign /etc/hosts pinentry-mac brings up a dialogue box, asking to insert the card with the serial number D2760001240102000006030374100000. The Application ID (is this the serial number?) do not match. gpg2 --card-status Reader ...........: Gemalto PC Twin Reader Application ID ...: D276000124010201000500004EBD0000 Version ..........: 2.1 Manufacturer .....: ZeitControl Serial number ....: 00004EBD Name of cardholder: Rainer Hoerbe Language prefs ...: de Sex ..............: male URL of public key : [not set] Login data .......: [not set] Signature PIN ....: forced Key attributes ...: rsa2048 rsa2048 rsa2048 Max. PIN lengths .: 32 32 32 PIN retry counter : 3 0 3 Signature counter : 2 Signature key ....: 7D23 36BF A95F F788 4C80 B7DA 64C2 F99E 904F 1906 created ....: 2017-01-30 14:47:18 Encryption key....: [none] Authentication key: [none] General key info..: pub rsa2048/0x64C2F99E904F1906 2017-01-30 Rainer Hoerbe (Identinetics GmbH) sec> rsa2048/0x64C2F99E904F1906 created: 2017-01-30 expires: 2027-01-28 card-no: 0006 03037410 What could be the problem? Thanks, Rainer From paolo.bolzoni.brown at gmail.com Sat Mar 18 09:18:59 2017 From: paolo.bolzoni.brown at gmail.com (Paolo Bolzoni) Date: Sat, 18 Mar 2017 09:18:59 +0100 Subject: Simple program to get sha256 hash In-Reply-To: <20170317221543.8C5C01F968@orac.inputplus.co.uk> References: <20170317221543.8C5C01F968@orac.inputplus.co.uk> Message-ID: On Fri, Mar 17, 2017 at 11:15 PM, Ralph Corderoy wrote: > Hi Paolo, > >> $ gcc -o ssha ./hash.cpp -lgcrypt >> $ ./ssha blablabla >> a6898dd93b4c6a87e978aea8547fdc3901b7b94d96636e03d5a6194f4491c571 > > You're feeding it nine bytes here. > >> $ sha256sum <<< 'blablabla' >> a5edca3a5b8fb54ae61d236a5274626ba6a38781573e02202000158faa707191 - > > And ten bytes here. > > $ wc -c << 10 > $ od -c << 0000000 b l a b l a b l a \n > 0000012 > $ > > Further, you're incrementing the pointer before dereferencing. > > $ printf 'lablabla\0' | od -c > 0000000 l a b l a b l a \0 > 0000011 > $ printf 'lablabla\0' | sha256sum > a6898dd93b4c6a87e978aea8547fdc3901b7b94d96636e03d5a6194f4491c571 - > $ > > -- > Cheers, Ralph. > https://plus.google.com/+RalphCorderoy Thanks everyone, it's dead on! $ echo -n 'blablabla' | sha256sum 492f3f38d6b5d3ca859514e250e25ba65935bcdd9f4f40c124b773fe536fee7d - $ ./a.out blablabla 492f3f38d6b5d3ca859514e250e25ba65935bcdd9f4f40c124b773fe536fee7d using echo -n "blablabla" gives indeed the same result! The flipped gcry_md_putc and ++c happened somewhat while I copied the code in the email, but indeed was another problem. Thanks again, Cheers Paolo From calmstorm at posteo.de Sun Mar 19 03:55:23 2017 From: calmstorm at posteo.de (zap) Date: Sat, 18 Mar 2017 22:55:23 -0400 Subject: help Message-ID: <58CDF31B.4080407@posteo.de> Does anyone know how to change the default ciphers in gnupg modern to their maximum security level? I am curious because I may soon be in a position to use it. Ubuntu 16.04 has this option as does other ubuntu 16.04 based derivatives... From rjh at sixdemonbag.org Sun Mar 19 22:01:13 2017 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Sun, 19 Mar 2017 17:01:13 -0400 Subject: help In-Reply-To: <58CDF31B.4080407@posteo.de> References: <58CDF31B.4080407@posteo.de> Message-ID: <08881ec9-7a93-0829-32f3-97f531853d0b@sixdemonbag.org> > Does anyone know how to change the default ciphers in gnupg modern to > their maximum security level? To your gpg.conf file add the line, personal-cipher-preferences AES256 CAMELLIA256 TWOFISH ... and you'll generate 256-bit encrypted traffic whenever possible. From calmstorm at posteo.de Mon Mar 20 03:12:50 2017 From: calmstorm at posteo.de (zap) Date: Sun, 19 Mar 2017 22:12:50 -0400 Subject: I figured out how to change the algorithms, Message-ID: <58CF3AA2.8030707@posteo.de> gpg --edit-key (user id) then showpref and then setpref with AES256 SHA512 ZLIB MDC the only thing, is that after the installing of gnupg modern I could not use enigmail properly in icedove... not sure why. I am using a ubuntu 14 derivative Is there a way to fix this without getting rid of gnupg modern? From rjh at sixdemonbag.org Mon Mar 20 06:29:30 2017 From: rjh at sixdemonbag.org (Robert J. Hansen) Date: Mon, 20 Mar 2017 01:29:30 -0400 Subject: I figured out how to change the algorithms, In-Reply-To: <58CF3AA2.8030707@posteo.de> References: <58CF3AA2.8030707@posteo.de> Message-ID: <0ad6b764-9416-e89d-6ee3-8bd22d70801a@sixdemonbag.org> No, you didn't figure out how to change the algorithms. Key preferences are the capabilities you advertise to the world. What you've done is told the world, "I only understand AES256, 3DES, SHA512, and SHA1." Which is great if the entire world understands AES256 and SHA512 -- but the moment you have a correspondent who doesn't (or who refuses to use it) you'll silently degrade to 3DES or SHA1. Imagine you're corresponding with someone who doesn't trust AES256, thinking it's tainted by association with NIST. (This is crazy talk, but unfortunately common.) They've configured GnuPG to never use AES256, but to prefer TWOFISH and CAMELLIA256 instead. Despite the fact your GnuPG is plenty capable of CAMELLIA256 and TWOFISH, since you're not advertising that capability your correspondent's GnuPG will silently drop to 3DES. Notably, GnuPG never looks at your own key preferences. That's what you advertise to the world as your capabilities. GnuPG looks to personal-cipher-preferences, et al, to determine which algos to use when creating traffic, which is why you were advised to set personal-cipher-preferences, etc., in your gpg.conf. If you want to generate 256-bit traffic, put AES256, TWOFISH, and CAMELLIA256 in your personal-cipher-preferences. Which is exactly what you were advised to do earlier. From calmstorm at posteo.de Mon Mar 20 10:56:27 2017 From: calmstorm at posteo.de (zap) Date: Mon, 20 Mar 2017 05:56:27 -0400 Subject: I figured out how to change the algorithms, In-Reply-To: <0ad6b764-9416-e89d-6ee3-8bd22d70801a@sixdemonbag.org> References: <58CF3AA2.8030707@posteo.de> <0ad6b764-9416-e89d-6ee3-8bd22d70801a@sixdemonbag.org> Message-ID: <58CFA74B.1090901@posteo.de> Okay, I was doing this to ecnrypt my files, not emails for the most part... I did however wonder, what you actually said, because I had pgp encryption on and for some reason I couldn't read it through enigmail. My apologies. On 03/20/2017 01:29 AM, Robert J. Hansen wrote: > No, you didn't figure out how to change the algorithms. > > Key preferences are the capabilities you advertise to the world. What > you've done is told the world, "I only understand AES256, 3DES, SHA512, > and SHA1." Which is great if the entire world understands AES256 and > SHA512 -- but the moment you have a correspondent who doesn't (or who > refuses to use it) you'll silently degrade to 3DES or SHA1. > > Imagine you're corresponding with someone who doesn't trust AES256, > thinking it's tainted by association with NIST. (This is crazy talk, > but unfortunately common.) They've configured GnuPG to never use > AES256, but to prefer TWOFISH and CAMELLIA256 instead. Despite the fact > your GnuPG is plenty capable of CAMELLIA256 and TWOFISH, since you're > not advertising that capability your correspondent's GnuPG will silently > drop to 3DES. > > Notably, GnuPG never looks at your own key preferences. That's what you > advertise to the world as your capabilities. GnuPG looks to > personal-cipher-preferences, et al, to determine which algos to use when > creating traffic, which is why you were advised to set > personal-cipher-preferences, etc., in your gpg.conf. > > If you want to generate 256-bit traffic, put AES256, TWOFISH, and > CAMELLIA256 in your personal-cipher-preferences. Which is exactly what > you were advised to do earlier. > > > _______________________________________________ > Gnupg-users mailing list > Gnupg-users at gnupg.org > http://lists.gnupg.org/mailman/listinfo/gnupg-users > From szczepan at nitrokey.com Mon Mar 20 11:45:19 2017 From: szczepan at nitrokey.com (Szczepan Zalega | Nitrokey) Date: Mon, 20 Mar 2017 11:45:19 +0100 Subject: Generating RSA-4096 on Nitrokey Pro In-Reply-To: References: Message-ID: On 03/20/2017 10:39 AM, Szczepan Zalega | Nitrokey wrote: > As far as I remember it worked on Ubuntu 16.04 with GPG 2.0.x. I use now > Ubuntu 16.10 with GPG 2.1.15. Logs attached. I have just checked it on Ubuntu 16.04.2-server. It has a GPG with version 2.1.11 (not 2.0.x, my mistake) and scdaemon in same version. The keys have been generated successfully although it took about 15 minutes to complete. [1] http://paste.ubuntu.com/24214504/ - run log on GPG 2.1.11 / Ubuntu 16.04-2-server - another attempt -- Best regards, Szczepan -------------- next part -------------- A non-text attachment was scrubbed... Name: u16.04.2-server-nkpro0.7-rsa4096-run.log_2.scdaemon.gz Type: application/gzip Size: 45953 bytes Desc: not available URL: -------------- next part -------------- sz at ubuntu:~/.gnupg? gpg2 --card-status Reader ...........: 20A0:4108:0000319E0000000000000000:0 Application ID ...: D27600012401020100050000319E0000 Version ..........: 2.1 Manufacturer .....: ZeitControl Serial number ....: 0000319E Name of cardholder: [not set] Language prefs ...: de Sex ..............: unspecified URL of public key : [not set] Login data .......: [not set] Signature PIN ....: not forced Key attributes ...: rsa4096 rsa4096 rsa4096 Max. PIN lengths .: 32 32 32 PIN retry counter : 3 0 3 Signature counter : 4 Signature key ....: 8001 0607 0C35 871D 8059 4BEF F83E 08C1 88EE F49F created ....: 2017-03-20 09:56:45 Encryption key....: B120 6769 0ABD 2532 B05A 691B 485B 53AD 1FB6 C046 created ....: 2017-03-20 09:56:45 Authentication key: 0A6C 7707 9326 2A25 2570 EAA6 9249 30CF C3D6 2787 created ....: 2017-03-20 09:56:45 General key info..: pub rsa4096/88EEF49F 2017-03-20 nkpro at 4096 (nkpro at 4096) sec> rsa4096/88EEF49F created: 2017-03-20 expires: 2017-03-21 card-no: 0005 0000319E ssb> rsa4096/C3D62787 created: 2017-03-20 expires: 2017-03-21 card-no: 0005 0000319E ssb> rsa4096/1FB6C046 created: 2017-03-20 expires: 2017-03-21 card-no: 0005 0000319E sz at ubuntu:~/.gnupg? tail scdaemon.log 2017-03-20 11:16:50 scdaemon[23560] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-20 11:16:50 scdaemon[23560] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-20 11:16:51 scdaemon[23560] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-20 11:16:51 scdaemon[23560] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-20 11:16:51 scdaemon[23560] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-20 11:16:51 scdaemon[23560] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-20 11:16:52 scdaemon[23560] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-20 11:16:52 scdaemon[23560] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-20 11:16:52 scdaemon[23560] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-20 11:16:52 scdaemon[23560] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 sz at ubuntu:~/.gnupg? gpg2 --card-edit Reader ...........: 20A0:4108:0000319E0000000000000000:0 Application ID ...: D27600012401020100050000319E0000 Version ..........: 2.1 Manufacturer .....: ZeitControl Serial number ....: 0000319E Name of cardholder: [not set] Language prefs ...: de Sex ..............: unspecified URL of public key : [not set] Login data .......: [not set] Signature PIN ....: not forced Key attributes ...: rsa4096 rsa4096 rsa4096 Max. PIN lengths .: 32 32 32 PIN retry counter : 3 0 3 Signature counter : 4 Signature key ....: 8001 0607 0C35 871D 8059 4BEF F83E 08C1 88EE F49F created ....: 2017-03-20 09:56:45 Encryption key....: B120 6769 0ABD 2532 B05A 691B 485B 53AD 1FB6 C046 created ....: 2017-03-20 09:56:45 Authentication key: 0A6C 7707 9326 2A25 2570 EAA6 9249 30CF C3D6 2787 created ....: 2017-03-20 09:56:45 General key info..: pub rsa4096/88EEF49F 2017-03-20 nkpro at 4096 (nkpro at 4096) sec> rsa4096/88EEF49F created: 2017-03-20 expires: 2017-03-21 card-no: 0005 0000319E ssb> rsa4096/C3D62787 created: 2017-03-20 expires: 2017-03-21 card-no: 0005 0000319E ssb> rsa4096/1FB6C046 created: 2017-03-20 expires: 2017-03-21 card-no: 0005 0000319E gpg/card> admin Admin commands are allowed gpg/card> generate Make off-card backup of encryption key? (Y/n) n gpg: Note: keys are already stored on the card! Replace existing keys? (y/N) y Please note that the factory settings of the PINs are PIN = '123456' Admin PIN = '12345678' You should change them using the command --change-pin What keysize do you want for the Signature key? (4096) What keysize do you want for the Encryption key? (4096) What keysize do you want for the Authentication key? (4096) Please specify how long the key should be valid. 0 = key does not expire = key expires in n days w = key expires in n weeks m = key expires in n months y = key expires in n years Key is valid for? (0) 1 Key expires at Tue 21 Mar 2017 11:17:12 AM CET Is this correct? (y/N) y GnuPG needs to construct a user ID to identify your key. Real name: nkpro4096-2 at 16.04.2-server Email address: nkpro4096-2 at 16.04.2-server Comment: nkpro4096-2 at 16.04.2-server You selected this USER-ID: "nkpro4096-2 at 16.04.2-server (nkpro4096-2 at 16.04.2-server) " Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? O gpg: key 47AAA5F9 marked as ultimately trusted gpg: revocation certificate stored as '/home/sz/.gnupg/openpgp-revocs.d/C2B5317381CEC39AFE3C9C0B7C92 2A3E47AAA5F9.rev' public and secret key created and signed. gpg: checking the trustdb gpg: marginals needed: 3 completes needed: 1 trust model: PGP gpg: depth: 0 valid: 2 signed: 0 trust: 0-, 0q, 0n, 0m, 0f, 2u gpg: next trustdb check due at 2017-03-21 gpg/card> pub rsa4096/47AAA5F9 2017-03-20 [S] [expires: 2017-03-21] Key fingerprint = C2B5 3173 81CE C39A FE3C 9C0B 7C92 2A3E 47AA A5F9 uid [ultimate] nkpro4096-2 at 16.04.2-server (nkpro4096-2 at 16.04.2-server) sub rsa4096/5F6FCE2B 2017-03-20 [] [expires: 2017-03-21] sub rsa4096/2FF57263 2017-03-20 [] [expires: 2017-03-21] sz at ubuntu:~/.gnupg? gpg2 --card-status Reader ...........: 20A0:4108:0000319E0000000000000000:0 Application ID ...: D27600012401020100050000319E0000 Version ..........: 2.1 Manufacturer .....: ZeitControl Serial number ....: 0000319E Name of cardholder: [not set] Language prefs ...: de Sex ..............: unspecified URL of public key : [not set] Login data .......: [not set] Signature PIN ....: not forced Key attributes ...: rsa4096 rsa4096 rsa4096 Max. PIN lengths .: 32 32 32 PIN retry counter : 3 0 3 Signature counter : 4 Signature key ....: C2B5 3173 81CE C39A FE3C 9C0B 7C92 2A3E 47AA A5F9 created ....: 2017-03-20 10:17:37 Encryption key....: C2BF AD4B 5A95 1D5A D19D D7F2 D1B4 4EB9 2FF5 7263 created ....: 2017-03-20 10:17:37 Authentication key: A736 1236 4272 9B6E 459A 60A8 BFA5 3830 5F6F CE2B created ....: 2017-03-20 10:17:37 General key info..: pub rsa4096/47AAA5F9 2017-03-20 nkpro4096-2 at 16.04.2-server (nkpro4096-2 at 16.04.2 -server) sec> rsa4096/47AAA5F9 created: 2017-03-20 expires: 2017-03-21 card-no: 0005 0000319E ssb> rsa4096/5F6FCE2B created: 2017-03-20 expires: 2017-03-21 card-no: 0005 0000319E ssb> rsa4096/2FF57263 created: 2017-03-20 expires: 2017-03-21 card-no: 0005 0000319E sz at ubuntu:~/.gnupg? ls dirmngr.conf openpgp-revocs.d pubring.kbx reader_0.status scdaemon.log S.scdaemon gpg.conf private-keys-v1.d pubring.kbx~ scdaemon.conf S.gpg-agent trustdb.gpg sz at ubuntu:~/.gnupg? pkill scdaemon sz at ubuntu:~/.gnupg? less scdaemon. scdaemon.: No such file or directory 1 sz at ubuntu:~/.gnupg? less scdaemon.log sz at ubuntu:~/.gnupg? less scdaemon.log sz at ubuntu:~/.gnupg? From szczepan at nitrokey.com Mon Mar 20 10:39:20 2017 From: szczepan at nitrokey.com (Szczepan Zalega | Nitrokey) Date: Mon, 20 Mar 2017 10:39:20 +0100 Subject: Generating RSA-4096 on Nitrokey Pro Message-ID: Hi! I would like to generate RSA-4096 key on Nitrokey Pro v0.7 device. During the generation error is shown: ``` gpg: key generation failed: Card error Key generation failed: Card error gpg: error setting forced signature PIN flag: Input/output error ``` In scdaemon.log I see that libusb reports time-outs: ``` 2017-03-17 20:26:51 scdaemon[16299] DBG: ccid-driver: usb_bulk_read error: LIBUSB_ERROR_TIMEOUT 2017-03-17 20:26:51 scdaemon[16299] ccid_transceive failed: (0x1000a) 2017-03-17 20:26:51 scdaemon[16299] apdu_send_simple(0) failed: card I/O error ``` How could I fix it? As far as I remember it worked on Ubuntu 16.04 with GPG 2.0.x. I use now Ubuntu 16.10 with GPG 2.1.15. Logs attached. Please keep me on CC when possible. -- Best regards, Szczepan -------------- next part -------------- A non-text attachment was scrubbed... Name: gpg2.1-pro-4096.log Type: text/x-log Size: 4861 bytes Desc: not available URL: -------------- next part -------------- 2017-03-17 20:22:53 scdaemon[16299] listening on socket '/run/user/1000/gnupg/S.scdaemon' 2017-03-17 20:22:53 scdaemon[16299] handler for fd -1 started 2017-03-17 20:22:53 scdaemon[16299] DBG: enter: apdu_open_reader: portstr=(null) 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: using CCID reader 0 (ID=20A0:4108:0000319E0000000000000000:0) 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: idVendor: 20A0 idProduct: 4108 bcdDevice: 0100 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: ChipCard Interface Descriptor: 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: bLength 54 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: bDescriptorType 33 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: bcdCCID 1.10 (Warning: Only accurate for version 1.0) 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: nMaxSlotIndex 0 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: bVoltageSupport 2 3.0V 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: dwProtocols 2 T=1 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: dwDefaultClock 3600 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: dwMaxiumumClock 3600 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: bNumClockSupported 0 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: dwDataRate 9677 bps 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: dwMaxDataRate 116129 bps 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: bNumDataRatesSupp. 0 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: dwMaxIFSD 254 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: dwSyncProtocols 00000000 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: dwMechanical 00000000 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: dwFeatures 000104BA 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: Auto configuration based on ATR (assumes auto voltage) 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: Auto voltage selection 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: Auto clock change 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: Auto baud rate change 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: Auto PPS made by CCID 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: Auto IFSD exchange 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: TPDU level exchange 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: dwMaxCCIDMsgLen 271 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: bClassGetResponse 00 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: bClassEnvelope 00 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: wlcdLayout none 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: bPINSupport 0 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: bMaxCCIDBusySlots 1 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_IccPowerOn: 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 0 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 1 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: bPowerSelect ......: 0x00 (auto) 2017-03-17 20:22:53 scdaemon[16299] DBG: ccid-driver: [0008] 00 00 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 21 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 1 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: [0010] 3B DA 18 FF 81 B1 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: [0016] FE 75 1F 03 00 31 C5 73 C0 01 40 00 90 00 0C 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_SetParameters: 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 7 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 2 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: bProtocolNum ......: 0x01 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: [0008] 00 00 18 10 FF 75 00 FE 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: [0016] 00 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_Parameters: 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 7 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 2 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: protocol ..........: T=1 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: bmFindexDindex ....: 00 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: bmTCCKST1 .........: 00 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: bGuardTimeT1 ......: 00 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: bmWaitingIntegersT1: 00 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: bClockStop ........: 00 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: bIFSC .............: 0 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: bNadValue .........: 0 2017-03-17 20:22:54 scdaemon[16299] reader slot 0: using ccid driver 2017-03-17 20:22:54 scdaemon[16299] slot 0: ATR=3B DA 18 FF 81 B1 FE 75 1F 03 00 31 C5 73 C0 01 40 00 90 00 0C 2017-03-17 20:22:54 scdaemon[16299] DBG: leave: apdu_open_reader => slot=0 [ccid] 2017-03-17 20:22:54 scdaemon[16299] DBG: chan_5 -> OK GNU Privacy Guard's Smartcard server ready 2017-03-17 20:22:54 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:22:54 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:22:54 scdaemon[16299] updating reader 0 (0) status: 0x0000->0x0007 (0->1) 2017-03-17 20:22:54 scdaemon[16299] DBG: chan_5 <- GETINFO socket_name 2017-03-17 20:22:54 scdaemon[16299] DBG: chan_5 -> D /run/user/1000/gnupg/S.scdaemon 2017-03-17 20:22:54 scdaemon[16299] DBG: chan_5 -> OK 2017-03-17 20:22:54 scdaemon[16299] DBG: chan_5 <- OPTION event-signal=12 2017-03-17 20:22:54 scdaemon[16299] DBG: chan_5 -> OK 2017-03-17 20:22:54 scdaemon[16299] DBG: chan_5 <- GETINFO version 2017-03-17 20:22:54 scdaemon[16299] DBG: chan_5 -> D 2.1.15 2017-03-17 20:22:54 scdaemon[16299] DBG: chan_5 -> OK 2017-03-17 20:22:54 scdaemon[16299] DBG: chan_5 <- SERIALNO openpgp 2017-03-17 20:22:54 scdaemon[16299] DBG: enter: apdu_connect: slot=0 2017-03-17 20:22:54 scdaemon[16299] DBG: leave: apdu_connect => sw=0x0 2017-03-17 20:22:54 scdaemon[16299] DBG: send apdu: c=00 i=A4 p1=00 p2=0C lc=2 le=-1 em=0 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_IccPowerOn: 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 0 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 6 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: bPowerSelect ......: 0x00 (auto) 2017-03-17 20:22:54 scdaemon[16299] DBG: ccid-driver: [0008] 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 21 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 6 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 3B DA 18 FF 81 B1 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] FE 75 1F 03 00 31 C5 73 C0 01 40 00 90 00 0C 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_SetParameters: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 7 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 7 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bProtocolNum ......: 0x01 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0008] 00 00 18 10 FF 75 00 FE 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_Parameters: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 7 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 7 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: protocol ..........: T=1 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bmFindexDindex ....: 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bmTCCKST1 .........: 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bGuardTimeT1 ......: 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bmWaitingIntegersT1: 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bClockStop ........: 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bIFSC .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bNadValue .........: 0 2017-03-17 20:22:55 scdaemon[16299] reader slot 0: using ccid driver 2017-03-17 20:22:55 scdaemon[16299] slot 0: ATR=3B DA 18 FF 81 B1 FE 75 1F 03 00 31 C5 73 C0 01 40 00 90 00 0C 2017-03-17 20:22:55 scdaemon[16299] DBG: raw apdu: 00 A4 00 0C 02 3F 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 11 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 8 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 07 00 A4 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 0C 02 3F 00 92 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 6 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 8 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 02 6B 00 69 2017-03-17 20:22:55 scdaemon[16299] DBG: response: sw=6B00 datalen=0 2017-03-17 20:22:55 scdaemon[16299] DBG: send apdu: c=00 i=A4 p1=04 p2=00 lc=6 le=-1 em=0 2017-03-17 20:22:55 scdaemon[16299] DBG: raw apdu: 00 A4 04 00 06 D2 76 00 01 24 01 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 15 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 9 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 0B 00 A4 04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 00 06 D2 76 00 01 24 01 6D 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 6 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 9 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 02 90 00 D2 2017-03-17 20:22:55 scdaemon[16299] DBG: response: sw=9000 datalen=0 2017-03-17 20:22:55 scdaemon[16299] DBG: dump: 2017-03-17 20:22:55 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=00 p2=4F lc=-1 le=256 em=0 2017-03-17 20:22:55 scdaemon[16299] DBG: raw apdu: 00 CA 00 4F 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 10 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 05 00 CA 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 4F 00 80 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 22 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 10 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 12 D2 76 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 01 24 01 02 01 00 05 00 00 31 9E 00 00 90 00 AB 2017-03-17 20:22:55 scdaemon[16299] DBG: response: sw=9000 datalen=16 2017-03-17 20:22:55 scdaemon[16299] DBG: dump: D2 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 2017-03-17 20:22:55 scdaemon[16299] AID: D2 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=5F p2=52 lc=-1 le=256 em=0 2017-03-17 20:22:55 scdaemon[16299] DBG: raw apdu: 00 CA 5F 52 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 11 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 05 00 CA 5F 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 52 00 82 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 16 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 11 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 0C 00 31 C5 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 73 C0 01 40 05 90 00 90 00 4F 2017-03-17 20:22:55 scdaemon[16299] DBG: response: sw=9000 datalen=10 2017-03-17 20:22:55 scdaemon[16299] DBG: dump: 00 31 C5 73 C0 01 40 05 90 00 2017-03-17 20:22:55 scdaemon[16299] Historical Bytes: 00 31 C5 73 C0 01 40 05 90 00 2017-03-17 20:22:55 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=00 p2=C4 lc=-1 le=256 em=0 2017-03-17 20:22:55 scdaemon[16299] DBG: raw apdu: 00 CA 00 C4 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 12 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 05 00 CA 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] C4 00 0B 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 13 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 12 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 09 00 20 20 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 20 03 00 03 90 00 B9 2017-03-17 20:22:55 scdaemon[16299] DBG: response: sw=9000 datalen=7 2017-03-17 20:22:55 scdaemon[16299] DBG: dump: 00 20 20 20 03 00 03 2017-03-17 20:22:55 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=00 p2=6E lc=-1 le=256 em=0 2017-03-17 20:22:55 scdaemon[16299] DBG: raw apdu: 00 CA 00 6E 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 13 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 05 00 CA 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 6E 00 E1 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 13 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 4F 10 D2 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0032] 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 D1 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 14 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 14 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 81 B7 C0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 08 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0032] 00 20 00 C2 06 01 08 00 00 20 00 C3 06 46 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 15 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 15 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 01 08 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 00 20 00 C4 07 00 20 20 20 03 00 03 C5 3C 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 73 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 16 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 16 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 17 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 17 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 BA 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 18 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 18 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 19 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 31 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 19 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 1B 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 90 00 0A 2017-03-17 20:22:55 scdaemon[16299] DBG: response: sw=9000 datalen=217 2017-03-17 20:22:55 scdaemon[16299] DBG: dump: 4F 10 D2 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 81 B7 C0 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 08 00 00 20 00 C2 06 01 08 00 00 20 00 C3 06 01 08 00 00 20 00 C4 07 00 20 20 20 03 00 03 C5 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=7F p2=74 lc=-1 le=256 em=0 2017-03-17 20:22:55 scdaemon[16299] DBG: raw apdu: 00 CA 7F 74 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 20 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 05 00 CA 7F 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 74 00 C4 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 6 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 20 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 02 6A 88 E0 2017-03-17 20:22:55 scdaemon[16299] DBG: response: sw=6A88 datalen=0 2017-03-17 20:22:55 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=00 p2=5E lc=-1 le=256 em=0 2017-03-17 20:22:55 scdaemon[16299] DBG: raw apdu: 00 CA 00 5E 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 21 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 05 00 CA 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 5E 00 D1 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 6 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 21 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 02 90 00 D2 2017-03-17 20:22:55 scdaemon[16299] DBG: response: sw=9000 datalen=0 2017-03-17 20:22:55 scdaemon[16299] DBG: dump: 2017-03-17 20:22:55 scdaemon[16299] Version-2 ......: yes 2017-03-17 20:22:55 scdaemon[16299] Get-Challenge ..: yes (2048 bytes max) 2017-03-17 20:22:55 scdaemon[16299] Key-Import .....: yes 2017-03-17 20:22:55 scdaemon[16299] Change-Force-PW1: yes 2017-03-17 20:22:55 scdaemon[16299] Private-DOs ....: yes 2017-03-17 20:22:55 scdaemon[16299] Algo-Attr-Change: yes 2017-03-17 20:22:55 scdaemon[16299] SM-Support .....: no 2017-03-17 20:22:55 scdaemon[16299] Max-Cert3-Len ..: 2048 2017-03-17 20:22:55 scdaemon[16299] Max-Cmd-Data ...: 2048 2017-03-17 20:22:55 scdaemon[16299] Max-Rsp-Data ...: 2048 2017-03-17 20:22:55 scdaemon[16299] Cmd-Chaining ...: no 2017-03-17 20:22:55 scdaemon[16299] Ext-Lc-Le ......: yes 2017-03-17 20:22:55 scdaemon[16299] Status Indicator: 05 2017-03-17 20:22:55 scdaemon[16299] Symmetric crypto: no 2017-03-17 20:22:55 scdaemon[16299] Button..........: no 2017-03-17 20:22:55 scdaemon[16299] GnuPG-No-Sync ..: no 2017-03-17 20:22:55 scdaemon[16299] GnuPG-Def-PW2 ..: no 2017-03-17 20:22:55 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=00 p2=6E lc=-1 le=256 em=0 2017-03-17 20:22:55 scdaemon[16299] DBG: raw apdu: 00 CA 00 6E 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 22 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 05 00 CA 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 6E 00 A1 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 22 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 4F 10 D2 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0032] 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 91 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 23 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 23 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 81 B7 C0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 08 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0032] 00 20 00 C2 06 01 08 00 00 20 00 C3 06 06 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 24 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 24 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 01 08 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 00 20 00 C4 07 00 20 20 20 03 00 03 C5 3C 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 33 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 25 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 25 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 40 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 26 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 26 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 FA 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 27 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 27 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 40 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 28 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 31 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 28 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 1B 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 90 00 4A 2017-03-17 20:22:55 scdaemon[16299] DBG: response: sw=9000 datalen=217 2017-03-17 20:22:55 scdaemon[16299] DBG: dump: 4F 10 D2 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 81 B7 C0 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 08 00 00 20 00 C2 06 01 08 00 00 20 00 C3 06 01 08 00 00 20 00 C4 07 00 20 20 20 03 00 03 C5 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:22:55 scdaemon[16299] Key-Attr-sign ..: RSA, n=2048, e=32, fmt=std 2017-03-17 20:22:55 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=00 p2=6E lc=-1 le=256 em=0 2017-03-17 20:22:55 scdaemon[16299] DBG: raw apdu: 00 CA 00 6E 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 29 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 05 00 CA 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 6E 00 E1 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 29 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 4F 10 D2 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0032] 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 D1 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 30 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 30 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 81 B7 C0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 08 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0032] 00 20 00 C2 06 01 08 00 00 20 00 C3 06 46 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 31 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 31 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 01 08 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 00 20 00 C4 07 00 20 20 20 03 00 03 C5 3C 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 73 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 32 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 32 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 33 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 33 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 BA 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 34 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:55 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 34 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 35 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 31 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 35 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 1B 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 90 00 0A 2017-03-17 20:22:56 scdaemon[16299] DBG: response: sw=9000 datalen=217 2017-03-17 20:22:56 scdaemon[16299] DBG: dump: 4F 10 D2 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 81 B7 C0 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 08 00 00 20 00 C2 06 01 08 00 00 20 00 C3 06 01 08 00 00 20 00 C4 07 00 20 20 20 03 00 03 C5 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:22:56 scdaemon[16299] Key-Attr-encr ..: RSA, n=2048, e=32, fmt=std 2017-03-17 20:22:56 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=00 p2=6E lc=-1 le=256 em=0 2017-03-17 20:22:56 scdaemon[16299] DBG: raw apdu: 00 CA 00 6E 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 36 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 05 00 CA 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 6E 00 A1 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 36 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 4F 10 D2 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0032] 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 91 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 37 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 37 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 81 B7 C0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 08 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0032] 00 20 00 C2 06 01 08 00 00 20 00 C3 06 06 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 38 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 38 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 01 08 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 00 20 00 C4 07 00 20 20 20 03 00 03 C5 3C 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 33 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 39 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 39 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 40 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 40 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 40 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 FA 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 41 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 41 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 40 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 42 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 31 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 42 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 1B 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 90 00 4A 2017-03-17 20:22:56 scdaemon[16299] DBG: response: sw=9000 datalen=217 2017-03-17 20:22:56 scdaemon[16299] DBG: dump: 4F 10 D2 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 81 B7 C0 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 08 00 00 20 00 C2 06 01 08 00 00 20 00 C3 06 01 08 00 00 20 00 C4 07 00 20 20 20 03 00 03 C5 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:22:56 scdaemon[16299] Key-Attr-auth ..: RSA, n=2048, e=32, fmt=std 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 -> S SERIALNO D27600012401020100050000319E0000 0 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 -> OK 2017-03-17 20:22:56 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:22:56 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 <- SERIALNO openpgp 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 -> S SERIALNO D27600012401020100050000319E0000 0 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 -> OK 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 <- SERIALNO 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 -> S SERIALNO D27600012401020100050000319E0000 0 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 -> OK 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 <- LEARN --force 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 -> S READER 20A0:4108:0000319E0000000000000000:0 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 -> S SERIALNO D27600012401020100050000319E0000 0 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 -> S APPTYPE OPENPGP 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 -> S EXTCAP gc=1+ki=1+fc=1+pd=1+mcl3=2048+aac=1+sm=0+si=5+dec=0+bt=0 2017-03-17 20:22:56 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=00 p2=65 lc=-1 le=256 em=0 2017-03-17 20:22:56 scdaemon[16299] DBG: raw apdu: 00 CA 00 65 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 44 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 05 00 CA 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 65 00 EA 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 17 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 44 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 0D 5B 00 5F 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 2D 02 64 65 5F 35 01 39 90 00 A5 2017-03-17 20:22:56 scdaemon[16299] DBG: response: sw=9000 datalen=11 2017-03-17 20:22:56 scdaemon[16299] DBG: dump: 5B 00 5F 2D 02 64 65 5F 35 01 39 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 -> S DISP-NAME 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 -> S DISP-LANG de 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 -> S DISP-SEX 9 2017-03-17 20:22:56 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=5F p2=50 lc=-1 le=256 em=0 2017-03-17 20:22:56 scdaemon[16299] DBG: raw apdu: 00 CA 5F 50 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 45 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 05 00 CA 5F 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 50 00 C0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 6 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 45 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 02 90 00 92 2017-03-17 20:22:56 scdaemon[16299] DBG: response: sw=9000 datalen=0 2017-03-17 20:22:56 scdaemon[16299] DBG: dump: 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 -> S PUBKEY-URL 2017-03-17 20:22:56 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=00 p2=6E lc=-1 le=256 em=0 2017-03-17 20:22:56 scdaemon[16299] DBG: raw apdu: 00 CA 00 6E 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 46 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 05 00 CA 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 6E 00 E1 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 46 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 4F 10 D2 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0032] 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 D1 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 47 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 47 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 81 B7 C0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 08 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0032] 00 20 00 C2 06 01 08 00 00 20 00 C3 06 46 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 48 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 48 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 01 08 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 00 20 00 C4 07 00 20 20 20 03 00 03 C5 3C 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 73 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 49 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 49 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 50 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 50 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 BA 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 51 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 51 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 52 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 31 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 52 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 1B 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 90 00 0A 2017-03-17 20:22:56 scdaemon[16299] DBG: response: sw=9000 datalen=217 2017-03-17 20:22:56 scdaemon[16299] DBG: dump: 4F 10 D2 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 81 B7 C0 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 08 00 00 20 00 C2 06 01 08 00 00 20 00 C3 06 01 08 00 00 20 00 C4 07 00 20 20 20 03 00 03 C5 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=00 p2=C4 lc=-1 le=256 em=0 2017-03-17 20:22:56 scdaemon[16299] DBG: raw apdu: 00 CA 00 C4 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 53 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 05 00 CA 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] C4 00 0B 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 13 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 53 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 09 00 20 20 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 20 03 00 03 90 00 B9 2017-03-17 20:22:56 scdaemon[16299] DBG: response: sw=9000 datalen=7 2017-03-17 20:22:56 scdaemon[16299] DBG: dump: 00 20 20 20 03 00 03 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 -> S CHV-STATUS +0+32+32+32+3+0+3 2017-03-17 20:22:56 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=00 p2=7A lc=-1 le=256 em=0 2017-03-17 20:22:56 scdaemon[16299] DBG: raw apdu: 00 CA 00 7A 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 54 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 05 00 CA 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 7A 00 F5 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 11 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 54 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 07 93 03 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 90 00 47 2017-03-17 20:22:56 scdaemon[16299] DBG: response: sw=9000 datalen=5 2017-03-17 20:22:56 scdaemon[16299] DBG: dump: 93 03 00 00 00 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 -> S SIG-COUNTER 0 2017-03-17 20:22:56 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=01 p2=01 lc=-1 le=256 em=0 2017-03-17 20:22:56 scdaemon[16299] DBG: raw apdu: 00 CA 01 01 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 55 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 05 00 CA 01 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 01 00 CF 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 6 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 55 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 02 90 00 92 2017-03-17 20:22:56 scdaemon[16299] DBG: response: sw=9000 datalen=0 2017-03-17 20:22:56 scdaemon[16299] DBG: dump: 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 -> S PRIVATE-DO-1 2017-03-17 20:22:56 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=01 p2=02 lc=-1 le=256 em=0 2017-03-17 20:22:56 scdaemon[16299] DBG: raw apdu: 00 CA 01 02 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 56 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 05 00 CA 01 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 02 00 8C 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 6 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 56 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 02 90 00 D2 2017-03-17 20:22:56 scdaemon[16299] DBG: response: sw=9000 datalen=0 2017-03-17 20:22:56 scdaemon[16299] DBG: dump: 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 -> S PRIVATE-DO-2 2017-03-17 20:22:56 scdaemon[16299] DBG: send apdu: c=00 i=47 p1=81 p2=00 lc=2 le=2048 em=1 2017-03-17 20:22:56 scdaemon[16299] DBG: raw apdu: 00 47 81 00 00 00 02 B6 00 08 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 15 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 57 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 0B 00 47 81 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 02 B6 00 08 00 71 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 6 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 57 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 02 6A 88 E0 2017-03-17 20:22:56 scdaemon[16299] DBG: response: sw=6A88 datalen=0 2017-03-17 20:22:56 scdaemon[16299] reading public key failed: Missing item in object 2017-03-17 20:22:56 scdaemon[16299] DBG: send apdu: c=00 i=47 p1=81 p2=00 lc=2 le=2048 em=1 2017-03-17 20:22:56 scdaemon[16299] DBG: raw apdu: 00 47 81 00 00 00 02 B8 00 08 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 15 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 58 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 0B 00 47 81 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 02 B8 00 08 00 3F 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 6 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 58 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 02 6A 88 A0 2017-03-17 20:22:56 scdaemon[16299] DBG: response: sw=6A88 datalen=0 2017-03-17 20:22:56 scdaemon[16299] reading public key failed: Missing item in object 2017-03-17 20:22:56 scdaemon[16299] DBG: send apdu: c=00 i=47 p1=81 p2=00 lc=2 le=2048 em=1 2017-03-17 20:22:56 scdaemon[16299] DBG: raw apdu: 00 47 81 00 00 00 02 A4 00 08 00 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 15 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 59 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 0B 00 47 81 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 02 A4 00 08 00 63 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 6 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 59 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:22:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 02 6A 88 E0 2017-03-17 20:22:56 scdaemon[16299] DBG: response: sw=6A88 datalen=0 2017-03-17 20:22:56 scdaemon[16299] reading public key failed: Missing item in object 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 -> OK 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 <- GETATTR KEY-ATTR 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 -> S KEY-ATTR 1 1 rsa2048 32 1 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 -> S KEY-ATTR 2 1 rsa2048 32 1 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 -> S KEY-ATTR 3 1 rsa2048 32 1 2017-03-17 20:22:56 scdaemon[16299] DBG: chan_5 -> OK 2017-03-17 20:22:56 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:22:56 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:22:57 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:22:57 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:22:57 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:22:57 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:22:58 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:22:58 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:22:58 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:22:58 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:22:59 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:22:59 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:22:59 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:22:59 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:00 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:00 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:00 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:00 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:01 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:01 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:01 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:01 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:02 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:02 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:02 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:02 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:03 scdaemon[16299] DBG: chan_5 <- GETATTR SERIALNO 2017-03-17 20:23:03 scdaemon[16299] DBG: chan_5 -> S SERIALNO D27600012401020100050000319E0000 2017-03-17 20:23:03 scdaemon[16299] DBG: chan_5 -> OK 2017-03-17 20:23:03 scdaemon[16299] DBG: chan_5 <- GETATTR KEY-FPR 2017-03-17 20:23:03 scdaemon[16299] DBG: chan_5 -> OK 2017-03-17 20:23:03 scdaemon[16299] DBG: chan_5 <- GETATTR CHV-STATUS 2017-03-17 20:23:03 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=00 p2=C4 lc=-1 le=256 em=0 2017-03-17 20:23:03 scdaemon[16299] DBG: raw apdu: 00 CA 00 C4 00 2017-03-17 20:23:03 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:23:03 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:23:03 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:23:03 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 73 2017-03-17 20:23:03 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:23:03 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:23:03 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 05 00 CA 00 2017-03-17 20:23:03 scdaemon[16299] DBG: ccid-driver: [0016] C4 00 4B 2017-03-17 20:23:03 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:23:03 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 13 2017-03-17 20:23:03 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:23:03 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 73 2017-03-17 20:23:03 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:23:03 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 09 00 20 20 2017-03-17 20:23:03 scdaemon[16299] DBG: ccid-driver: [0016] 20 03 00 03 90 00 F9 2017-03-17 20:23:03 scdaemon[16299] DBG: response: sw=9000 datalen=7 2017-03-17 20:23:03 scdaemon[16299] DBG: dump: 00 20 20 20 03 00 03 2017-03-17 20:23:03 scdaemon[16299] DBG: chan_5 -> S CHV-STATUS +0+32+32+32+3+0+3 2017-03-17 20:23:03 scdaemon[16299] DBG: chan_5 -> OK 2017-03-17 20:23:03 scdaemon[16299] DBG: chan_5 <- GETATTR DISP-NAME 2017-03-17 20:23:03 scdaemon[16299] DBG: chan_5 -> S DISP-NAME 2017-03-17 20:23:03 scdaemon[16299] DBG: chan_5 -> OK 2017-03-17 20:23:03 scdaemon[16299] DBG: chan_5 <- GETATTR EXTCAP 2017-03-17 20:23:03 scdaemon[16299] DBG: chan_5 -> S EXTCAP gc=1+ki=1+fc=1+pd=1+mcl3=2048+aac=1+sm=0+si=5+dec=0+bt=0 2017-03-17 20:23:03 scdaemon[16299] DBG: chan_5 -> OK 2017-03-17 20:23:03 scdaemon[16299] DBG: chan_5 <- GETATTR KEY-ATTR 2017-03-17 20:23:03 scdaemon[16299] DBG: chan_5 -> S KEY-ATTR 1 1 rsa2048 32 1 2017-03-17 20:23:03 scdaemon[16299] DBG: chan_5 -> S KEY-ATTR 2 1 rsa2048 32 1 2017-03-17 20:23:03 scdaemon[16299] DBG: chan_5 -> S KEY-ATTR 3 1 rsa2048 32 1 2017-03-17 20:23:03 scdaemon[16299] DBG: chan_5 -> OK 2017-03-17 20:23:03 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:03 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:03 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:03 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:04 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:04 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:04 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:04 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:05 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:05 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:05 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:05 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:06 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:06 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:06 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:06 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:07 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:07 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:07 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:07 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:08 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:08 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:08 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:08 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:09 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:09 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:09 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:09 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:10 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:10 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:10 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:10 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:11 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:11 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:11 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:11 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:12 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:12 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:12 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:12 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:13 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:13 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:13 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:13 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:14 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:14 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:14 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:14 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:15 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:15 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:15 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:15 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:16 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:16 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:16 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:16 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:17 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:17 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:17 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:17 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:18 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:18 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:18 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:18 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:19 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:19 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:19 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:19 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:20 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:20 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:20 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:20 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:21 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:21 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:21 scdaemon[16299] DBG: chan_5 <- SETATTR CHV-STATUS-1 %01 2017-03-17 20:23:21 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=00 p2=C4 lc=-1 le=256 em=0 2017-03-17 20:23:21 scdaemon[16299] DBG: raw apdu: 00 CA 00 C4 00 2017-03-17 20:23:21 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:23:21 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:23:21 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:23:21 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 111 2017-03-17 20:23:21 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:23:21 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:23:21 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 05 00 CA 00 2017-03-17 20:23:21 scdaemon[16299] DBG: ccid-driver: [0016] C4 00 0B 2017-03-17 20:23:21 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:23:21 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 13 2017-03-17 20:23:21 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:23:21 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 111 2017-03-17 20:23:21 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:23:21 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 09 00 20 20 2017-03-17 20:23:21 scdaemon[16299] DBG: ccid-driver: [0016] 20 03 00 03 90 00 B9 2017-03-17 20:23:21 scdaemon[16299] DBG: response: sw=9000 datalen=7 2017-03-17 20:23:21 scdaemon[16299] DBG: dump: 00 20 20 20 03 00 03 2017-03-17 20:23:21 scdaemon[16299] 3 Admin PIN attempts remaining before card is permanently locked 2017-03-17 20:23:21 scdaemon[16299] DBG: asking for PIN '|A|Please enter the Admin PIN' 2017-03-17 20:23:21 scdaemon[16299] DBG: chan_5 -> INQUIRE NEEDPIN |A|Please enter the Admin PIN 2017-03-17 20:23:21 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:21 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:22 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:22 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:22 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:22 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:23 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:23 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:23 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:23 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:24 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:24 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:24 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:24 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:25 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:25 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:25 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:25 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:26 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:26 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:26 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:26 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:27 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:27 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:27 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:27 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:28 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:28 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:28 scdaemon[16299] DBG: chan_5 <- [ 44 20 31 32 33 34 35 36 37 38 00 00 00 00 00 00 ...(76 byte(s) skipped) ] 2017-03-17 20:23:28 scdaemon[16299] DBG: chan_5 <- END 2017-03-17 20:23:28 scdaemon[16299] DBG: send apdu: c=00 i=20 p1=00 p2=83 lc=8 le=-1 em=0 2017-03-17 20:23:28 scdaemon[16299] DBG: raw apdu: 00 20 00 83 08 31 32 33 34 35 36 37 38 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 17 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 126 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 0D 00 20 00 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: [0016] 83 08 31 32 33 34 35 36 37 38 EE 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 6 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 126 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 02 90 00 D2 2017-03-17 20:23:28 scdaemon[16299] DBG: response: sw=9000 datalen=0 2017-03-17 20:23:28 scdaemon[16299] DBG: dump: 2017-03-17 20:23:28 scdaemon[16299] DBG: send apdu: c=00 i=DA p1=00 p2=C4 lc=1 le=-1 em=0 2017-03-17 20:23:28 scdaemon[16299] DBG: raw apdu: 00 DA 00 C4 01 01 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 10 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 127 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 06 00 DA 00 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: [0016] C4 01 01 18 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 6 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 127 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:23:28 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 02 90 00 92 2017-03-17 20:23:28 scdaemon[16299] DBG: response: sw=9000 datalen=0 2017-03-17 20:23:28 scdaemon[16299] DBG: dump: 2017-03-17 20:23:28 scdaemon[16299] DBG: chan_5 -> OK 2017-03-17 20:23:28 scdaemon[16299] DBG: chan_5 <- CHECKPIN D27600012401020100050000319E0000 2017-03-17 20:23:28 scdaemon[16299] DBG: asking for PIN '||Please enter the PIN' 2017-03-17 20:23:28 scdaemon[16299] DBG: chan_5 -> INQUIRE NEEDPIN ||Please enter the PIN 2017-03-17 20:23:28 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:28 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:29 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:29 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:29 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:29 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:30 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:30 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:30 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:30 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:31 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:31 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:31 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:31 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:32 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:32 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:32 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:32 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:32 scdaemon[16299] DBG: chan_5 <- [ 44 20 31 32 33 34 35 36 00 00 00 00 00 00 00 00 ...(76 byte(s) skipped) ] 2017-03-17 20:23:32 scdaemon[16299] DBG: chan_5 <- END 2017-03-17 20:23:32 scdaemon[16299] DBG: send apdu: c=00 i=20 p1=00 p2=82 lc=6 le=-1 em=0 2017-03-17 20:23:32 scdaemon[16299] DBG: raw apdu: 00 20 00 82 06 31 32 33 34 35 36 2017-03-17 20:23:32 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:23:32 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 15 2017-03-17 20:23:32 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:23:32 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 137 2017-03-17 20:23:32 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:23:32 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:23:32 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 0B 00 20 00 2017-03-17 20:23:32 scdaemon[16299] DBG: ccid-driver: [0016] 82 06 31 32 33 34 35 36 E8 2017-03-17 20:23:33 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:23:33 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 6 2017-03-17 20:23:33 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:23:33 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 137 2017-03-17 20:23:33 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:23:33 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 02 90 00 D2 2017-03-17 20:23:33 scdaemon[16299] DBG: response: sw=9000 datalen=0 2017-03-17 20:23:33 scdaemon[16299] DBG: dump: 2017-03-17 20:23:33 scdaemon[16299] DBG: send apdu: c=00 i=20 p1=00 p2=81 lc=6 le=-1 em=0 2017-03-17 20:23:33 scdaemon[16299] DBG: raw apdu: 00 20 00 81 06 31 32 33 34 35 36 2017-03-17 20:23:33 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:23:33 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 15 2017-03-17 20:23:33 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:23:33 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 138 2017-03-17 20:23:33 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:23:33 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:23:33 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 0B 00 20 00 2017-03-17 20:23:33 scdaemon[16299] DBG: ccid-driver: [0016] 81 06 31 32 33 34 35 36 AB 2017-03-17 20:23:33 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:23:33 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 6 2017-03-17 20:23:33 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:23:33 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 138 2017-03-17 20:23:33 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:23:33 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 02 90 00 92 2017-03-17 20:23:33 scdaemon[16299] DBG: response: sw=9000 datalen=0 2017-03-17 20:23:33 scdaemon[16299] DBG: dump: 2017-03-17 20:23:33 scdaemon[16299] operation check_pin result: Success 2017-03-17 20:23:33 scdaemon[16299] DBG: chan_5 -> OK 2017-03-17 20:23:33 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:33 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:33 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:33 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:34 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:34 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:34 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:34 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:35 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:35 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:35 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:35 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:36 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:36 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:36 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:36 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:37 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:37 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:37 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:37 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:38 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:38 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:38 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:38 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:39 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:39 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:39 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:39 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:40 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:40 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:40 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:40 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:41 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:41 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:41 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:41 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:42 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:42 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:42 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:42 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:43 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:43 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:43 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:43 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:44 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:44 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:44 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:44 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:45 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:45 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:45 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:45 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:46 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:46 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:46 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:46 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:47 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:47 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:47 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:47 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:48 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:48 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:48 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:48 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:49 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:49 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:49 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:49 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:50 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:50 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:50 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:50 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:51 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:51 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:51 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:51 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:52 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:52 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:52 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:52 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:53 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:53 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:53 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:53 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:54 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:54 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:54 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:54 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:55 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:55 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:55 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:55 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:56 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:56 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:56 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:56 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:57 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:57 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:57 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:57 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:58 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:58 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:58 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:58 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:59 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:59 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:23:59 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:23:59 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:00 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:00 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:00 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:00 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:01 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:01 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:01 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:01 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:02 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:02 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:02 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:02 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:03 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:03 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:03 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:03 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:04 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:04 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:04 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:04 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:05 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:05 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:05 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:05 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:06 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:06 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:06 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:06 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:07 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:07 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:07 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:07 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:08 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:08 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:08 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:08 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:09 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:09 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:09 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:09 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:10 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:10 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:10 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:10 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:11 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:11 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:11 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:11 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:12 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:12 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:12 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:12 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:13 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:13 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:13 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:13 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:14 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:14 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:14 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:14 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:15 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:15 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:15 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:15 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:16 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:16 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:16 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:16 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:17 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:17 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:17 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:17 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:18 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:18 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:18 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:18 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:19 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:19 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:19 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:19 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:20 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:20 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:20 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:20 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:21 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:21 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:21 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:21 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:22 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:22 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:22 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:22 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:23 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:23 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:23 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:23 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:24 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:24 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:24 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:24 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:25 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:25 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:25 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:25 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:26 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:26 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:26 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:26 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:27 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:27 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:27 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:27 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:28 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:28 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:28 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:28 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:29 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:29 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:29 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:29 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:30 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:30 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:30 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:30 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:31 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:31 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:31 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:31 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:32 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:32 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:32 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:32 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:33 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:33 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:33 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:33 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:34 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:34 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:34 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:34 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:35 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:35 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:35 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:35 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:36 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:36 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:36 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:36 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:37 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:37 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:37 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:37 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:38 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:38 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:38 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:38 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:39 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:39 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:39 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:39 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:40 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:40 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:40 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:40 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:41 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:41 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:41 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:41 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:42 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:42 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:42 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:42 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:43 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:43 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:43 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:43 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:44 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:44 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:44 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:44 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:45 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:45 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:45 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:45 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:46 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:46 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:46 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:46 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:47 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:47 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:47 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:47 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:48 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:48 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:48 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:48 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:49 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:49 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:49 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:49 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:50 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:50 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:50 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:50 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:51 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:51 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:51 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:51 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:52 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:52 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:52 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:52 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:53 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:53 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:53 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:53 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:54 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:54 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:54 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:54 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:55 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:55 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:55 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:55 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:56 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:56 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:56 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:56 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:57 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:57 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:57 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:57 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:58 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:58 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:58 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:58 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:59 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:59 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:24:59 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:24:59 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:00 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:00 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:00 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:00 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:01 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:01 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:01 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:01 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:02 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:02 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:02 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:02 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:03 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:03 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:03 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:03 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:04 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:04 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:04 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:04 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:05 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:05 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:05 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:05 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:06 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:06 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:06 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:06 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:07 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:07 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:07 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:07 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:08 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:08 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:08 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:08 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:09 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:09 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:09 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:09 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:10 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:10 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:10 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:10 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:11 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:11 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:11 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:11 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:12 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:12 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:12 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:12 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:13 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:13 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:13 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:13 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:14 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:14 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:14 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:14 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:15 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:15 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:15 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:15 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:16 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:16 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:16 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:16 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:17 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:17 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:17 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:17 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:18 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:18 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:18 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:18 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:19 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:19 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:19 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:19 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:20 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:20 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:20 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:20 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:21 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:21 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:21 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:21 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:22 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:22 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:22 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:22 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:23 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:23 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:23 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:23 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:24 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:24 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:24 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:24 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:25 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:25 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:25 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:25 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:26 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:26 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:26 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:26 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:27 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:27 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:27 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:27 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:28 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:28 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:28 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:28 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:29 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:29 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:29 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:29 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:30 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:30 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:30 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:30 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:31 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:31 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:31 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:31 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:32 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:32 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:32 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:32 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:33 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:33 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:33 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:33 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:34 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:34 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:34 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:34 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:35 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:35 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:35 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:35 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:36 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:36 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:36 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:36 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:37 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:37 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:37 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:37 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:38 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:38 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:38 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:38 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:39 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:39 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:39 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:39 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:40 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:40 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:40 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:40 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:41 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:41 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:41 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:41 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:42 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:42 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:42 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:42 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:43 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:43 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:43 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:43 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:44 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:44 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:45 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:45 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:45 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:45 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:46 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:46 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:46 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:46 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:47 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:47 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:47 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:47 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:48 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:48 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:48 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:48 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:49 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:49 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:49 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:49 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:50 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:50 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:50 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:50 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:51 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:51 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:51 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:51 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:52 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:52 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:52 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:52 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:53 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:53 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:53 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:53 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:54 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:54 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:54 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:54 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:55 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:55 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:55 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:55 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:56 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:56 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:56 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:56 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:57 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:57 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:57 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:57 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:58 scdaemon[16299] DBG: chan_5 <- SETATTR KEY-ATTR --force+1+1+rsa4096 2017-03-17 20:25:58 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=00 p2=6E lc=-1 le=256 em=0 2017-03-17 20:25:58 scdaemon[16299] DBG: raw apdu: 00 CA 00 6E 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 172 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 05 00 CA 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0016] 6E 00 E1 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 172 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 4F 10 D2 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0016] 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0032] 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 D1 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 173 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 173 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 81 B7 C0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0016] 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 08 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0032] 00 20 00 C2 06 01 08 00 00 20 00 C3 06 46 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 174 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 174 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 01 08 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0016] 00 20 00 C4 07 01 20 20 20 03 00 03 C5 3C 00 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 72 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 175 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 175 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 00 00 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 176 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 176 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 00 00 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 BA 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 177 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 177 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 00 00 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 178 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 31 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 178 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 1B 00 00 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 90 00 0A 2017-03-17 20:25:58 scdaemon[16299] DBG: response: sw=9000 datalen=217 2017-03-17 20:25:58 scdaemon[16299] DBG: dump: 4F 10 D2 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 81 B7 C0 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 08 00 00 20 00 C2 06 01 08 00 00 20 00 C3 06 01 08 00 00 20 00 C4 07 01 20 20 20 03 00 03 C5 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:25:58 scdaemon[16299] DBG: send apdu: c=00 i=DA p1=00 p2=C1 lc=6 le=-1 em=0 2017-03-17 20:25:58 scdaemon[16299] DBG: raw apdu: 00 DA 00 C1 06 01 10 00 00 20 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 15 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 179 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 0B 00 DA 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0016] C1 06 01 10 00 00 20 00 27 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 6 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 179 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 02 90 00 92 2017-03-17 20:25:58 scdaemon[16299] DBG: response: sw=9000 datalen=0 2017-03-17 20:25:58 scdaemon[16299] DBG: dump: 2017-03-17 20:25:58 scdaemon[16299] key attribute changed (key=1) 2017-03-17 20:25:58 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=00 p2=6E lc=-1 le=256 em=0 2017-03-17 20:25:58 scdaemon[16299] DBG: raw apdu: 00 CA 00 6E 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 180 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 05 00 CA 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0016] 6E 00 E1 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 180 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 4F 10 D2 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0016] 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0032] 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 D1 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 181 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 181 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 81 B7 C0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0016] 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 10 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0032] 00 20 00 C2 06 01 08 00 00 20 00 C3 06 5E 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 182 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 182 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 01 08 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0016] 00 20 00 C4 07 01 20 20 20 03 00 03 C5 3C 00 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 72 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 183 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 183 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 00 00 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 184 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 184 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 00 00 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 BA 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 185 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 185 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 00 00 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 186 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 31 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 186 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 1B 00 00 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 2017-03-17 20:25:58 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 90 00 0A 2017-03-17 20:25:58 scdaemon[16299] DBG: response: sw=9000 datalen=217 2017-03-17 20:25:58 scdaemon[16299] DBG: dump: 4F 10 D2 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 81 B7 C0 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 10 00 00 20 00 C2 06 01 08 00 00 20 00 C3 06 01 08 00 00 20 00 C4 07 01 20 20 20 03 00 03 C5 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:25:58 scdaemon[16299] Key-Attr-sign ..: RSA, n=4096, e=32, fmt=std 2017-03-17 20:25:58 scdaemon[16299] DBG: chan_5 -> OK 2017-03-17 20:25:58 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:58 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:59 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:59 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:25:59 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:25:59 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:00 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:00 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:00 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:00 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:01 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:01 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:01 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:01 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:01 scdaemon[16299] DBG: chan_5 <- SETATTR KEY-ATTR --force+2+1+rsa4096 2017-03-17 20:26:01 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=00 p2=6E lc=-1 le=256 em=0 2017-03-17 20:26:01 scdaemon[16299] DBG: raw apdu: 00 CA 00 6E 00 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 194 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 05 00 CA 00 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0016] 6E 00 A1 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 194 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 4F 10 D2 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0016] 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0032] 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 91 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 195 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 195 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 81 B7 C0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0016] 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 10 00 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0032] 00 20 00 C2 06 01 08 00 00 20 00 C3 06 1E 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 196 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 196 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 01 08 00 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0016] 00 20 00 C4 07 01 20 20 20 03 00 03 C5 3C 00 00 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 32 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 197 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 197 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 00 00 00 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 40 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 198 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 198 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 00 00 00 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 FA 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 199 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 199 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 00 00 00 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 40 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 200 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 31 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 200 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 1B 00 00 00 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 90 00 4A 2017-03-17 20:26:01 scdaemon[16299] DBG: response: sw=9000 datalen=217 2017-03-17 20:26:01 scdaemon[16299] DBG: dump: 4F 10 D2 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 81 B7 C0 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 10 00 00 20 00 C2 06 01 08 00 00 20 00 C3 06 01 08 00 00 20 00 C4 07 01 20 20 20 03 00 03 C5 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:26:01 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=00 p2=C4 lc=-1 le=256 em=0 2017-03-17 20:26:01 scdaemon[16299] DBG: raw apdu: 00 CA 00 C4 00 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 201 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 05 00 CA 00 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0016] C4 00 4B 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 13 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 201 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 09 01 20 20 2017-03-17 20:26:01 scdaemon[16299] DBG: ccid-driver: [0016] 20 03 00 03 90 00 F8 2017-03-17 20:26:01 scdaemon[16299] DBG: response: sw=9000 datalen=7 2017-03-17 20:26:01 scdaemon[16299] DBG: dump: 01 20 20 20 03 00 03 2017-03-17 20:26:01 scdaemon[16299] 3 Admin PIN attempts remaining before card is permanently locked 2017-03-17 20:26:01 scdaemon[16299] DBG: asking for PIN '|A|Please enter the Admin PIN' 2017-03-17 20:26:01 scdaemon[16299] DBG: chan_5 -> INQUIRE NEEDPIN |A|Please enter the Admin PIN 2017-03-17 20:26:02 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:02 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:02 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:02 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:03 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:03 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:03 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:03 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:04 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:04 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:04 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:04 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:04 scdaemon[16299] DBG: chan_5 <- [ 44 20 31 32 33 34 35 36 37 38 00 00 00 00 00 00 ...(76 byte(s) skipped) ] 2017-03-17 20:26:04 scdaemon[16299] DBG: chan_5 <- END 2017-03-17 20:26:04 scdaemon[16299] DBG: send apdu: c=00 i=20 p1=00 p2=83 lc=8 le=-1 em=0 2017-03-17 20:26:04 scdaemon[16299] DBG: raw apdu: 00 20 00 83 08 31 32 33 34 35 36 37 38 2017-03-17 20:26:04 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:04 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 17 2017-03-17 20:26:04 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:04 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 208 2017-03-17 20:26:04 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:04 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:04 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 0D 00 20 00 2017-03-17 20:26:04 scdaemon[16299] DBG: ccid-driver: [0016] 83 08 31 32 33 34 35 36 37 38 AE 2017-03-17 20:26:04 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:04 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 6 2017-03-17 20:26:04 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:04 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 208 2017-03-17 20:26:04 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:04 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 02 90 00 92 2017-03-17 20:26:04 scdaemon[16299] DBG: response: sw=9000 datalen=0 2017-03-17 20:26:04 scdaemon[16299] DBG: dump: 2017-03-17 20:26:04 scdaemon[16299] DBG: send apdu: c=00 i=DA p1=00 p2=C2 lc=6 le=-1 em=0 2017-03-17 20:26:04 scdaemon[16299] DBG: raw apdu: 00 DA 00 C2 06 01 10 00 00 20 00 2017-03-17 20:26:04 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:04 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 15 2017-03-17 20:26:04 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:04 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 209 2017-03-17 20:26:04 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:04 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:04 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 0B 00 DA 00 2017-03-17 20:26:04 scdaemon[16299] DBG: ccid-driver: [0016] C2 06 01 10 00 00 20 00 64 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 6 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 209 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 02 90 00 D2 2017-03-17 20:26:05 scdaemon[16299] DBG: response: sw=9000 datalen=0 2017-03-17 20:26:05 scdaemon[16299] DBG: dump: 2017-03-17 20:26:05 scdaemon[16299] key attribute changed (key=2) 2017-03-17 20:26:05 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=00 p2=6E lc=-1 le=256 em=0 2017-03-17 20:26:05 scdaemon[16299] DBG: raw apdu: 00 CA 00 6E 00 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 210 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 05 00 CA 00 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0016] 6E 00 A1 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 210 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 4F 10 D2 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0016] 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0032] 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 91 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 211 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 211 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 81 B7 C0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0016] 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 10 00 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0032] 00 20 00 C2 06 01 10 00 00 20 00 C3 06 06 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 212 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 212 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 01 08 00 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0016] 00 20 00 C4 07 01 20 20 20 03 00 03 C5 3C 00 00 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 32 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 213 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 213 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 00 00 00 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 40 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 214 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 214 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 00 00 00 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 FA 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 215 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 215 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 00 00 00 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 40 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 216 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 31 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 216 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 1B 00 00 00 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 2017-03-17 20:26:05 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 90 00 4A 2017-03-17 20:26:05 scdaemon[16299] DBG: response: sw=9000 datalen=217 2017-03-17 20:26:05 scdaemon[16299] DBG: dump: 4F 10 D2 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 81 B7 C0 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 10 00 00 20 00 C2 06 01 10 00 00 20 00 C3 06 01 08 00 00 20 00 C4 07 01 20 20 20 03 00 03 C5 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:26:05 scdaemon[16299] Key-Attr-encr ..: RSA, n=4096, e=32, fmt=std 2017-03-17 20:26:05 scdaemon[16299] DBG: chan_5 -> OK 2017-03-17 20:26:05 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:05 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:05 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:05 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:06 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:06 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:06 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:06 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:07 scdaemon[16299] DBG: chan_5 <- SETATTR KEY-ATTR --force+3+1+rsa4096 2017-03-17 20:26:07 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=00 p2=6E lc=-1 le=256 em=0 2017-03-17 20:26:07 scdaemon[16299] DBG: raw apdu: 00 CA 00 6E 00 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 221 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 05 00 CA 00 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0016] 6E 00 E1 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 221 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 4F 10 D2 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0016] 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0032] 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 D1 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 222 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 222 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 81 B7 C0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0016] 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 10 00 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0032] 00 20 00 C2 06 01 10 00 00 20 00 C3 06 46 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 223 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 223 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 01 08 00 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0016] 00 20 00 C4 07 01 20 20 20 03 00 03 C5 3C 00 00 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 72 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 224 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 224 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 00 00 00 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 225 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 225 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 00 00 00 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 BA 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 226 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 226 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 00 00 00 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 227 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 31 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 227 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 1B 00 00 00 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 90 00 0A 2017-03-17 20:26:07 scdaemon[16299] DBG: response: sw=9000 datalen=217 2017-03-17 20:26:07 scdaemon[16299] DBG: dump: 4F 10 D2 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 81 B7 C0 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 10 00 00 20 00 C2 06 01 10 00 00 20 00 C3 06 01 08 00 00 20 00 C4 07 01 20 20 20 03 00 03 C5 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:26:07 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=00 p2=C4 lc=-1 le=256 em=0 2017-03-17 20:26:07 scdaemon[16299] DBG: raw apdu: 00 CA 00 C4 00 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 228 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 05 00 CA 00 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0016] C4 00 0B 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 13 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 228 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 09 01 20 20 2017-03-17 20:26:07 scdaemon[16299] DBG: ccid-driver: [0016] 20 03 00 03 90 00 B8 2017-03-17 20:26:07 scdaemon[16299] DBG: response: sw=9000 datalen=7 2017-03-17 20:26:07 scdaemon[16299] DBG: dump: 01 20 20 20 03 00 03 2017-03-17 20:26:07 scdaemon[16299] 3 Admin PIN attempts remaining before card is permanently locked 2017-03-17 20:26:07 scdaemon[16299] DBG: asking for PIN '|A|Please enter the Admin PIN' 2017-03-17 20:26:07 scdaemon[16299] DBG: chan_5 -> INQUIRE NEEDPIN |A|Please enter the Admin PIN 2017-03-17 20:26:07 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:07 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:07 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:07 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:08 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:08 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:08 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:08 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:09 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:09 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:09 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:09 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:10 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:10 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:10 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:10 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:11 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:11 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:11 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:11 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:12 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:12 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:12 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:12 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:13 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:13 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:13 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:13 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:14 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:14 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:14 scdaemon[16299] DBG: chan_5 <- [ 44 20 31 32 33 34 35 36 37 38 00 00 00 00 00 00 ...(76 byte(s) skipped) ] 2017-03-17 20:26:14 scdaemon[16299] DBG: chan_5 <- END 2017-03-17 20:26:14 scdaemon[16299] DBG: send apdu: c=00 i=20 p1=00 p2=83 lc=8 le=-1 em=0 2017-03-17 20:26:14 scdaemon[16299] DBG: raw apdu: 00 20 00 83 08 31 32 33 34 35 36 37 38 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 17 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 244 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 0D 00 20 00 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0016] 83 08 31 32 33 34 35 36 37 38 EE 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 6 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 244 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 02 90 00 D2 2017-03-17 20:26:14 scdaemon[16299] DBG: response: sw=9000 datalen=0 2017-03-17 20:26:14 scdaemon[16299] DBG: dump: 2017-03-17 20:26:14 scdaemon[16299] DBG: send apdu: c=00 i=DA p1=00 p2=C3 lc=6 le=-1 em=0 2017-03-17 20:26:14 scdaemon[16299] DBG: raw apdu: 00 DA 00 C3 06 01 10 00 00 20 00 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 15 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 245 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 0B 00 DA 00 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0016] C3 06 01 10 00 00 20 00 25 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 6 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 245 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 02 90 00 92 2017-03-17 20:26:14 scdaemon[16299] DBG: response: sw=9000 datalen=0 2017-03-17 20:26:14 scdaemon[16299] DBG: dump: 2017-03-17 20:26:14 scdaemon[16299] key attribute changed (key=3) 2017-03-17 20:26:14 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=00 p2=6E lc=-1 le=256 em=0 2017-03-17 20:26:14 scdaemon[16299] DBG: raw apdu: 00 CA 00 6E 00 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 246 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 05 00 CA 00 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0016] 6E 00 E1 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 246 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 4F 10 D2 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0016] 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0032] 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 D1 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 247 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 247 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 81 B7 C0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0016] 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 10 00 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0032] 00 20 00 C2 06 01 10 00 00 20 00 C3 06 46 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 248 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 248 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 01 10 00 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0016] 00 20 00 C4 07 01 20 20 20 03 00 03 C5 3C 00 00 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 6A 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 249 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 249 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 00 00 00 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 250 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 250 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 00 00 00 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 BA 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 251 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 251 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 00 00 00 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 252 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 31 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 252 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 1B 00 00 00 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 2017-03-17 20:26:14 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 90 00 0A 2017-03-17 20:26:14 scdaemon[16299] DBG: response: sw=9000 datalen=217 2017-03-17 20:26:14 scdaemon[16299] DBG: dump: 4F 10 D2 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 81 B7 C0 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 10 00 00 20 00 C2 06 01 10 00 00 20 00 C3 06 01 10 00 00 20 00 C4 07 01 20 20 20 03 00 03 C5 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:26:14 scdaemon[16299] Key-Attr-auth ..: RSA, n=4096, e=32, fmt=std 2017-03-17 20:26:14 scdaemon[16299] DBG: chan_5 -> OK 2017-03-17 20:26:14 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:14 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:15 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:15 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:15 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:15 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:16 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:16 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:16 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:16 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:17 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:17 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:17 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:17 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:18 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:18 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:18 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:18 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:19 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:19 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:19 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:19 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:20 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:20 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:20 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:20 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:21 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:21 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:21 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:21 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:22 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:22 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:22 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:22 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:23 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:23 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:23 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:23 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:24 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:24 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:24 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:24 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:25 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:25 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:25 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:25 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:26 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:26 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:26 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:26 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:27 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:27 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:27 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:27 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:28 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:28 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:28 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:28 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:29 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:29 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:29 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:29 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:30 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:30 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:30 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:30 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:31 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:31 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:31 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:31 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:32 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:32 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:33 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:33 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:33 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:33 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:34 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:34 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:34 scdaemon[16299] DBG: chan_5 <- GENKEY --timestamp=20170317T192634 --force 1 2017-03-17 20:26:34 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=00 p2=6E lc=-1 le=256 em=0 2017-03-17 20:26:34 scdaemon[16299] DBG: raw apdu: 00 CA 00 6E 00 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 36 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 05 00 CA 00 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0016] 6E 00 A1 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 36 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 4F 10 D2 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0016] 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0032] 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 91 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 37 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 37 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 81 B7 C0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0016] 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 10 00 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0032] 00 20 00 C2 06 01 10 00 00 20 00 C3 06 06 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 38 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 38 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 01 10 00 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0016] 00 20 00 C4 07 01 20 20 20 03 00 03 C5 3C 00 00 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 2A 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 39 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 39 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 00 00 00 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 40 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 40 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 40 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0010] 00 20 20 00 00 00 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 FA 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 41 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0010] 00 90 00 90 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 36 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 41 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0010] 00 60 20 00 00 00 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 00 00 00 00 00 00 00 40 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 4 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 42 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0010] 00 80 00 80 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 31 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 42 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 1B 00 00 00 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0032] 00 00 00 00 00 00 90 00 4A 2017-03-17 20:26:34 scdaemon[16299] DBG: response: sw=9000 datalen=217 2017-03-17 20:26:34 scdaemon[16299] DBG: dump: 4F 10 D2 76 00 01 24 01 02 01 00 05 00 00 31 9E 00 00 5F 52 0A 00 31 C5 73 C0 01 40 05 90 00 73 81 B7 C0 0A 7C 00 08 00 08 00 08 00 08 00 C1 06 01 10 00 00 20 00 C2 06 01 10 00 00 20 00 C3 06 01 10 00 00 20 00 C4 07 01 20 20 20 03 00 03 C5 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 C6 3C 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 CD 0C 00 00 00 00 00 00 00 00 00 00 00 00 2017-03-17 20:26:34 scdaemon[16299] generating new key 2017-03-17 20:26:34 scdaemon[16299] DBG: send apdu: c=00 i=CA p1=00 p2=C4 lc=-1 le=256 em=0 2017-03-17 20:26:34 scdaemon[16299] DBG: raw apdu: 00 CA 00 C4 00 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 9 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 43 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 05 00 CA 00 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0016] C4 00 4B 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 13 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 43 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 09 01 20 20 2017-03-17 20:26:34 scdaemon[16299] DBG: ccid-driver: [0016] 20 03 00 03 90 00 F8 2017-03-17 20:26:34 scdaemon[16299] DBG: response: sw=9000 datalen=7 2017-03-17 20:26:34 scdaemon[16299] DBG: dump: 01 20 20 20 03 00 03 2017-03-17 20:26:34 scdaemon[16299] 3 Admin PIN attempts remaining before card is permanently locked 2017-03-17 20:26:34 scdaemon[16299] DBG: asking for PIN '|A|Please enter the Admin PIN' 2017-03-17 20:26:34 scdaemon[16299] DBG: chan_5 -> INQUIRE NEEDPIN |A|Please enter the Admin PIN 2017-03-17 20:26:34 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:34 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:35 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:35 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:35 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:35 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:36 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:36 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:36 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:36 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:37 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:37 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:37 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:37 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:38 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:38 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=1 2017-03-17 20:26:38 scdaemon[16299] DBG: chan_5 <- [ 44 20 31 32 33 34 35 36 37 38 00 00 00 00 00 00 ...(76 byte(s) skipped) ] 2017-03-17 20:26:38 scdaemon[16299] DBG: chan_5 <- END 2017-03-17 20:26:38 scdaemon[16299] DBG: send apdu: c=00 i=20 p1=00 p2=83 lc=8 le=-1 em=0 2017-03-17 20:26:38 scdaemon[16299] DBG: raw apdu: 00 20 00 83 08 31 32 33 34 35 36 37 38 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 17 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 52 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 0D 00 20 00 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: [0016] 83 08 31 32 33 34 35 36 37 38 AE 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 6 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 52 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: [0010] 00 00 02 90 00 92 2017-03-17 20:26:38 scdaemon[16299] DBG: response: sw=9000 datalen=0 2017-03-17 20:26:38 scdaemon[16299] DBG: dump: 2017-03-17 20:26:38 scdaemon[16299] please wait while key is being generated ... 2017-03-17 20:26:38 scdaemon[16299] DBG: send apdu: c=00 i=47 p1=80 p2=00 lc=2 le=2048 em=1 2017-03-17 20:26:38 scdaemon[16299] DBG: raw apdu: 00 47 80 00 00 00 02 B6 00 08 00 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 15 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 53 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 0B 00 47 80 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: [0016] 00 00 00 02 B6 00 08 00 30 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: RDR_to_PC_DataBlock: 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 5 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 53 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: bStatus ...........: 0 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: [0010] 00 C3 01 64 A6 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: T=1: S-block request received cmd=3 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: T=1: waittime extension of bwi=100 2017-03-17 20:26:38 scdaemon[16299] DBG: chan_5 -> S PROGRESS card_busy w 0 0 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 5 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 54 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:38 scdaemon[16299] DBG: ccid-driver: [0010] 00 E3 01 64 86 2017-03-17 20:26:51 scdaemon[16299] DBG: ccid-driver: usb_bulk_read error: LIBUSB_ERROR_TIMEOUT 2017-03-17 20:26:51 scdaemon[16299] ccid_transceive failed: (0x1000a) 2017-03-17 20:26:51 scdaemon[16299] apdu_send_simple(0) failed: card I/O error 2017-03-17 20:26:51 scdaemon[16299] generating key failed 2017-03-17 20:26:51 scdaemon[16299] operation genkey result: Card error 2017-03-17 20:26:51 scdaemon[16299] DBG: chan_5 -> ERR 100663404 Card error 2017-03-17 20:26:51 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:26:56 scdaemon[16299] DBG: ccid-driver: usb_bulk_write error: LIBUSB_ERROR_TIMEOUT 2017-03-17 20:26:56 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x1000a status=7 changecnt=1 2017-03-17 20:26:56 scdaemon[16299] DBG: chan_5 <- SETATTR CHV-STATUS-1 %00 2017-03-17 20:26:56 scdaemon[16299] DBG: send apdu: c=00 i=DA p1=00 p2=C4 lc=1 le=-1 em=0 2017-03-17 20:26:56 scdaemon[16299] DBG: raw apdu: 00 DA 00 C4 01 00 2017-03-17 20:26:56 scdaemon[16299] DBG: ccid-driver: PC_to_RDR_XfrBlock: 2017-03-17 20:26:56 scdaemon[16299] DBG: ccid-driver: dwLength ..........: 10 2017-03-17 20:26:56 scdaemon[16299] DBG: ccid-driver: bSlot .............: 0 2017-03-17 20:26:56 scdaemon[16299] DBG: ccid-driver: bSeq ..............: 56 2017-03-17 20:26:56 scdaemon[16299] DBG: ccid-driver: bBWI ..............: 0x04 2017-03-17 20:26:56 scdaemon[16299] DBG: ccid-driver: wLevelParameter ...: 0x0000 2017-03-17 20:26:56 scdaemon[16299] DBG: ccid-driver: [0010] 00 40 06 00 DA 00 2017-03-17 20:26:56 scdaemon[16299] DBG: ccid-driver: [0016] C4 01 00 59 2017-03-17 20:27:01 scdaemon[16299] DBG: ccid-driver: usb_bulk_write error: LIBUSB_ERROR_TIMEOUT 2017-03-17 20:27:01 scdaemon[16299] ccid_transceive failed: (0x1000a) 2017-03-17 20:27:01 scdaemon[16299] apdu_send_simple(0) failed: card I/O error 2017-03-17 20:27:01 scdaemon[16299] failed to set 'CHV-STATUS-1': Input/output error 2017-03-17 20:27:01 scdaemon[16299] DBG: chan_5 -> ERR 100696113 Input/output error 2017-03-17 20:27:01 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:06 scdaemon[16299] DBG: ccid-driver: usb_bulk_write error: LIBUSB_ERROR_TIMEOUT 2017-03-17 20:27:06 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x1000a status=7 changecnt=1 2017-03-17 20:27:07 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:12 scdaemon[16299] DBG: ccid-driver: usb_bulk_write error: LIBUSB_ERROR_TIMEOUT 2017-03-17 20:27:12 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x1000a status=7 changecnt=1 2017-03-17 20:27:12 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:17 scdaemon[16299] DBG: ccid-driver: usb_bulk_write error: LIBUSB_ERROR_TIMEOUT 2017-03-17 20:27:17 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x1000a status=7 changecnt=1 2017-03-17 20:27:18 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:20 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:20 scdaemon[16299] updating reader 0 (0) status: 0x0007->0x0007 (1->2) 2017-03-17 20:27:20 scdaemon[16299] sending signal 12 to client 2454 2017-03-17 20:27:20 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:20 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:21 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:21 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:21 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:21 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:22 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:22 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:22 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:22 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:23 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:23 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:23 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:23 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:24 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:24 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:24 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:24 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:25 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:25 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:25 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:25 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:26 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:26 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:26 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:26 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:27 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:27 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:27 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:27 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:28 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:28 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:28 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:28 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:29 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:29 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:29 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:29 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:30 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:30 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:30 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:30 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:31 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:31 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:31 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:31 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:32 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:32 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:32 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:32 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:33 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:33 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:33 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:33 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:34 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:34 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:34 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:34 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:35 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:35 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:35 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:35 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:36 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:36 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:36 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:36 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:37 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:37 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:37 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:37 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:38 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:38 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:38 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:38 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:39 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:39 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:39 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:39 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:40 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:40 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:40 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:40 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:41 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:41 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:41 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:41 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:42 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:42 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:42 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:42 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:43 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:43 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:43 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:43 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:44 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:44 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:44 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:44 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:45 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:45 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:45 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:45 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:46 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:46 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:46 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:46 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:47 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:47 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:47 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:47 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:48 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:48 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:48 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:48 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:49 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:49 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:49 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:49 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:50 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:50 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:50 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:50 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:51 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:51 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:51 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:51 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:52 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:52 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:52 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:52 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:53 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:53 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:53 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:53 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:54 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:54 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:54 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:54 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:55 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:55 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:55 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:55 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:56 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:56 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:56 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:56 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:57 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:57 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:57 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:57 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:58 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:58 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:58 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:58 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:59 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:59 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:27:59 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:27:59 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:00 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:00 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:00 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:00 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:01 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:01 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:01 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:01 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:02 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:02 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:02 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:02 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:03 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:03 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:03 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:03 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:04 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:04 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:04 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:04 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:05 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:05 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:05 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:05 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:06 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:06 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:06 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:06 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:07 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:07 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:07 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:07 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:08 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:08 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:08 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:08 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:09 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:09 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:09 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:09 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:10 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:10 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:10 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:10 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:11 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:11 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:11 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:11 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:12 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:12 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:12 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:12 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:13 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:13 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:13 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:13 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:14 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:14 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:14 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:14 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:15 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:15 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:15 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:15 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:16 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:16 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:16 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:16 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:17 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:17 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:17 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:17 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:18 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:18 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:18 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:18 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:19 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:19 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:19 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:19 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:20 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:20 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:20 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:20 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:21 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:21 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:21 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:21 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:22 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:22 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:22 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:22 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:23 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:23 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:23 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:23 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:24 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:24 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:24 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:24 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:25 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:25 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:25 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:25 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:26 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:26 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:26 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:26 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:27 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:27 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:27 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:27 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:28 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:28 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:28 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:28 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:29 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:29 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:29 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:29 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:30 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:30 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:30 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:30 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:31 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:31 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:31 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:31 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:32 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:32 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:32 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:32 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:33 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:33 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:33 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:33 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:34 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:34 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:34 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:34 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:35 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:35 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:35 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:35 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:36 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:36 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:36 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:36 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:37 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:37 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:37 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:37 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:38 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:38 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:38 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:38 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:39 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:39 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:39 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:39 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:40 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:40 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:40 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:40 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:41 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:41 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:41 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:41 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:42 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:42 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:42 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:42 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:43 scdaemon[16299] DBG: chan_5 <- RESTART 2017-03-17 20:28:43 scdaemon[16299] DBG: chan_5 -> OK 2017-03-17 20:28:43 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:43 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:43 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:43 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:44 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:44 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:44 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:44 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:45 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:45 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:45 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:45 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:46 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:46 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:46 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:46 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:47 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:47 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:47 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:47 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:48 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:48 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:48 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:48 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:49 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:49 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:49 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:49 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:50 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:50 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:50 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:50 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:51 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:51 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:51 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:51 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:52 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:52 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:52 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:52 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:53 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:53 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:53 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:53 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:54 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:54 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:54 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:54 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:55 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:55 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:55 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:55 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:56 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:56 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:56 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:56 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:57 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:57 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:57 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:57 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:58 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:58 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:58 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:58 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:59 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:59 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:28:59 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:28:59 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:29:00 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:29:00 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:29:00 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:29:00 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:29:01 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:29:01 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:29:01 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:29:01 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:29:02 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:29:02 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:29:02 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:29:02 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:29:03 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:29:03 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:29:03 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:29:03 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:29:04 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:29:04 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:29:04 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:29:04 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:29:05 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:29:05 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:29:05 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:29:05 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:29:06 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:29:06 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:29:06 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:29:06 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:29:07 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:29:07 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:29:07 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:29:07 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:29:08 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:29:08 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:29:08 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:29:08 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:29:09 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:29:09 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:29:09 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:29:09 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:29:10 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:29:10 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:29:10 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:29:10 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 2017-03-17 20:29:11 scdaemon[16299] DBG: enter: apdu_get_status: slot=0 hang=0 2017-03-17 20:29:11 scdaemon[16299] DBG: leave: apdu_get_status => sw=0x0 status=7 changecnt=2 From Pankaj.Chaurasia at smartusys.com Mon Mar 20 11:57:18 2017 From: Pankaj.Chaurasia at smartusys.com (Pankaj Kumar. Chaurasia) Date: Mon, 20 Mar 2017 10:57:18 +0000 Subject: Need Help. Message-ID: Does anyone know how to import a public key for a server account. I tried below one, but it is not working: Gpg2 -import -u NT\MSSQLAgent e:\MyPub.gpg Thanks & Regards, Pankaj K Chaurasia Sr. Database Developer Smart Utility Systems 0120-4208528 (O) | +91- 8109510013 (M) | +91- 9406929510 (M) pankaj.chaurasia at smartusys.com | www.smartusys.com [csWeekSIg0.1.3] [facebook][linkedin] [twitter] [google] This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. P Please consider the environment before printing this email. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 76121 bytes Desc: image001.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 1147 bytes Desc: image002.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 1240 bytes Desc: image003.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image004.png Type: image/png Size: 1270 bytes Desc: image004.png URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image005.png Type: image/png Size: 1669 bytes Desc: image005.png URL: From dkg at fifthhorseman.net Mon Mar 20 16:21:32 2017 From: dkg at fifthhorseman.net (Daniel Kahn Gillmor) Date: Mon, 20 Mar 2017 11:21:32 -0400 Subject: Need Help. In-Reply-To: References: Message-ID: <8737e8m0sj.fsf@alice.fifthhorseman.net> On Mon 2017-03-20 06:57:18 -0400, Pankaj Kumar. Chaurasia wrote: > Does anyone know how to import a public key for a server account. > > I tried below one, but it is not working: > > Gpg2 -import -u NT\MSSQLAgent e:\MyPub.gpg Usually --import needs two leading hyphens, not one. it's not clear to me what "NT\MSSQLAgent" is supposed to mean -- the -u flag is to identify an OpenPGP User ID, which isn't relevant for the --import operation. It looks like you're trying to use it to switch user accounts, which GnuPG won't do. You'll need to use your operating system's mechanism to switch user accounts first, and then run gpg from the other user. In Windows (which it looks like you're using) that'd be "Run as?" or something like that. --dkg -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 832 bytes Desc: not available URL: From dkg at fifthhorseman.net Mon Mar 20 16:30:12 2017 From: dkg at fifthhorseman.net (Daniel Kahn Gillmor) Date: Mon, 20 Mar 2017 11:30:12 -0400 Subject: dirmngr failes with missing file In-Reply-To: References: Message-ID: <87ziggkltn.fsf@alice.fifthhorseman.net> On Fri 2017-03-17 17:39:38 -0400, sivmu at web.de wrote: > When gpg -recv-key ID is used with the line > hkps://hkps.pool.sks-keyservers.net enabled in dirmngr.conf, it failes > with an error message saying dirmngr not found. What version of gpg? what version of dirmngr? can you please paste the exact error message? what specific kind of failure are you seeing -- does dirmngr itself actually fail, or does it just produce the warning and continue? --dkg -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 832 bytes Desc: not available URL: From patrick at enigmail.net Mon Mar 20 17:35:30 2017 From: patrick at enigmail.net (Patrick Brunschwig) Date: Mon, 20 Mar 2017 17:35:30 +0100 Subject: I figured out how to change the algorithms, In-Reply-To: <58CFA74B.1090901__46746.4957772338$1490003945$gmane$org@posteo.de> References: <58CF3AA2.8030707@posteo.de> <0ad6b764-9416-e89d-6ee3-8bd22d70801a@sixdemonbag.org> <58CFA74B.1090901__46746.4957772338$1490003945$gmane$org@posteo.de> Message-ID: <5a836fef-622c-8695-e29e-81838722161e@enigmail.net> On 20.03.17 10:56, zap wrote: > Okay, I was doing this to ecnrypt my files, not emails for the most part... > > I did however wonder, what you actually said, because I had pgp > encryption on and for some reason I couldn't read it through enigmail. I assume that's due to a configuration issue. But it's impossible to tell without further information, like what is the error message you are getting. -Patrick From Pankaj.Chaurasia at smartusys.com Tue Mar 21 05:05:17 2017 From: Pankaj.Chaurasia at smartusys.com (Pankaj Kumar. Chaurasia) Date: Tue, 21 Mar 2017 04:05:17 +0000 Subject: Need Help. In-Reply-To: <8737e8m0sj.fsf@alice.fifthhorseman.net> References: <8737e8m0sj.fsf@alice.fifthhorseman.net> Message-ID: Hi Daniel, Thanks for response. You are right, I am trying to import key for different user from which I have logged in. But the problem is I need to import the key for service account user. I do not allow to login. SQL Agent jobs run with this. I am trying to do this after reading below article: " gpg: decryption failed: No secret key I realised that I was being an idiot and that the service account that I was running the SQL Agent under did not have the certificate registered under that userid. I had only imported the certificate into Kleopatra for the development userid I logged in with and not for the service account. I simply imported the certificate to the service account profile and then everything worked. This meant that the original instructions and code were valid, but I thought I?d put this post up in case anyone did the same stupid thing as me. It?s worth remembering that the certificates are by default imported at a user level into Kleopatra. " Article link: http://globalgoat.com/2012/03/13/create-automated-pgp-task-in-ssis-using-gnupg/ Thanks & Regards, Pankaj K Chaurasia Sr. Database Developer Smart Utility Systems 0120-4208528 (O) ?|? +91- 8109510013 (M) |? +91- 9406929510 (M) pankaj.chaurasia at smartusys.com? |?www.smartusys.com ?? This message may contain confidential and/or privileged information. If you are not the addressee or authorized to receive this for the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message. Thank you for your cooperation. ? Please?consider the environment before printing this?email. -----Original Message----- From: Daniel Kahn Gillmor [mailto:dkg at fifthhorseman.net] Sent: Monday, March 20, 2017 8:52 PM To: Pankaj Kumar. Chaurasia; gnupg-users at gnupg.org Subject: Re: Need Help. On Mon 2017-03-20 06:57:18 -0400, Pankaj Kumar. Chaurasia wrote: > Does anyone know how to import a public key for a server account. > > I tried below one, but it is not working: > > Gpg2 -import -u NT\MSSQLAgent e:\MyPub.gpg Usually --import needs two leading hyphens, not one. it's not clear to me what "NT\MSSQLAgent" is supposed to mean -- the -u flag is to identify an OpenPGP User ID, which isn't relevant for the --import operation. It looks like you're trying to use it to switch user accounts, which GnuPG won't do. You'll need to use your operating system's mechanism to switch user accounts first, and then run gpg from the other user. In Windows (which it looks like you're using) that'd be "Run as?" or something like that. --dkg From terry.stewart at mrc-bsu.cam.ac.uk Wed Mar 22 00:10:14 2017 From: terry.stewart at mrc-bsu.cam.ac.uk (terry) Date: Tue, 21 Mar 2017 23:10:14 +0000 Subject: Compiling GPG on Solaris 10 Message-ID: <480e1184-4ea6-c3a8-705c-d15dadefd338@mrc-bsu.cam.ac.uk> Hi I'm having problems compiling GPG on a Solaris 10 server using gcc v.3.4.3 and gmake v.3.80 I've successfully compiled and installed the dependencies Libgpg-error (v 1.27) Libgcrypt (v 1.7.6) Libksba (v 1.3.5) Libassuan (v 2.4.3) nPth (v 1.3) as below ./configure (no arguments, just used default) gmake gmake check (all tests passed) gmake install All libraries went into /usr/local/lib by default where I can see them When it came to compiling gnupg-2.0.30 I have hit problems with configure, which fails with the following configure: checking system features for estream configure: *** *** You need libgcrypt to build this program. ** This library is for example available at *** ftp://ftp.gnupg.org/gcrypt/libgcrypt/ *** (at least version 1.5.0 using API 1 is required.) *** configure: *** *** It is now required to build with support for the *** GNU Portable Threads Library (Pth). Please install this *** library first. The library is for example available at *** ftp://ftp.gnu.org/gnu/pth/ *** On a Debian GNU/Linux system you can install it using *** apt-get install libpth-dev *** To build GnuPG for Windows you need to use the W32PTH *** package; available at: *** ftp://ftp.g10code.com/g10code/w32pth/ *** configure: error: *** *** Required libraries not found. Please consult the above messages *** and install them before running configure again. I then installed pth-2.0.7 (again configure, gmake, gmake check gmake install) and configure found pth, but I'm still getting the libgcrypt error I can see the libraries in /usr/local/lib -rwxr-xr-x 1 root root 274K Mar 21 17:46 libgpg-error.so.0.22.0 lrwxrwxrwx 1 root root 22 Mar 21 17:46 libgpg-error.so.0 -> libgpg-error.so.0.22.0 lrwxrwxrwx 1 root root 22 Mar 21 17:46 libgpg-error.so -> libgpg-error.so.0.22.0 -rwxr-xr-x 1 root root 1.1K Mar 21 17:46 libgpg-error.la -rwxr-xr-x 1 root root 477K Mar 21 17:47 libassuan.so.0.7.3 lrwxrwxrwx 1 root root 18 Mar 21 17:47 libassuan.so.0 -> libassuan.so.0.7.3 lrwxrwxrwx 1 root root 18 Mar 21 17:47 libassuan.so -> libassuan.so.0.7.3 -rwxr-xr-x 1 root root 1.2K Mar 21 17:47 libassuan.la -rwxr-xr-x 1 root root 844K Mar 21 17:48 libksba.so.8.11.6 lrwxrwxrwx 1 root root 17 Mar 21 17:48 libksba.so.8 -> libksba.so.8.11.6 lrwxrwxrwx 1 root root 17 Mar 21 17:48 libksba.so -> libksba.so.8.11.6 -rwxr-xr-x 1 root root 1.1K Mar 21 17:48 libksba.la -rwxr-xr-x 1 root root 17K Mar 21 17:49 libnpth.so.0.0.6 lrwxrwxrwx 1 root root 16 Mar 21 17:49 libnpth.so.0 -> libnpth.so.0.0.6 lrwxrwxrwx 1 root root 16 Mar 21 17:49 libnpth.so -> libnpth.so.0.0.6 -rwxr-xr-x 1 root root 925 Mar 21 17:49 libnpth.la -rwxr-xr-x 1 root root 3.0M Mar 21 18:03 libgcrypt.so.20.1.6 lrwxrwxrwx 1 root root 19 Mar 21 18:03 libgcrypt.so.20 -> libgcrypt.so.20.1.6 -rwxr-xr-x 1 root root 75K Mar 21 18:39 libpth.so.20.0.27 lrwxrwxrwx 1 root root 17 Mar 21 18:39 libpth.so.20 -> libpth.so.20.0.27 lrwxrwxrwx 1 root root 17 Mar 21 18:39 libpth.so -> libpth.so.20.0.27 -rwxr-xr-x 1 root root 791 Mar 21 18:39 libpth.la -rw-r--r-- 1 root root 93K Mar 21 18:39 libpth.a -rwxr-xr-x 1 root root 1.7M Mar 21 20:18 libgcrypt.so.11.8.4 lrwxrwxrwx 1 root root 19 Mar 21 20:18 libgcrypt.so.11 -> libgcrypt.so.11.8.4 lrwxrwxrwx 1 root root 19 Mar 21 20:18 libgcrypt.so -> libgcrypt.so.11.8.4 -rwxr-xr-x 1 root root 1.2K Mar 21 20:18 libgcrypt.la and have set LD_LIBRARY_PATH to /usr/local/lib ,but can't make any headway Do you have any suggestions on how to proceed? -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy903p at gmail.com Wed Mar 22 03:10:17 2017 From: andy903p at gmail.com (=?UTF-8?Q?Andreas_H=C3=B6rmandinger?=) Date: Wed, 22 Mar 2017 03:10:17 +0100 Subject: Compiling GPG on Solaris 10 In-Reply-To: References: <480e1184-4ea6-c3a8-705c-d15dadefd338@mrc-bsu.cam.ac.uk> Message-ID: sorry, configureac isn't supposed to be a link. but here would be a link to it https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=blob;f=configure.ac;h=0041bec526c69baff880d4964f6b4260d8c11318;hb=refs/heads/STABLE-BRANCH-2-0 2017-03-22 3:08 GMT+01:00 Andreas H?rmandinger : > Hi, > > do you have automake too? > If you take a quick look at *configure.ac * of gpg > 2.0, you will notice that it checks the presence of libgcrypt via the > automake macro > > *AM_PATH_LIBGCRYPT.* > hth, > Andy > > 2017-03-22 0:10 GMT+01:00 terry : > >> Hi >> I'm having problems compiling GPG on a Solaris 10 server using gcc >> v.3.4.3 and gmake v.3.80 >> >> I've successfully compiled and installed the dependencies >> >> Libgpg-error (v 1.27) >> Libgcrypt (v 1.7.6) >> Libksba (v 1.3.5) >> Libassuan (v 2.4.3) >> nPth (v 1.3) >> as below >> >> ./configure (no arguments, just used default) >> gmake >> gmake check (all tests passed) >> gmake install >> >> All libraries went into /usr/local/lib by default where I can see them >> When it came to compiling gnupg-2.0.30 I have hit problems with configure, >> which fails with the following >> configure: checking system features for estream >> configure: >> *** >> *** You need libgcrypt to build this program. >> ** This library is for example available at >> *** ftp://ftp.gnupg.org/gcrypt/libgcrypt/ >> *** (at least version 1.5.0 using API 1 is required.) >> *** >> configure: >> *** >> *** It is now required to build with support for the >> *** GNU Portable Threads Library (Pth). Please install this >> *** library first. The library is for example available at >> *** ftp://ftp.gnu.org/gnu/pth/ >> *** On a Debian GNU/Linux system you can install it using >> *** apt-get install libpth-dev >> *** To build GnuPG for Windows you need to use the W32PTH >> *** package; available at: >> *** ftp://ftp.g10code.com/g10code/w32pth/ >> *** >> configure: error: >> *** >> *** Required libraries not found. Please consult the above messages >> *** and install them before running configure again. >> >> I then installed pth-2.0.7 (again configure, gmake, gmake check gmake >> install) and configure found pth, but I'm still getting the libgcrypt >> error >> I can see the libraries in /usr/local/lib >> -rwxr-xr-x 1 root root 274K Mar 21 17:46 >> libgpg-error.so.0.22.0 >> lrwxrwxrwx 1 root root 22 Mar 21 17:46 libgpg-error.so.0 >> -> libgpg-error.so.0.22.0 >> lrwxrwxrwx 1 root root 22 Mar 21 17:46 libgpg-error.so -> >> libgpg-error.so.0.22.0 >> -rwxr-xr-x 1 root root 1.1K Mar 21 17:46 libgpg-error.la >> -rwxr-xr-x 1 root root 477K Mar 21 17:47 libassuan.so.0.7.3 >> lrwxrwxrwx 1 root root 18 Mar 21 17:47 libassuan.so.0 -> >> libassuan.so.0.7.3 >> lrwxrwxrwx 1 root root 18 Mar 21 17:47 libassuan.so -> >> libassuan.so.0.7.3 >> -rwxr-xr-x 1 root root 1.2K Mar 21 17:47 libassuan.la >> -rwxr-xr-x 1 root root 844K Mar 21 17:48 libksba.so.8.11.6 >> lrwxrwxrwx 1 root root 17 Mar 21 17:48 libksba.so.8 -> >> libksba.so.8.11.6 >> lrwxrwxrwx 1 root root 17 Mar 21 17:48 libksba.so -> >> libksba.so.8.11.6 >> -rwxr-xr-x 1 root root 1.1K Mar 21 17:48 libksba.la >> -rwxr-xr-x 1 root root 17K Mar 21 17:49 libnpth.so.0.0.6 >> lrwxrwxrwx 1 root root 16 Mar 21 17:49 libnpth.so.0 -> >> libnpth.so.0.0.6 >> lrwxrwxrwx 1 root root 16 Mar 21 17:49 libnpth.so -> >> libnpth.so.0.0.6 >> -rwxr-xr-x 1 root root 925 Mar 21 17:49 libnpth.la >> -rwxr-xr-x 1 root root 3.0M Mar 21 18:03 libgcrypt.so.20.1.6 >> lrwxrwxrwx 1 root root 19 Mar 21 18:03 libgcrypt.so.20 -> >> libgcrypt.so.20.1.6 >> -rwxr-xr-x 1 root root 75K Mar 21 18:39 libpth.so.20.0.27 >> lrwxrwxrwx 1 root root 17 Mar 21 18:39 libpth.so.20 -> >> libpth.so.20.0.27 >> lrwxrwxrwx 1 root root 17 Mar 21 18:39 libpth.so -> >> libpth.so.20.0.27 >> -rwxr-xr-x 1 root root 791 Mar 21 18:39 libpth.la >> -rw-r--r-- 1 root root 93K Mar 21 18:39 libpth.a >> -rwxr-xr-x 1 root root 1.7M Mar 21 20:18 libgcrypt.so.11.8.4 >> lrwxrwxrwx 1 root root 19 Mar 21 20:18 libgcrypt.so.11 -> >> libgcrypt.so.11.8.4 >> lrwxrwxrwx 1 root root 19 Mar 21 20:18 libgcrypt.so -> >> libgcrypt.so.11.8.4 >> -rwxr-xr-x 1 root root 1.2K Mar 21 20:18 libgcrypt.la >> >> and have set LD_LIBRARY_PATH to /usr/local/lib ,but can't make any >> headway >> Do you have any suggestions on how to proceed? >> >> _______________________________________________ >> Gnupg-users mailing list >> Gnupg-users at gnupg.org >> http://lists.gnupg.org/mailman/listinfo/gnupg-users >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: From andy903p at gmail.com Wed Mar 22 03:08:49 2017 From: andy903p at gmail.com (=?UTF-8?Q?Andreas_H=C3=B6rmandinger?=) Date: Wed, 22 Mar 2017 03:08:49 +0100 Subject: Compiling GPG on Solaris 10 In-Reply-To: <480e1184-4ea6-c3a8-705c-d15dadefd338@mrc-bsu.cam.ac.uk> References: <480e1184-4ea6-c3a8-705c-d15dadefd338@mrc-bsu.cam.ac.uk> Message-ID: Hi, do you have automake too? If you take a quick look at *configure.ac * of gpg 2.0, you will notice that it checks the presence of libgcrypt via the automake macro *AM_PATH_LIBGCRYPT.* hth, Andy 2017-03-22 0:10 GMT+01:00 terry : > Hi > I'm having problems compiling GPG on a Solaris 10 server using gcc v.3.4.3 > and gmake v.3.80 > > I've successfully compiled and installed the dependencies > > Libgpg-error (v 1.27) > Libgcrypt (v 1.7.6) > Libksba (v 1.3.5) > Libassuan (v 2.4.3) > nPth (v 1.3) > as below > > ./configure (no arguments, just used default) > gmake > gmake check (all tests passed) > gmake install > > All libraries went into /usr/local/lib by default where I can see them > When it came to compiling gnupg-2.0.30 I have hit problems with configure, > which fails with the following > configure: checking system features for estream > configure: > *** > *** You need libgcrypt to build this program. > ** This library is for example available at > *** ftp://ftp.gnupg.org/gcrypt/libgcrypt/ > *** (at least version 1.5.0 using API 1 is required.) > *** > configure: > *** > *** It is now required to build with support for the > *** GNU Portable Threads Library (Pth). Please install this > *** library first. The library is for example available at > *** ftp://ftp.gnu.org/gnu/pth/ > *** On a Debian GNU/Linux system you can install it using > *** apt-get install libpth-dev > *** To build GnuPG for Windows you need to use the W32PTH > *** package; available at: > *** ftp://ftp.g10code.com/g10code/w32pth/ > *** > configure: error: > *** > *** Required libraries not found. Please consult the above messages > *** and install them before running configure again. > > I then installed pth-2.0.7 (again configure, gmake, gmake check gmake > install) and configure found pth, but I'm still getting the libgcrypt > error > I can see the libraries in /usr/local/lib > -rwxr-xr-x 1 root root 274K Mar 21 17:46 > libgpg-error.so.0.22.0 > lrwxrwxrwx 1 root root 22 Mar 21 17:46 libgpg-error.so.0 -> > libgpg-error.so.0.22.0 > lrwxrwxrwx 1 root root 22 Mar 21 17:46 libgpg-error.so -> > libgpg-error.so.0.22.0 > -rwxr-xr-x 1 root root 1.1K Mar 21 17:46 libgpg-error.la > -rwxr-xr-x 1 root root 477K Mar 21 17:47 libassuan.so.0.7.3 > lrwxrwxrwx 1 root root 18 Mar 21 17:47 libassuan.so.0 -> > libassuan.so.0.7.3 > lrwxrwxrwx 1 root root 18 Mar 21 17:47 libassuan.so -> > libassuan.so.0.7.3 > -rwxr-xr-x 1 root root 1.2K Mar 21 17:47 libassuan.la > -rwxr-xr-x 1 root root 844K Mar 21 17:48 libksba.so.8.11.6 > lrwxrwxrwx 1 root root 17 Mar 21 17:48 libksba.so.8 -> > libksba.so.8.11.6 > lrwxrwxrwx 1 root root 17 Mar 21 17:48 libksba.so -> > libksba.so.8.11.6 > -rwxr-xr-x 1 root root 1.1K Mar 21 17:48 libksba.la > -rwxr-xr-x 1 root root 17K Mar 21 17:49 libnpth.so.0.0.6 > lrwxrwxrwx 1 root root 16 Mar 21 17:49 libnpth.so.0 -> > libnpth.so.0.0.6 > lrwxrwxrwx 1 root root 16 Mar 21 17:49 libnpth.so -> > libnpth.so.0.0.6 > -rwxr-xr-x 1 root root 925 Mar 21 17:49 libnpth.la > -rwxr-xr-x 1 root root 3.0M Mar 21 18:03 libgcrypt.so.20.1.6 > lrwxrwxrwx 1 root root 19 Mar 21 18:03 libgcrypt.so.20 -> > libgcrypt.so.20.1.6 > -rwxr-xr-x 1 root root 75K Mar 21 18:39 libpth.so.20.0.27 > lrwxrwxrwx 1 root root 17 Mar 21 18:39 libpth.so.20 -> > libpth.so.20.0.27 > lrwxrwxrwx 1 root root 17 Mar 21 18:39 libpth.so -> > libpth.so.20.0.27 > -rwxr-xr-x 1 root root 791 Mar 21 18:39 libpth.la > -rw-r--r-- 1 root root 93K Mar 21 18:39 libpth.a > -rwxr-xr-x 1 root root 1.7M Mar 21 20:18 libgcrypt.so.11.8.4 > lrwxrwxrwx 1 root root 19 Mar 21 20:18 libgcrypt.so.11 -> > libgcrypt.so.11.8.4 > lrwxrwxrwx 1 root root 19 Mar 21 20:18 libgcrypt.so -> > libgcrypt.so.11.8.4 > -rwxr-xr-x 1 root root 1.2K Mar 21 20:18 libgcrypt.la > > and have set LD_LIBRARY_PATH to /usr/local/lib ,but can't make any headway > Do you have any suggestions on how to proceed? > > _______________________________________________ > Gnupg-users mailing list > Gnupg-users at gnupg.org > http://lists.gnupg.org/mailman/listinfo/gnupg-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From wk at gnupg.org Wed Mar 22 08:33:56 2017 From: wk at gnupg.org (Werner Koch) Date: Wed, 22 Mar 2017 08:33:56 +0100 Subject: Compiling GPG on Solaris 10 In-Reply-To: <480e1184-4ea6-c3a8-705c-d15dadefd338@mrc-bsu.cam.ac.uk> (terry's message of "Tue, 21 Mar 2017 23:10:14 +0000") References: <480e1184-4ea6-c3a8-705c-d15dadefd338@mrc-bsu.cam.ac.uk> Message-ID: <87poh9ix3v.fsf@wheatstone.g10code.de> On Wed, 22 Mar 2017 00:10, terry.stewart at mrc-bsu.cam.ac.uk said: > *** You need libgcrypt to build this program. > ** This library is for example available at > *** ftp://ftp.gnupg.org/gcrypt/libgcrypt/ > *** (at least version 1.5.0 using API 1 is required.) Did you install the development package for Libgcrypt or build and installed it yourself? /usr/local/bin/libgcrypt-config --version Is the first thing which configure runs to get the libgcrypt configuration (then --libs and --cflags is used). If you look into config.log or scroll your tty up for the output of configure, you will see some lines explaining why Libgcrypt was not found. Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From peter at digitalbrains.com Wed Mar 22 13:28:02 2017 From: peter at digitalbrains.com (Peter Lebbing) Date: Wed, 22 Mar 2017 13:28:02 +0100 Subject: Mac Pinentry problem In-Reply-To: <946F0E18-5040-4A2A-AB8E-6B3394ED34AC@hoerbe.at> References: <946F0E18-5040-4A2A-AB8E-6B3394ED34AC@hoerbe.at> Message-ID: <3214628e-eea6-b2d5-d578-d477ebfa0b76@digitalbrains.com> On 17/03/17 22:44, Rainer Hoerbe wrote: > I copied my key to a OpenPGP card and was able to create signatures > and authentication via SSH using the card. Now moving the the Mac I > am stuck with pinentry-mac, because it keeps asking me for another > card. I think GnuPG hasn't deleted your secret key stubs which still point to the old smartcard with the different serial number. Unless I'm very much mistaken, this is a shortcoming of GnuPG 2.1 currently. The agent identifies keys by their so-called keygrip. You can see the keygrips for your private key with: $ gpg2 --with-keygrip -K 64C2F99E904F1906 These keygrips correspond to files in ~/.gnupg/private-keys-v1.d/. Just bluntly remove these files, but be careful to only delete files belonging to smartcard stubs! Double check each keygrip before deleting them. In fact, make a backup of the directory first :-). > gpg --delete-secret-keys 0x64C2F99E904F1906 > gpg2 --card-status > gpg2 --clearsign /etc/hosts Did you mean to write "gpg" there rather than "gpg2"? You didn't indicate which version of GnuPG you're using, but your problem sounds like a 2.1 problem to me. If you are using GnuPG 2.1, you shouldn't mix it with GnuPG 1.4, that road leads to pain. They don't share their private key storage, and might or might not share public key storage depending on which version created the public key storage on the very first invocation. HTH, Peter. -- I use the GNU Privacy Guard (GnuPG) in combination with Enigmail. You can send me encrypted mail if you want some privacy. My key is available at -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From terry.stewart at mrc-bsu.cam.ac.uk Wed Mar 22 14:12:16 2017 From: terry.stewart at mrc-bsu.cam.ac.uk (Terry Stewart) Date: Wed, 22 Mar 2017 13:12:16 +0000 Subject: Compiling GPG on Solaris 10 In-Reply-To: References: <480e1184-4ea6-c3a8-705c-d15dadefd338@mrc-bsu.cam.ac.uk> Message-ID: <201e5217-dc78-e9da-327e-85abc898fa72@mrc-bsu.cam.ac.uk> Hi Andy I didn't have, but I've just installed it now. 13:07:>> automake --version automake (GNU automake) 1.15 However no luck, still failing with the same error checking for deflateInit2_ in -lz... yes checking for bzlib.h... yes checking for BZ2_bzCompressInit in -lbz2... yes checking whether readline via "-lreadline" is present and sane... no checking whether readline via "-lreadline -ltermcap" is present and sane... no checking whether readline via "-lreadline -lcurses" is present and sane... no checking whether readline via "-lreadline -lncurses" is present and sane... no configure: checking for cc features checking if gcc ignores unknown -Wno-* options... no checking if gcc supports -Wno-pointer-sign... no checking if gcc supports -Wpointer-arith... yes configure: checking system features for estream-printf checking for stdint.h... (cached) yes checking for long long int... (cached) yes checking for long double... yes checking for intmax_t... yes checking for uintmax_t... yes checking for ptrdiff_t... yes checking size of unsigned long... (cached) 4 checking size of void *... 4 checking for nl_langinfo and THOUSANDS_SEP... no configure: checking system features for estream configure: *** *** You need libgcrypt to build this program. ** This library is for example available at *** ftp://ftp.gnupg.org/gcrypt/libgcrypt/ *** (at least version 1.5.0 using API 1 is required.) *** configure: error: *** *** Required libraries not found. Please consult the above messages *** and install them before running configure again. *** On 22/03/17 02:08, Andreas H?rmandinger wrote: > Hi, > > do you have automake too? > If you take a quick look at *configure.ac * of > gpg 2.0, you will notice that it checks the presence of libgcrypt via > the automake macro *AM_PATH_LIBGCRYPT. > > * > hth, > Andy > > 2017-03-22 0:10 GMT+01:00 terry >: > > Hi > I'm having problems compiling GPG on a Solaris 10 server using gcc > v.3.4.3 and gmake v.3.80 > > I've successfully compiled and installed the dependencies > > Libgpg-error (v 1.27) > Libgcrypt (v 1.7.6) > Libksba (v 1.3.5) > Libassuan (v 2.4.3) > nPth (v 1.3) > as below > > ./configure (no arguments, just used default) > gmake > gmake check (all tests passed) > gmake install > > All libraries went into /usr/local/lib by default where I can see them > When it came to compiling gnupg-2.0.30 I have hit problems with > configure, which fails with the following > configure: checking system features for estream > configure: > *** > *** You need libgcrypt to build this program. > ** This library is for example available at > *** ftp://ftp.gnupg.org/gcrypt/libgcrypt/ > > *** (at least version 1.5.0 using API 1 is required.) > *** > configure: > *** > *** It is now required to build with support for the > *** GNU Portable Threads Library (Pth). Please install this > *** library first. The library is for example available at > *** ftp://ftp.gnu.org/gnu/pth/ > *** On a Debian GNU/Linux system you can install it using > *** apt-get install libpth-dev > *** To build GnuPG for Windows you need to use the W32PTH > *** package; available at: > *** ftp://ftp.g10code.com/g10code/w32pth/ > > *** > configure: error: > *** > *** Required libraries not found. Please consult the above messages > *** and install them before running configure again. > > I then installed pth-2.0.7 (again configure, gmake, gmake check > gmake install) and configure found pth, but I'm still getting the > libgcrypt error > I can see the libraries in /usr/local/lib > -rwxr-xr-x 1 root root 274K Mar 21 17:46 > libgpg-error.so.0.22.0 > lrwxrwxrwx 1 root root 22 Mar 21 17:46 > libgpg-error.so.0 -> libgpg-error.so.0.22.0 > lrwxrwxrwx 1 root root 22 Mar 21 17:46 > libgpg-error.so -> libgpg-error.so.0.22.0 > -rwxr-xr-x 1 root root 1.1K Mar 21 17:46 > libgpg-error.la > -rwxr-xr-x 1 root root 477K Mar 21 17:47 > libassuan.so.0.7.3 > lrwxrwxrwx 1 root root 18 Mar 21 17:47 > libassuan.so.0 -> libassuan.so.0.7.3 > lrwxrwxrwx 1 root root 18 Mar 21 17:47 libassuan.so > -> libassuan.so.0.7.3 > -rwxr-xr-x 1 root root 1.2K Mar 21 17:47 libassuan.la > > -rwxr-xr-x 1 root root 844K Mar 21 17:48 > libksba.so.8.11.6 > lrwxrwxrwx 1 root root 17 Mar 21 17:48 libksba.so.8 > -> libksba.so.8.11.6 > lrwxrwxrwx 1 root root 17 Mar 21 17:48 libksba.so > -> libksba.so.8.11.6 > -rwxr-xr-x 1 root root 1.1K Mar 21 17:48 libksba.la > > -rwxr-xr-x 1 root root 17K Mar 21 17:49 libnpth.so.0.0.6 > lrwxrwxrwx 1 root root 16 Mar 21 17:49 libnpth.so.0 > -> libnpth.so.0.0.6 > lrwxrwxrwx 1 root root 16 Mar 21 17:49 libnpth.so > -> libnpth.so.0.0.6 > -rwxr-xr-x 1 root root 925 Mar 21 17:49 libnpth.la > > -rwxr-xr-x 1 root root 3.0M Mar 21 18:03 > libgcrypt.so.20.1.6 > lrwxrwxrwx 1 root root 19 Mar 21 18:03 > libgcrypt.so.20 -> libgcrypt.so.20.1.6 > -rwxr-xr-x 1 root root 75K Mar 21 18:39 > libpth.so.20.0.27 > lrwxrwxrwx 1 root root 17 Mar 21 18:39 libpth.so.20 > -> libpth.so.20.0.27 > lrwxrwxrwx 1 root root 17 Mar 21 18:39 libpth.so -> > libpth.so.20.0.27 > -rwxr-xr-x 1 root root 791 Mar 21 18:39 libpth.la > > -rw-r--r-- 1 root root 93K Mar 21 18:39 libpth.a > -rwxr-xr-x 1 root root 1.7M Mar 21 20:18 > libgcrypt.so.11.8.4 > lrwxrwxrwx 1 root root 19 Mar 21 20:18 > libgcrypt.so.11 -> libgcrypt.so.11.8.4 > lrwxrwxrwx 1 root root 19 Mar 21 20:18 libgcrypt.so > -> libgcrypt.so.11.8.4 > -rwxr-xr-x 1 root root 1.2K Mar 21 20:18 libgcrypt.la > > > and have set LD_LIBRARY_PATH to /usr/local/lib ,but can't make any > headway > Do you have any suggestions on how to proceed? > > > _______________________________________________ > Gnupg-users mailing list > Gnupg-users at gnupg.org > http://lists.gnupg.org/mailman/listinfo/gnupg-users > > > -- Terry Stewart MRC Biostatistics Unit Cambridge Institute of Public Health Forvie Site Robinson Way Cambridge Biomedical Campus Cambridge CB2 0SR -------------- next part -------------- An HTML attachment was scrubbed... URL: From terry.stewart at mrc-bsu.cam.ac.uk Wed Mar 22 14:32:33 2017 From: terry.stewart at mrc-bsu.cam.ac.uk (Terry Stewart) Date: Wed, 22 Mar 2017 13:32:33 +0000 Subject: Compiling GPG on Solaris 10 In-Reply-To: <87poh9ix3v.fsf@wheatstone.g10code.de> References: <480e1184-4ea6-c3a8-705c-d15dadefd338@mrc-bsu.cam.ac.uk> <87poh9ix3v.fsf@wheatstone.g10code.de> Message-ID: Hi Werner Thanks for replying. I compiled libgcrypt from source (from https://www.gnupg.org/download/index.html) as well as the other dependencies All these dependencies installed without error using ./configure gmake gmake check gmake install >> /usr/local/bin/libgcrypt-config --version 1.7.6 Configure was complaining about readline so I reinstalled that as well checking whether regular expression support is requested... yes checking for library containing regcomp... none required checking for regcomp... yes checking whether your system's regexp library is broken... no checking zlib.h usability... yes checking zlib.h presence... yes checking for zlib.h... yes checking for deflateInit2_ in -lz... yes checking for bzlib.h... yes checking for BZ2_bzCompressInit in -lbz2... yes checking whether readline via "-lreadline" is present and sane... no checking whether readline via "-lreadline -ltermcap" is present and sane... yes configure: checking for cc features checking if gcc ignores unknown -Wno-* options... no checking if gcc supports -Wno-pointer-sign... no checking if gcc supports -Wpointer-arith... yes configure: checking system features for estream-printf checking for stdint.h... (cached) yes checking for long long int... (cached) yes checking for long double... yes checking for intmax_t... yes checking for uintmax_t... yes checking for ptrdiff_t... yes checking size of unsigned long... (cached) 4 checking size of void *... 4 checking for nl_langinfo and THOUSANDS_SEP... no configure: checking system features for estream configure: *** *** You need libgcrypt to build this program. ** This library is for example available at *** ftp://ftp.gnupg.org/gcrypt/libgcrypt/ *** (at least version 1.5.0 using API 1 is required.) *** configure: error: On 22/03/17 07:33, Werner Koch wrote: > On Wed, 22 Mar 2017 00:10, terry.stewart at mrc-bsu.cam.ac.uk said: > >> *** You need libgcrypt to build this program. >> ** This library is for example available at >> *** ftp://ftp.gnupg.org/gcrypt/libgcrypt/ >> *** (at least version 1.5.0 using API 1 is required.) > Did you install the development package for Libgcrypt or build and > installed it yourself? > > /usr/local/bin/libgcrypt-config --version > > Is the first thing which configure runs to get the libgcrypt > configuration (then --libs and --cflags is used). > > If you look into config.log or scroll your tty up for the output of > configure, you will see some lines explaining why Libgcrypt was not > found. > > > Shalom-Salam, > > Werner > -- Terry Stewart MRC Biostatistics Unit Cambridge Institute of Public Health Forvie Site Robinson Way Cambridge Biomedical Campus Cambridge CB2 0SR -------------- next part -------------- An HTML attachment was scrubbed... URL: From terry.stewart at mrc-bsu.cam.ac.uk Wed Mar 22 17:04:17 2017 From: terry.stewart at mrc-bsu.cam.ac.uk (Terry Stewart) Date: Wed, 22 Mar 2017 16:04:17 +0000 Subject: Compiling GPG on Solaris 10 In-Reply-To: <87poh9ix3v.fsf@wheatstone.g10code.de> References: <480e1184-4ea6-c3a8-705c-d15dadefd338@mrc-bsu.cam.ac.uk> <87poh9ix3v.fsf@wheatstone.g10code.de> Message-ID: <044479b4-8c3b-9a7a-bfaa-12ae9ea8410c@mrc-bsu.cam.ac.uk> Thanks for the help everyone Looking on my system I found an old version of libgcrypt-config in /usr/bin. I was installing into /usr/local/bin but /usr/bin was before that in my PATH All working and compiled now Regards Terry On 22/03/17 07:33, Werner Koch wrote: > On Wed, 22 Mar 2017 00:10, terry.stewart at mrc-bsu.cam.ac.uk said: > >> *** You need libgcrypt to build this program. >> ** This library is for example available at >> *** ftp://ftp.gnupg.org/gcrypt/libgcrypt/ >> *** (at least version 1.5.0 using API 1 is required.) > Did you install the development package for Libgcrypt or build and > installed it yourself? > > /usr/local/bin/libgcrypt-config --version > > Is the first thing which configure runs to get the libgcrypt > configuration (then --libs and --cflags is used). > > If you look into config.log or scroll your tty up for the output of > configure, you will see some lines explaining why Libgcrypt was not > found. > > > Shalom-Salam, > > Werner > -- Terry Stewart MRC Biostatistics Unit Cambridge Institute of Public Health Forvie Site Robinson Way Cambridge Biomedical Campus Cambridge CB2 0SR -------------- next part -------------- An HTML attachment was scrubbed... URL: From ssmeenk at freshdot.net Wed Mar 22 15:46:32 2017 From: ssmeenk at freshdot.net (Sander Smeenk) Date: Wed, 22 Mar 2017 15:46:32 +0100 Subject: GnuPGv2 & 'pinentry' on Linux w/ remote access Message-ID: <20170322144632.GA17716@dot.dmz.freshdot.net> Hi, I'm trying to make the big step from GnuPG v1 to v2 but i'm experiencing agonizing pains caused by the forced use of "pinentry" by gpg-agent and friends, or rather the way the GPG_TTY stuff works? I'm on Linux and i am not using Unity/Gnome/whatever, so i start X by calling 'startx' and it invokes my .xsession that has ... | GPG_TTY=$(tty) | export GPG_TTY | eval $(gpg-agent --daemon) ... where ssh-agent used to be, just before starting the window manager. Then i have this gpg-agent.conf: | enable-ssh-support | pinentry-program /usr/bin/pinentry-curses | default-cache-ttl 300 | max-cache-ttl 999999 With this config, trying to decrypt a GPG-file, everything stalls and undescriptive errors appear after staring at a blinking cursor for quite some time. So i learned that i could update GPG_TTY from my shellrc by doing... | GPG_TTY=$(tty) | export GPG_TTY | gpg-connect-agent updatestartuptty /bye >/dev/null ... every time a new shell spawns. This kind-of works. At least the pinentry pops up in a terminal. For GPG-related commands, the pinentry seems to pop-up at the terminal that is running a GPG-related command, but trying to use ssh randomly pops the pinentry in a terminal unrelated to where i am running ssh. Probably the terminal that was started last? Then, when i then ^C the ssh command that is seemingly hanging because a pinentry popped up on some other workspace's terminal, the pinentry program on the unrelated terminal completely messes up said terminal. Sometimes resulting in *'s being displayed while typing, or letters disappearing from the input altogether. In such situations it turns out pinentry-curses was still running, even though my shell was also interactive. I can't fathom what i am doing wrong but i must be doing something wrong. Any tips? And i haven't even started looking at "how can u use a gpg-agent that is already running on a box that i am logging in remotely" yet, sort of what 'keychain' can do with ssh-agent. Regards, -Sndr. -- | How can there be self-help "groups"? | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2 From shrivastavasubhash5 at gmail.com Wed Mar 22 12:41:50 2017 From: shrivastavasubhash5 at gmail.com (Subhash Shrivastava) Date: Wed, 22 Mar 2017 03:41:50 -0800 Subject: Enquiry about the GnuPGP Message-ID: What is the full form of GnuPG -------------- next part -------------- An HTML attachment was scrubbed... URL: From michaels at syapse.com Thu Mar 23 02:32:17 2017 From: michaels at syapse.com (Michael Smith) Date: Wed, 22 Mar 2017 21:32:17 -0400 Subject: Parallel decrypts fail in 2.1.19 Message-ID: We use gpg extensively, particularly as a part of salt-ssh. Lately, salt-ssh runs against multiple instances have begun to fail in rendering gpg-encrypted data. Looking into it, I learned that running one gpg -d at a time works without any problem, but several runs in parallel fail. 1. I create a file encrypted to myself. (I'm the default recipient.) $ gpg -qeo junk <<< junk 2. I can decrypt the file if it's in a single run. $ gpg -qd junk junk 3. I cannot decrypt the junk with 10 runs in parallel. (Pinentry opens during this run.) $ yes junk | head -n10 | xargs -n1 -P10 gpg -qd gpg: decryption failed: No secret key gpg: decryption failed: No secret key gpg: decryption failed: No secret key gpg: decryption failed: No secret key gpg: decryption failed: No secret key gpg: decryption failed: No secret key gpg: decryption failed: No secret key gpg: decryption failed: No secret key gpg: decryption failed: No secret key gpg: decryption failed: No secret key 4. gpg-agent is no longer running So... I threw these options into ~/.gnupg/gpg-agent.log: debug-pinentry debug-level guru log-file /tmp/agent.log debug 1024 verbose And tried the above again. This bit caught my eye: 2017-03-22 21:25:13 gpg-agent[3624] Warning: using insecure memory! 56ab56... 2017-03-22 21:25:14 gpg-agent[3624] DBG: rsa_decrypt res: [out of core] 2017-03-22 21:25:14 gpg-agent[3624] Ohhhh jeeee: ... this is a bug (sexp.c:1433:do_vsexp_sscan) I searched for that output online and came across this message: https://lists.gnutls.org/pipermail/gnupg-devel/2017-January/032489.html The description there matches my experience, but that particular double free seems to have been resolved already in 2.1.18, so I guess I'm seeing a new bug. Has anyone come across this? $ gpg --version gpg (GnuPG) 2.1.19 libgcrypt 1.7.6 - Michael A. Smith From rainer at hoerbe.at Thu Mar 23 07:33:36 2017 From: rainer at hoerbe.at (Rainer Hoerbe) Date: Thu, 23 Mar 2017 07:33:36 +0100 Subject: haaveged + gpg --sign fails with "signing failed: Operation cancelled" Message-ID: <8B14507D-44AE-4725-B766-5D148311D916@hoerbe.at> Just for the record: Adding entropy using haveged does not work in my setup - it will cause the signature to fail without useful error message. My setup is: Linux keymgmt 4.9.14-200.fc25.x86_64 #1 SMP Mon Mar 13 19:26:40 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux gpg (GnuPG) 2.0.22 libgcrypt 1.5.3 The procedure that repeatedly fails when including haveged: sudo /usr/sbin/pcscd sudo /usr/sbin/haveged gpg2 --import my_pub.gpg gpg2 --card-status echo -e "trust\n5\ny" > /tmp/gpg_editkey.cmd gpg2 --command-file /tmp/gpg_editkey.cmd --edit-key gpg2 --sign mydoc.txt Regards, Rainer H?rbe Identinetics GmbH From peter at digitalbrains.com Thu Mar 23 11:40:34 2017 From: peter at digitalbrains.com (Peter Lebbing) Date: Thu, 23 Mar 2017 11:40:34 +0100 Subject: GnuPGv2 & 'pinentry' on Linux w/ remote access In-Reply-To: <20170322144632.GA17716@dot.dmz.freshdot.net> References: <20170322144632.GA17716@dot.dmz.freshdot.net> Message-ID: <7d2e0dfc-6633-f0b1-62ec-44c6a0944402@digitalbrains.com> Hi Sndr, On 22/03/17 15:46, Sander Smeenk via Gnupg-users wrote: > I'm trying to make the big step from GnuPG v1 to v2 but i'm experiencing > agonizing pains caused by the forced use of "pinentry" by gpg-agent and > friends, or rather the way the GPG_TTY stuff works? The first thing we really need to know before we can give good help, is: which version of GnuPG are you using? $ gpg2 --version gpg (GnuPG) 2.1.18 libgcrypt 1.7.6-beta [...] Cheers, Peter. -- I use the GNU Privacy Guard (GnuPG) in combination with Enigmail. You can send me encrypted mail if you want some privacy. My key is available at -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From wk at gnupg.org Thu Mar 23 17:35:34 2017 From: wk at gnupg.org (Werner Koch) Date: Thu, 23 Mar 2017 17:35:34 +0100 Subject: Compiling GPG on Solaris 10 In-Reply-To: (Terry Stewart's message of "Wed, 22 Mar 2017 13:32:33 +0000") References: <480e1184-4ea6-c3a8-705c-d15dadefd338@mrc-bsu.cam.ac.uk> <87poh9ix3v.fsf@wheatstone.g10code.de> Message-ID: <8737e4lzmx.fsf@wheatstone.g10code.de> On Wed, 22 Mar 2017 14:32, terry.stewart at mrc-bsu.cam.ac.uk said: Hi, The quoted part of the log is unfortunately not what I am looking for. Please check the log for lines similar to this: configure: checking for libraries checking for gpg-error-config... /usr/local/bin/gpg-error-config checking for GPG Error - version >= 1.11... yes (1.27-beta8) checking for libgcrypt-config... /usr/local/bin/libgcrypt-config checking for LIBGCRYPT - version >= 1.5.0... yes (1.7.6-beta1) checking LIBGCRYPT API version... okay checking for libassuan-config... /usr/local/bin/libassuan-config checking for LIBASSUAN - version >= 2.0.0... yes (2.4.4-beta1) checking LIBASSUAN API version... okay checking for ksba-config... /usr/local/bin/ksba-config checking for KSBA - version >= 1.0.7... yes (1.3.6-beta2) checking KSBA API version... okay Shalom-Salam, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From wk at gnupg.org Thu Mar 23 17:36:35 2017 From: wk at gnupg.org (Werner Koch) Date: Thu, 23 Mar 2017 17:36:35 +0100 Subject: Enquiry about the GnuPGP In-Reply-To: (Subhash Shrivastava's message of "Wed, 22 Mar 2017 03:41:50 -0800") References: Message-ID: <87y3vwkl0s.fsf@wheatstone.g10code.de> Hi, On Wed, 22 Mar 2017 12:41, shrivastavasubhash5 at gmail.com said: > What is the full form of GnuPG GnuPG stands for GNU Privacy Guard Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From terry.stewart at mrc-bsu.cam.ac.uk Thu Mar 23 18:06:44 2017 From: terry.stewart at mrc-bsu.cam.ac.uk (Terry Stewart) Date: Thu, 23 Mar 2017 17:06:44 +0000 Subject: Compiling GPG on Solaris 10 In-Reply-To: <8737e4lzmx.fsf@wheatstone.g10code.de> References: <480e1184-4ea6-c3a8-705c-d15dadefd338@mrc-bsu.cam.ac.uk> <87poh9ix3v.fsf@wheatstone.g10code.de> <8737e4lzmx.fsf@wheatstone.g10code.de> Message-ID: <825bcc79-533c-9758-c94b-0732e8cc3f61@mrc-bsu.cam.ac.uk> Hi Werner I found the problem, which was an old version of libgcrypt-config in /usr/bin - you were correct, looking in the log file carefully referenced this. I was installing into /usr/local/bin but /usr/bin was before that in my PATH All working and compiled now Regard On 23/03/17 16:35, Werner Koch wrote: > On Wed, 22 Mar 2017 14:32, terry.stewart at mrc-bsu.cam.ac.uk said: > Hi, > > The quoted part of the log is unfortunately not what I am looking for. > Please check the log for lines similar to this: > > configure: checking for libraries > checking for gpg-error-config... /usr/local/bin/gpg-error-config > checking for GPG Error - version >= 1.11... yes (1.27-beta8) > checking for libgcrypt-config... /usr/local/bin/libgcrypt-config > checking for LIBGCRYPT - version >= 1.5.0... yes (1.7.6-beta1) > checking LIBGCRYPT API version... okay > checking for libassuan-config... /usr/local/bin/libassuan-config > checking for LIBASSUAN - version >= 2.0.0... yes (2.4.4-beta1) > checking LIBASSUAN API version... okay > checking for ksba-config... /usr/local/bin/ksba-config > checking for KSBA - version >= 1.0.7... yes (1.3.6-beta2) > checking KSBA API version... okay > > > Shalom-Salam, > > Werner > -- Terry Stewart MRC Biostatistics Unit Cambridge Institute of Public Health Forvie Site Robinson Way Cambridge Biomedical Campus Cambridge CB2 0SR -------------- next part -------------- An HTML attachment was scrubbed... URL: From wk at gnupg.org Thu Mar 23 18:29:31 2017 From: wk at gnupg.org (Werner Koch) Date: Thu, 23 Mar 2017 18:29:31 +0100 Subject: Parallel decrypts fail in 2.1.19 In-Reply-To: (Michael Smith's message of "Wed, 22 Mar 2017 21:32:17 -0400") References: Message-ID: <877f3flx50.fsf@wheatstone.g10code.de> On Thu, 23 Mar 2017 02:32, michaels at syapse.com said: > 2017-03-22 21:25:14 gpg-agent[3624] DBG: rsa_decrypt res: [out of core] > 2017-03-22 21:25:14 gpg-agent[3624] Ohhhh jeeee: ... this is a bug > (sexp.c:1433:do_vsexp_sscan) The bug diagnostic is a side-effect of the out of core error. I'll fix that for libgcrypt 1.8 but it is not a problem. > $ gpg --version > gpg (GnuPG) 2.1.19 > libgcrypt 1.7.6 Libgcrypt has the fix for the secure memory. Thus the above should not happen unless you have set an ulimit. Are you sure that the running gpg-agent is up-to-date? gpg-connect-agent 'getinfo version' /bye shows this. However, gpg did not show a warning so I expect this is all fine. We need to have a test case to replicate and valgrind the problem. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From michaels at syapse.com Thu Mar 23 22:26:52 2017 From: michaels at syapse.com (Michael Smith) Date: Thu, 23 Mar 2017 17:26:52 -0400 Subject: Parallel decrypts fail in 2.1.19 In-Reply-To: <877f3flx50.fsf@wheatstone.g10code.de> References: <877f3flx50.fsf@wheatstone.g10code.de> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 > Libgcrypt has the fix for the secure memory. Thus the above should not > happen unless you have set an ulimit. Are you sure that the running > gpg-agent is up-to-date? > > gpg-connect-agent 'getinfo version' /bye $ gpg-connect-agent 'getinfo version' /bye D 2.1.19 OK I am on a MacBook Pro and haven't changed any defaults related to ulimits, but I'll take a look. > We need to have a test case to replicate and valgrind the problem. How can I help further to create a test case? Thanks, Michael On Thu, Mar 23, 2017 at 1:29 PM, Werner Koch wrote: > On Thu, 23 Mar 2017 02:32, michaels at syapse.com said: > >> 2017-03-22 21:25:14 gpg-agent[3624] DBG: rsa_decrypt res: [out of core] >> 2017-03-22 21:25:14 gpg-agent[3624] Ohhhh jeeee: ... this is a bug >> (sexp.c:1433:do_vsexp_sscan) > > The bug diagnostic is a side-effect of the out of core error. I'll fix > that for libgcrypt 1.8 but it is not a problem. > >> $ gpg --version >> gpg (GnuPG) 2.1.19 >> libgcrypt 1.7.6 > > Libgcrypt has the fix for the secure memory. Thus the above should not > happen unless you have set an ulimit. Are you sure that the running > gpg-agent is up-to-date? > > gpg-connect-agent 'getinfo version' /bye > > shows this. However, gpg did not show a warning so I expect this is > all fine. > > We need to have a test case to replicate and valgrind the problem. > > > Salam-Shalom, > > Werner > > -- > Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEFENfcrF4GOcIc0u0oCVjgPWyEDgFAljUPUcACgkQoCVjgPWy EDgEpA//R6qjcX7cSu9oRgSSGqRsROeNU7qeNie/JC2gKbUG1tXvnpYTjnoKKxXH nElnd0laLTgWFZB4f2a8XtmFA0Ofca/rmmgQ/uVfCAdxcpsmFmRnQMBVnteXIxzy SHhR2+980JU6gSG/gfdJ1ezVYDvU3MlM0MVb/EzMsjeA6MeKCGpg5Anc21ymO4mo iWjp0sBC8f3aOn9zJBSmqmejqPKcyhlYl6khM3w5Q6pYFCF1B2b3VtO2F+qxrSWS cVePVz+HVREkvPeOfi5tbN6ENaWWLQUhm5aGZl/Jsg+GJ6mD1TyOv3ZZSqVvZgjh m11xPAFyHvvphk2ILa1X0TmTnSXUD9JZnX5RhLcUW4x/JICCidghjb+RKXyb7bNK naaGjI47kCqBP38HZZpydOdBlnsQ60M/14/s9QUi2lkrhYtkrSzoB7vKLRoKIMwc KJlzl29TKXbGbH8p3hikpFfJuAggUIZekALTlLcQfAXCBlLxwRf0zKehke8T8xIJ Cc/j7V9parH3x7R4jbkd5uPyoGjpD2ivJJ3pnBTgbaH0CuWbhErDiFN9jIfUaqJc BIC5A3qRDcbVJodzuQE1sVqeAstJaWv0E+FBrTGRrd6b7xppiRK5kpRGEb2VrhD3 I8JaYS1EesqCHLN9rRKWVT1eYJA7Pfg738qAi4KoYdPGxADc4Mw= =kTy8 -----END PGP SIGNATURE----- From szczepan at nitrokey.com Fri Mar 24 12:46:26 2017 From: szczepan at nitrokey.com (Szczepan Zalega | Nitrokey) Date: Fri, 24 Mar 2017 12:46:26 +0100 Subject: Generating RSA-4096 on Nitrokey Pro In-Reply-To: References: Message-ID: <511de379-4ec0-b327-80b0-18889506ea89@nitrokey.com> On 03/20/2017 10:39 AM, Szczepan Zalega | Nitrokey wrote: > I would like to generate RSA-4096 key on Nitrokey Pro v0.7 device. > During the generation error is shown: > ``` > gpg: key generation failed: Card error > Key generation failed: Card error > gpg: error setting forced signature PIN flag: Input/output error > ``` > In scdaemon.log I see that libusb reports time-outs: > ``` > 2017-03-17 20:26:51 scdaemon[16299] DBG: ccid-driver: usb_bulk_read > error: LIBUSB_ERROR_TIMEOUT > 2017-03-17 20:26:51 scdaemon[16299] ccid_transceive failed: (0x1000a) > 2017-03-17 20:26:51 scdaemon[16299] apdu_send_simple(0) failed: card I/O > error > ``` > Same is occurring on latest GPG 2.1.19. Attached logs taken under Arch Linux. Any ideas how to fix it? -- Best regards, Szczepan -------------- next part -------------- A non-text attachment was scrubbed... Name: scdaemon-pro-4096-2.1.19-arch-linux.log.txt.gz Type: application/gzip Size: 6178 bytes Desc: not available URL: From gniibe at fsij.org Sat Mar 25 13:01:32 2017 From: gniibe at fsij.org (NIIBE Yutaka) Date: Sat, 25 Mar 2017 21:01:32 +0900 Subject: Generating RSA-4096 on Nitrokey Pro In-Reply-To: <511de379-4ec0-b327-80b0-18889506ea89@nitrokey.com> References: <511de379-4ec0-b327-80b0-18889506ea89@nitrokey.com> Message-ID: <87poh5muoz.fsf@fsij.org> Szczepan Zalega | Nitrokey wrote: > Same is occurring on latest GPG 2.1.19. Attached logs taken under Arch > Linux. Any ideas how to fix it? I have read the log which you attached on Monday. I think that the CCID driver has a bug for TPDU handling for time extension from the card. This problem never occurred when a reader handles a time extension from card and changes into the request of time extension from the reader. I'll check how it works with my reader and OpenPGP card 2.1. I will fix the CCID driver. Nitrokey Pro also can handle the card's request of time extension to chang it to reader's request. Anyhow, scdaemon of GnuPG should be fixed. -- From ssmeenk at freshdot.net Sat Mar 25 15:40:23 2017 From: ssmeenk at freshdot.net (Sander Smeenk) Date: Sat, 25 Mar 2017 15:40:23 +0100 Subject: GnuPGv2 & 'pinentry' on Linux w/ remote access In-Reply-To: <7d2e0dfc-6633-f0b1-62ec-44c6a0944402@digitalbrains.com> References: <20170322144632.GA17716@dot.dmz.freshdot.net> <7d2e0dfc-6633-f0b1-62ec-44c6a0944402@digitalbrains.com> Message-ID: <20170325144023.GC17716@dot.dmz.freshdot.net> Quoting Peter Lebbing (peter at digitalbrains.com): > > I'm trying to make the big step from GnuPG v1 to v2 but i'm experiencing > > agonizing pains caused by the forced use of "pinentry" by gpg-agent and > > friends, or rather the way the GPG_TTY stuff works? > The first thing we really need to know before we can give good help, is: > which version of GnuPG are you using? Heh. D'oh! This is Ubuntu 16.10's gpg 2.1.15 w/ libgcrypt 1.7.2-beta. When not starting gpg-agent from .xsession and thus not using it for ssh-agent emulation, it seems a bit more well-behaved. I have yet to run into pinentry trouble, but it is not that often that i use gpg. Thanks! -Sndr. -- | Giraffiti: Vandalism spray-painted very, very high. | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From gniibe at fsij.org Mon Mar 27 04:40:30 2017 From: gniibe at fsij.org (NIIBE Yutaka) Date: Mon, 27 Mar 2017 11:40:30 +0900 Subject: Generating RSA-4096 on Nitrokey Pro In-Reply-To: <87poh5muoz.fsf@fsij.org> References: <511de379-4ec0-b327-80b0-18889506ea89@nitrokey.com> <87poh5muoz.fsf@fsij.org> Message-ID: <87y3vr1ly9.fsf@iwagami.gniibe.org> NIIBE Yutaka wrote: > I think that the CCID driver has a bug for TPDU handling for time > extension from the card. I confirmed that the problem can be reproducible with Gemelto card reader (TPDU exchange). The problem is that OpenPGP card (2.0 or 2.1) needs time out detection of 43 seconds or so, and its BWI request value is 100 (which is quite unusual). The internal CCID driver doesn't handle block waiting time (BWT) correctly according to the card protocol, but uses fixed timeout value of 13-second. I put a kludge to handle this special case in the internal CCID driver. Fixed in 0848cfcce738150b53bfb65b78efc1e6dc9f3d26. -- From justus at g10code.com Mon Mar 27 13:10:26 2017 From: justus at g10code.com (Justus Winter) Date: Mon, 27 Mar 2017 13:10:26 +0200 Subject: Parallel decrypts fail in 2.1.19 In-Reply-To: References: <877f3flx50.fsf@wheatstone.g10code.de> Message-ID: <87shlzkmal.fsf@europa.jade-hamburg.de> Michael Smith writes: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > >> Libgcrypt has the fix for the secure memory. Thus the above should not >> happen unless you have set an ulimit. Are you sure that the running >> gpg-agent is up-to-date? >> >> gpg-connect-agent 'getinfo version' /bye > > $ gpg-connect-agent 'getinfo version' /bye > D 2.1.19 > OK > > I am on a MacBook Pro and haven't changed any defaults related to > ulimits, but I'll take a look. > >> We need to have a test case to replicate and valgrind the problem. > > How can I help further to create a test case? Can you please check which version of libgcrypt the agent is linked to? E.g. by using 'otool': $ otool -L repos/gnupg/obj/agent/gpg-agent repos/gnupg/obj/agent/gpg-agent: /Users/justus/local/lib/libgcrypt.20.dylib (compatibility version 22.0.0, current version 22.3.0) /Users/justus/local/lib/libgpg-error.0.dylib (compatibility version 21.0.0, current version 21.0.0) /Users/justus/local/lib/libassuan.0.dylib (compatibility version 8.0.0, current version 8.3.0) /Users/justus/pkg/lib/libnpth.0.dylib (compatibility version 1.0.0, current version 1.5.0) /Users/justus/pkg/lib/libiconv.2.dylib (compatibility version 8.0.0, current version 8.1.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1238.0.0) Are you building GnuPG yourself? Justus -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 487 bytes Desc: not available URL: From michaels at syapse.com Mon Mar 27 15:02:45 2017 From: michaels at syapse.com (Michael Smith) Date: Mon, 27 Mar 2017 09:02:45 -0400 Subject: Parallel decrypts fail in 2.1.19 In-Reply-To: <87shlzkmal.fsf@europa.jade-hamburg.de> References: <877f3flx50.fsf@wheatstone.g10code.de> <87shlzkmal.fsf@europa.jade-hamburg.de> Message-ID: -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 > Can you please check which version of libgcrypt the agent is linked to? $ otool -L $(type -P gpg-agent) /usr/local/bin/gpg-agent: /usr/local/opt/libgcrypt/lib/libgcrypt.20.dylib (compatibility version 22.0.0, current version 22.6.0) /usr/local/opt/libgpg-error/lib/libgpg-error.0.dylib (compatibility version 23.0.0, current version 23.0.0) /usr/local/opt/libassuan/lib/libassuan.0.dylib (compatibility version 8.0.0, current version 8.3.0) /usr/local/opt/npth/lib/libnpth.0.dylib (compatibility version 1.0.0, current version 1.5.0) /usr/local/opt/gettext/lib/libintl.8.dylib (compatibility version 10.0.0, current version 10.5.0) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 1348.28.0) /usr/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1238.0.0) > Are you building GnuPG yourself? I first encountered the problem with the Homebrew binpkg. I also rebuilt libgcrypt and gnupg using brew install --build-from-source. The behavior has been consistent. On Mon, Mar 27, 2017 at 7:10 AM Justus Winter wrote: > > Michael Smith writes: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA512 > > > >> Libgcrypt has the fix for the secure memory. Thus the above should not > >> happen unless you have set an ulimit. Are you sure that the running > >> gpg-agent is up-to-date? > >> > >> gpg-connect-agent 'getinfo version' /bye > > > > $ gpg-connect-agent 'getinfo version' /bye > > D 2.1.19 > > OK > > > > I am on a MacBook Pro and haven't changed any defaults related to > > ulimits, but I'll take a look. > > > >> We need to have a test case to replicate and valgrind the problem. > > > > How can I help further to create a test case? > > Can you please check which version of libgcrypt the agent is linked to? > E.g. by using 'otool': > > $ otool -L repos/gnupg/obj/agent/gpg-agent > repos/gnupg/obj/agent/gpg-agent: > /Users/justus/local/lib/libgcrypt.20.dylib (compatibility version 22.0.0, current version 22.3.0) > /Users/justus/local/lib/libgpg-error.0.dylib (compatibility version 21.0.0, current version 21.0.0) > /Users/justus/local/lib/libassuan.0.dylib (compatibility version 8.0.0, current version 8.3.0) > /Users/justus/pkg/lib/libnpth.0.dylib (compatibility version 1.0.0, current version 1.5.0) > /Users/justus/pkg/lib/libiconv.2.dylib (compatibility version 8.0.0, current version 8.1.0) > /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1238.0.0) > > Are you building GnuPG yourself? > > Justus -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEFENfcrF4GOcIc0u0oCVjgPWyEDgFAljZDWMACgkQoCVjgPWy EDh3yA/+IPvavITIZUkQ1nYEUTy7FcaCgD7AhOavj38iLE7anqr83I0PhbO1roCt nCbyMnQGhqXqRGPm3lyHbi3qCOgDS4OfMQfzeMXMH51HIs0uQVPlOj2BQ3bS5qrw 8IXOAlTA8ZnsB7HrM+bSMKm3/o8dqo24tU2YJAJHu4sDczmNb7wIZ7Yh4TnrJjMe PMYiDHytlAjVvbuVsH+P1pmxLUnN6h7Udnsp8Gkq1KLu9e7Xqlit0fOGo3+yTRIK sc7GXCfEt3OFdkFI5R6xt+++qFuMgGrupTV54MAEL+lNBr1UFrdUBWmANz91lP83 LHYRE0nHuextdnI0fD2dy4+S+ToaFSG2elom/CwonfFRds5FI9aExDGUE0MfzmJ6 AFcgduHRtn6UVfbVKKki2MIDEaVlweL33kaUaPACo5RIFt3vo7MnFCuMhe01/Oci aApWrikrWIrBfU6GqUCvKxmRkdhWZxFLXxzzHtZ6D9LdvQD3+1fhtEgKwD0waNQm 7Pc3vxdektXbq6xtwK2N/ScvpRFhu57hMuO3GDPyi5NPnGapLC+eshPA2B+C2X22 qHWnilXuS0rp3nUdzB/2RgT20wvF8WDe8Edt3RQmh1CKmofeFCM32Kr0cFOPkl+R wL8w5hCFaqu5fA9aKOukenAWYpvlBcig7UJU2woyfeN+10gGHnU= =Z0rQ -----END PGP SIGNATURE----- From post at jankoppe.de Mon Mar 27 13:55:53 2017 From: post at jankoppe.de (Jan Koppe) Date: Mon, 27 Mar 2017 13:55:53 +0200 Subject: Parallel decrypts fail in 2.1.19 Message-ID: <622a9889-e46a-4eb7-988c-5a29d63718de@jankoppe.de> Hello, I hope this message will be attached to the right thread. If not, please excuse me. Also: Hi, I'm new to the list, and pretty new to GnuPG in general! I've stumbled upon this error as well - decrypting in parallel fails for me, with the same error messages. I'm using the packages as provided by my distribution (Arch Linux), no modifications at all. Output of the suggested commands: $ LANG=C gpg2 --version gpg (GnuPG) 2.1.19 libgcrypt 1.7.6 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Home: /home/jan/.gnupg Supported algorithms: Pubkey: RSA, ELG, DSA, ECDH, ECDSA, EDDSA Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH, CAMELLIA128, CAMELLIA192, CAMELLIA256 Hash: SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224 Compression: Uncompressed, ZIP, ZLIB, BZIP2 $ gpg-connect-agent 'getinfo version' /bye D 2.1.19 OK $ ldd -r -v $(which gpg) linux-vdso.so.1 (0x00007fffea28d000) libz.so.1 => /usr/lib/libz.so.1 (0x00007f8e87620000) libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x00007f8e87410000) libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0x00007f8e870fd000) libgcrypt.so.20 => /usr/lib/libgcrypt.so.20 (0x00007f8e86dee000) libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0x00007f8e86bd9000) libreadline.so.7 => /usr/lib/libreadline.so.7 (0x00007f8e8698b000) libassuan.so.0 => /usr/lib/libassuan.so.0 (0x00007f8e86778000) libc.so.6 => /usr/lib/libc.so.6 (0x00007f8e863d4000) libm.so.6 => /usr/lib/libm.so.6 (0x00007f8e860c1000) libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f8e85ebd000) libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f8e85c9f000) libncursesw.so.6 => /usr/lib/libncursesw.so.6 (0x00007f8e85a33000) /lib64/ld-linux-x86-64.so.2 (0x00007f8e87837000) Version information: /usr/bin/gpg: libassuan.so.0 (LIBASSUAN_1.0) => /usr/lib/libassuan.so.0 libgpg-error.so.0 (GPG_ERROR_1.0) => /usr/lib/libgpg-error.so.0 libc.so.6 (GLIBC_2.14) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.3.3) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.7) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.4) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.3) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.3.4) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.2.5) => /usr/lib/libc.so.6 libgcrypt.so.20 (GCRYPT_1.6) => /usr/lib/libgcrypt.so.20 /usr/lib/libz.so.1: libc.so.6 (GLIBC_2.14) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.4) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.2.5) => /usr/lib/libc.so.6 /usr/lib/libbz2.so.1.0: libc.so.6 (GLIBC_2.3) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.4) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.2.5) => /usr/lib/libc.so.6 /usr/lib/libsqlite3.so.0: libdl.so.2 (GLIBC_2.2.5) => /usr/lib/libdl.so.2 libm.so.6 (GLIBC_2.2.5) => /usr/lib/libm.so.6 libpthread.so.0 (GLIBC_2.2.5) => /usr/lib/libpthread.so.0 libc.so.6 (GLIBC_2.3) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.14) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.3.4) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.4) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.2.5) => /usr/lib/libc.so.6 /usr/lib/libgcrypt.so.20: libgpg-error.so.0 (GPG_ERROR_1.0) => /usr/lib/libgpg-error.so.0 libc.so.6 (GLIBC_2.3) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.14) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.15) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.4) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.3.4) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.2.5) => /usr/lib/libc.so.6 /usr/lib/libgpg-error.so.0: libc.so.6 (GLIBC_2.14) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.15) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.4) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.3.4) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.2.5) => /usr/lib/libc.so.6 /usr/lib/libreadline.so.7: libc.so.6 (GLIBC_2.11) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.14) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.15) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.4) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.3.4) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.2.5) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.3) => /usr/lib/libc.so.6 /usr/lib/libassuan.so.0: libgpg-error.so.0 (GPG_ERROR_1.0) => /usr/lib/libgpg-error.so.0 libc.so.6 (GLIBC_2.3) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.14) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.4) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.3.4) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.2.5) => /usr/lib/libc.so.6 /usr/lib/libc.so.6: ld-linux-x86-64.so.2 (GLIBC_2.3) => /lib64/ld-linux-x86-64.so.2 ld-linux-x86-64.so.2 (GLIBC_PRIVATE) => /lib64/ld-linux-x86-64.so.2 /usr/lib/libm.so.6: ld-linux-x86-64.so.2 (GLIBC_PRIVATE) => /lib64/ld-linux-x86-64.so.2 libc.so.6 (GLIBC_2.4) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.2.5) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_PRIVATE) => /usr/lib/libc.so.6 /usr/lib/libdl.so.2: ld-linux-x86-64.so.2 (GLIBC_PRIVATE) => /lib64/ld-linux-x86-64.so.2 libc.so.6 (GLIBC_PRIVATE) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.4) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.2.5) => /usr/lib/libc.so.6 /usr/lib/libpthread.so.0: ld-linux-x86-64.so.2 (GLIBC_2.2.5) => /lib64/ld-linux-x86-64.so.2 ld-linux-x86-64.so.2 (GLIBC_PRIVATE) => /lib64/ld-linux-x86-64.so.2 libc.so.6 (GLIBC_2.14) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.3.2) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.4) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.2.5) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_PRIVATE) => /usr/lib/libc.so.6 /usr/lib/libncursesw.so.6: libc.so.6 (GLIBC_2.3) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.14) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.16) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.4) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.3.4) => /usr/lib/libc.so.6 libc.so.6 (GLIBC_2.2.5) => /usr/lib/libc.so.6 Any help is greatly appreciated. If I can provide some more output or run further tests let me know. Regards, Jan -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From adam at sherman.ca Mon Mar 27 17:37:08 2017 From: adam at sherman.ca (Adam Sherman) Date: Mon, 27 Mar 2017 11:37:08 -0400 Subject: Homedir & scdaemon Message-ID: <480fb5c0-309e-ad5b-77c8-2b3365477da7@sherman.ca> Hello, I would like to be able to do the occasional operation from an alternate home directory. And I'm using a SmartCard. So, gpg2 itself has the --homedir option, which works. But you need to kill existing agents before hand, or things get confusing. But, scdaemon seems more stubborn, and doesn't respect gpg2's homedir option. And trying to start it manually, beforehand, with the --homedir option, fails with: $ /usr/lib/gnupg2/scdaemon -v --homedir /media/asherman/TailsData/gnupg/ scdaemon[5944]: invalid option "--homedir" Any tips? Or is there a much better way to keep some of my secret keys offline? A. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: From gniibe at fsij.org Tue Mar 28 01:24:23 2017 From: gniibe at fsij.org (NIIBE Yutaka) Date: Tue, 28 Mar 2017 08:24:23 +0900 Subject: Homedir & scdaemon In-Reply-To: <480fb5c0-309e-ad5b-77c8-2b3365477da7@sherman.ca> References: <480fb5c0-309e-ad5b-77c8-2b3365477da7@sherman.ca> Message-ID: <87wpbab8wo.fsf@fsij.org> Adam Sherman wrote: > But, scdaemon seems more stubborn, and doesn't respect gpg2's homedir > option. And trying to start it manually, beforehand, with the --homedir > option, fails with: For your information, this is fixed in 2.1. If you will have a chance, please try version 2.1. -- From wk at gnupg.org Tue Mar 28 08:13:05 2017 From: wk at gnupg.org (Werner Koch) Date: Tue, 28 Mar 2017 08:13:05 +0200 Subject: Parallel decrypts fail in 2.1.19 In-Reply-To: <622a9889-e46a-4eb7-988c-5a29d63718de@jankoppe.de> (Jan Koppe's message of "Mon, 27 Mar 2017 13:55:53 +0200") References: <622a9889-e46a-4eb7-988c-5a29d63718de@jankoppe.de> Message-ID: <87mvc67wum.fsf@wheatstone.g10code.de> On Mon, 27 Mar 2017 13:55, post at jankoppe.de said: > $ LANG=C gpg2 --version > gpg (GnuPG) 2.1.19 > libgcrypt 1.7.6 Can you please run a gpg-agent --version too. That is just in case the agent is using a different Libgcrypt. I guess we should also add an Assuan getinfo option to show the library version of the running agent. Salam-Shalom, Werner -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 227 bytes Desc: not available URL: From post at jankoppe.de Tue Mar 28 09:04:06 2017 From: post at jankoppe.de (Jan Koppe) Date: Tue, 28 Mar 2017 09:04:06 +0200 Subject: Parallel decrypts fail in 2.1.19 In-Reply-To: <87mvc67wum.fsf@wheatstone.g10code.de> References: <622a9889-e46a-4eb7-988c-5a29d63718de@jankoppe.de> <87mvc67wum.fsf@wheatstone.g10code.de> Message-ID: <68677ade-8f0b-8fa9-99e3-8ea4545c46dc@jankoppe.de> On 28.03.2017 08:13, Werner Koch wrote: > > Can you please run a > > gpg-agent --version > > too. That is just in case the agent is using a different Libgcrypt. $ gpg-agent --version gpg-agent (GnuPG) 2.1.19 libgcrypt 1.7.6 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Regards, Jan -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From szczepan at nitrokey.com Tue Mar 28 09:07:16 2017 From: szczepan at nitrokey.com (Szczepan Zalega | Nitrokey) Date: Tue, 28 Mar 2017 09:07:16 +0200 Subject: Generating RSA-4096 on Nitrokey Pro In-Reply-To: <87y3vr1ly9.fsf@iwagami.gniibe.org> References: <511de379-4ec0-b327-80b0-18889506ea89@nitrokey.com> <87poh5muoz.fsf@fsij.org> <87y3vr1ly9.fsf@iwagami.gniibe.org> Message-ID: On 03/27/2017 04:40 AM, NIIBE Yutaka wrote: > NIIBE Yutaka wrote: >> I think that the CCID driver has a bug for TPDU handling for time >> extension from the card. > > I confirmed that the problem can be reproducible with Gemelto card > reader (TPDU exchange). > (...) > > I put a kludge to handle this special case in the internal CCID driver. > > Fixed in 0848cfcce738150b53bfb65b78efc1e6dc9f3d26. > Hi! Thank you for the patch! I will check it on next occasion and leave feedback. -- Best regards, Szczepan From adam at sherman.ca Tue Mar 28 16:25:36 2017 From: adam at sherman.ca (Adam Sherman) Date: Tue, 28 Mar 2017 10:25:36 -0400 Subject: Homedir & scdaemon In-Reply-To: <87wpbab8wo.fsf@fsij.org> References: <480fb5c0-309e-ad5b-77c8-2b3365477da7@sherman.ca> <87wpbab8wo.fsf@fsij.org> Message-ID: On 2017-03-27 07:24 PM, NIIBE Yutaka wrote: > Adam Sherman wrote: >> But, scdaemon seems more stubborn, and doesn't respect gpg2's homedir >> option. And trying to start it manually, beforehand, with the --homedir >> option, fails with: > For your information, this is fixed in 2.1. If you will have a chance, > please try version 2.1. That does not appear to be the case: scdaemon (GnuPG) 2.1.11 libgcrypt 1.6.5 libksba 1.3.3-unknown Thanks, A. -- Adam Sherman From gpg at mdsresource.net Tue Mar 28 15:22:39 2017 From: gpg at mdsresource.net (helices) Date: Tue, 28 Mar 2017 08:22:39 -0500 Subject: With which key did I sign my encrypted file? Message-ID: My company uses several keys for signing files encrypted with one of many recipient public keys. Once in awhile, we get pushback from a recipient that they cannot decrypt our file, and sometimes they claim it is because the encrypted file is signed. Yesterday, I took the same file, encrypted it and signed it, as well as encrypting it without signing it. $ /usr/bin/gpg --verify signed.pgp gpg: verify signatures failed: Unexpected error $ /usr/bin/gpg --verify NO-sign.pgp gpg: verify signatures failed: Unexpected error $ /usr/bin/gpg --version gpg (GnuPG) 2.0.14 What am I missing? Please, advise. Thank you. ~ helices -------------- next part -------------- An HTML attachment was scrubbed... URL: From mike at mdsresource.net Tue Mar 28 16:22:10 2017 From: mike at mdsresource.net (Mike Schleif) Date: Tue, 28 Mar 2017 09:22:10 -0500 Subject: With which key did I sign my encrypted file? Message-ID: My company uses several keys for signing files encrypted with one of many recipient public keys. Once in awhile, we get pushback from a recipient that they cannot decrypt our file, and sometimes they claim it is because the encrypted file is signed. Yesterday, I took the same file, encrypted it and signed it, as well as encrypting it without signing it. $ /usr/bin/gpg --verify signed.pgp gpg: verify signatures failed: Unexpected error $ /usr/bin/gpg --verify NO-sign.pgp gpg: verify signatures failed: Unexpected error $ /usr/bin/gpg --version gpg (GnuPG) 2.0.14 What am I missing? Please, advise. Thank you. ~ helices -------------- next part -------------- An HTML attachment was scrubbed... URL: From wk at gnupg.org Tue Mar 28 17:08:08 2017 From: wk at gnupg.org (Werner Koch) Date: Tue, 28 Mar 2017 17:08:08 +0200 Subject: [Announce] GPGME 1.9.0 released Message-ID: <87inmt782v.fsf@wheatstone.g10code.de> Hello! We are pleased to announce version 1.9.0 of GPGME. GnuPG Made Easy (GPGME) is a C language library that allows to add support for cryptography to a program. It is designed to make access to public key crypto engines like gpg and gpgsm easier for applications. GPGME provides a high-level crypto API for encryption, decryption, signing, signature verification, and key management. GPGME comes with language bindings for Common Lisp, C++, QT, Python 2 and 3. See https://gnupg.org/software/gpgme for more. Noteworthy changes in version 1.9.0 =================================== * Clarified meaning of the 'expire' parameter of gpgme_op_createkey and gpgme_op_createsubkey. New flag to force a key without an expiration date. * New function gpgme_op_keylist_from_data_start to list keys from data objects without importing them. * New function gpgme_op_set_uid_flag to flag a key as primary. * New function gpgme_op_decrypt_ext to run decryption with special flags. This can for example be used to unwrap keys (remove only the encryption layer). * New encryption flags to wrap a key (adding an encryption layer to an OpenPGP message) or to create anonymously encrypted messages. * Support for adduid and revuid operations in the C++ bindings. * Support for smartcard key generation in the C++ bindings. * Several new functions for the Python binding. * Many smaller bug fixes. Download ======== You may download this library and its OpenPGP signature from: ftp://ftp.gnupg.org/gcrypt/gpgme/gpgme-1.9.0.tar.bz2 (1312k) ftp://ftp.gnupg.org/gcrypt/gpgme/gpgme-1.9.0.tar.bz2.sig or https://gnupg.org/ftp/gcrypt/gpgme/gpgme-1.9.0.tar.bz2 (1312k) https://gnupg.org/ftp/gcrypt/gpgme/gpgme-1.9.0.tar.bz2.sig The SHA-1 checksum is 870719cd3d2ef6a7fcb1d6af9ce5446edba7bfc3 gpgme-1.9.0.tar.bz2 but you better check the integrity using the provided signature. See for details. Support ======= Please consult the archive of the gnupg-devel mailing list before reporting a bug . We suggest to send bug reports for a new release to this list in favor of filing a bug at . If you need commercial support check out . Maintenance and development of GnuPG is mostly financed by donations. The GnuPG project employs 4 full-time developers, one part-timer, and one contractor. They all work exclusivly on GnuPG and closely related software like Libgcrypt. Please consider to donate via: https://gnupg.org/donate/ Thanks ====== We have to thank all the people who helped with this release, be it testing, coding, translating, suggesting, auditing, administering the servers, spreading the word, answering questions on the mailing lists, and donating money. Happy hacking, Andre, Justus, Werner p.s. This is an announcement only mailing list. Please send replies only to the gnupg-devel 'at' gnupg.org mailing list. p.p.s List of Release Signing Keys: To guarantee that a downloaded GnuPG version has not been tampered by malicious entities we provide signature files for all tarballs and binary versions. The keys are also signed by the long term keys of their respective owners. Current releases are signed by one or more of these five keys: 2048R/4F25E3B6 2011-01-12 [expires: 2019-12-31] Key fingerprint = D869 2123 C406 5DEA 5E0F 3AB5 249B 39D2 4F25 E3B6 Werner Koch (dist sig) rsa2048/E0856959 2014-10-29 [expires: 2019-12-31] Key fingerprint = 46CC 7308 65BB 5C78 EBAB ADCF 0437 6F3E E085 6959 David Shaw (GnuPG Release Signing Key) rsa2048/33BD3F06 2014-10-29 [expires: 2016-10-28] Key fingerprint = 031E C253 6E58 0D8E A286 A9F2 2071 B08A 33BD 3F06 NIIBE Yutaka (GnuPG Release Key) rsa2048/7EFD60D9 2014-10-19 [expires: 2020-12-31] Key fingerprint = D238 EA65 D64C 67ED 4C30 73F2 8A86 1B1C 7EFD 60D9 Werner Koch (Release Signing Key) rsa3072/4B092E28 2017-03-17 [expires: 2027-03-15] Key fingerprint = 5B80 C575 4298 F0CB 55D8 ED6A BCEF 7E29 4B09 2E28 Andre Heinecke (Release Signing Key) You may retrieve these keys from a keyserver using this command gpg --keyserver hkp://keys.gnupg.net --recv-keys \ 249B39D24F25E3B6 04376F3EE0856959 \ 2071B08A33BD3F06 8A861B1C7EFD60D9 BCEF7E294B092E28 The keys are also available at https://gnupg.org/signature_key.html and in any recently released GnuPG tarball in the file g10/distsigkey.gpg . Note that this mail has been signed by a different key. -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 194 bytes Desc: not available URL: -------------- next part -------------- _______________________________________________ Gnupg-announce mailing list Gnupg-announce at gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-announce From gniibe at fsij.org Wed Mar 29 01:21:59 2017 From: gniibe at fsij.org (NIIBE Yutaka) Date: Wed, 29 Mar 2017 08:21:59 +0900 Subject: Homedir & scdaemon In-Reply-To: References: <480fb5c0-309e-ad5b-77c8-2b3365477da7@sherman.ca> <87wpbab8wo.fsf@fsij.org> Message-ID: <87zig5dm20.fsf@fsij.org> Hello, Sorry, I should have offer more information. Adam Sherman wrote: > That does not appear to be the case: > > scdaemon (GnuPG) 2.1.11 > libgcrypt 1.6.5 > libksba 1.3.3-unknown Umm... it is better to have libgcrypt 1.7 for GnuPG. Specifically, it was fixed by following commits. ----------------------------------------- 8b6c0bae33bdc36892f4595806665ce61f77dfd2 Author: NIIBE Yutaka CommitDate: Fri Sep 2 13:41:19 2016 +0900 agent: invoke scdaemon with --homedir. ----------------------------------------- 4e41745b3ea3bb8ffc50af6bafeb1de9c928812f Author: Werner Koch CommitDate: Fri Jun 17 08:36:07 2016 +0200 scd: Make option --homedir work. ----------------------------------------- I confirmed that --homedir works fine with 2.1.16 and later. -- From rainer at hoerbe.at Wed Mar 29 08:23:32 2017 From: rainer at hoerbe.at (Rainer Hoerbe) Date: Wed, 29 Mar 2017 08:23:32 +0200 Subject: haaveged + gpg --sign fails with "signing failed: Operation cancelled" In-Reply-To: <1ac00ede-138d-770d-408e-42d8a00e8eb8@dougbarton.email> References: <8B14507D-44AE-4725-B766-5D148311D916@hoerbe.at> <1ac00ede-138d-770d-408e-42d8a00e8eb8@dougbarton.email> Message-ID: <3A146DBD-6DBD-4576-898A-2CC06A7F2E41@hoerbe.at> > Am 29.03.2017 um 07:44 schrieb Doug Barton : > > > That's not how you use haveged. It is supposed to start when the system boots, and run in the background, collecting entropy to seed the PRNG. This system is based on a LiveCD starting a Docker container. Therefore there is no init.d, only pcscd and haveged. In my understanding wait time to collect entropy should not be the problem when having a blocking RNG - the process just waits. > > That said, if you are using a card for signing that's way more likely to be involved in the problems you're seeing. Try creating a key on the file system, and test using that first. If that works, then you've narrowed down your problems. I did this before, and it worked. As not using havegd did work for me I have no need to fix this problem. I just would recommend to add a note to gpg that users are warned about the issue, as gpg will not yield a meaningful error message, even with -vvv. Thanks, Rainer > > Doug > > > On 03/22/2017 11:33 PM, Rainer Hoerbe wrote: >> Just for the record: Adding entropy using haveged does not work in my setup - it will cause the signature to fail without useful error message. >> >> My setup is: >> Linux keymgmt 4.9.14-200.fc25.x86_64 #1 SMP Mon Mar 13 19:26:40 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux >> gpg (GnuPG) 2.0.22 >> libgcrypt 1.5.3 >> >> The procedure that repeatedly fails when including haveged: >> sudo /usr/sbin/pcscd >> sudo /usr/sbin/haveged >> gpg2 --import my_pub.gpg >> gpg2 --card-status >> echo -e "trust\n5\ny" > /tmp/gpg_editkey.cmd >> gpg2 --command-file /tmp/gpg_editkey.cmd --edit-key >> gpg2 --sign mydoc.txt >> >> Regards, >> Rainer H?rbe >> Identinetics GmbH >> _______________________________________________ >> Gnupg-users mailing list >> Gnupg-users at gnupg.org >> http://lists.gnupg.org/mailman/listinfo/gnupg-users >> From dougb at dougbarton.email Wed Mar 29 07:44:26 2017 From: dougb at dougbarton.email (Doug Barton) Date: Tue, 28 Mar 2017 22:44:26 -0700 Subject: haaveged + gpg --sign fails with "signing failed: Operation cancelled" In-Reply-To: <8B14507D-44AE-4725-B766-5D148311D916@hoerbe.at> References: <8B14507D-44AE-4725-B766-5D148311D916@hoerbe.at> Message-ID: <1ac00ede-138d-770d-408e-42d8a00e8eb8@dougbarton.email> That's not how you use haveged. It is supposed to start when the system boots, and run in the background, collecting entropy to seed the PRNG. That said, if you are using a card for signing that's way more likely to be involved in the problems you're seeing. Try creating a key on the file system, and test using that first. If that works, then you've narrowed down your problems. Doug On 03/22/2017 11:33 PM, Rainer Hoerbe wrote: > Just for the record: Adding entropy using haveged does not work in my setup - it will cause the signature to fail without useful error message. > > My setup is: > Linux keymgmt 4.9.14-200.fc25.x86_64 #1 SMP Mon Mar 13 19:26:40 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux > gpg (GnuPG) 2.0.22 > libgcrypt 1.5.3 > > The procedure that repeatedly fails when including haveged: > sudo /usr/sbin/pcscd > sudo /usr/sbin/haveged > gpg2 --import my_pub.gpg > gpg2 --card-status > echo -e "trust\n5\ny" > /tmp/gpg_editkey.cmd > gpg2 --command-file /tmp/gpg_editkey.cmd --edit-key > gpg2 --sign mydoc.txt > > Regards, > Rainer H?rbe > Identinetics GmbH > _______________________________________________ > Gnupg-users mailing list > Gnupg-users at gnupg.org > http://lists.gnupg.org/mailman/listinfo/gnupg-users > From peter at digitalbrains.com Wed Mar 29 12:20:02 2017 From: peter at digitalbrains.com (Peter Lebbing) Date: Wed, 29 Mar 2017 12:20:02 +0200 Subject: GnuPGv2 & 'pinentry' on Linux w/ remote access In-Reply-To: <20170325144023.GC17716@dot.dmz.freshdot.net> References: <20170322144632.GA17716@dot.dmz.freshdot.net> <7d2e0dfc-6633-f0b1-62ec-44c6a0944402@digitalbrains.com> <20170325144023.GC17716@dot.dmz.freshdot.net> Message-ID: <25b5d9d9-9abf-bdac-c4e8-7dd7d993d108@digitalbrains.com> Hi! On 22/03/17 15:46, Sander Smeenk via Gnupg-users wrote: > I'm on Linux and i am not using Unity/Gnome/whatever, so i start X by > calling 'startx' and it invokes my .xsession that has ... > > | GPG_TTY=$(tty) > | export GPG_TTY > | eval $(gpg-agent --daemon) This is the style for GnuPG 2.0, not for 2.1. 2.1 uses a standard socket location and the OpenPGP part of the agent will Just Work(tm). You still need something for the SSH part, and for GnuPG v1 if you want to have that use the agent. The following is a variation on the Debian GnuPG v2.1 Xsession script. If you need the agent for GnuPG v1, include the following snippet: ---------------------8<--------------->8--------------------- agent_sock=$(gpgconf --list-dirs agent-socket) export GPG_AGENT_INFO=${agent_sock}:0:1 ---------------------8<--------------->8--------------------- However, note that the way the agent is used is fundamentally different. GnuPG v1 uses it as a passphrase cache and retrieves the password to decrypt the private key in secring.gpg on its own. GnuPG v2.1 delegates all private key operations to the agent entirely, and the agent stores its private keys in private-keys-v1.d. I'd advise against mixing use of GnuPG v1 and v2.1 at all. If you don't want GnuPG v1 with use-agent, just omit the snippet. For SSH, you can use the following snippet: ---------------------8<--------------->8--------------------- if [ -n "$(gpgconf --list-options gpg-agent | \ awk -F: '/^enable-ssh-support:/{ print $10 }')" ]; then export SSH_AUTH_SOCK=$(gpgconf --list-dirs agent-ssh-socket) # Launch the agent if it is not already running gpgconf --launch gpg-agent fi ---------------------8<--------------->8--------------------- Note that the agent survives the user session, so if you logout and log back in, the agent will already be running. gpgconf will not launch it again. And your keys will still be unlocked if the time to live hasn't expired. Finally, there is the TTY issue. gpg will pass the TTY (or DISPLAY) it is running on to the agent, so the pinentry pops up on the TTY/DISPLAY where the invoking gpg was running. Unfortunately, SSH has no facility for that, so the pinentry pops up on the "startup TTY". When I'm using SSH from a terminal running on my graphical X session, it turns out just fine: pinentry-gtk-2 pops up on my X screen. When I'm connecting remotely, it goes wrong. Personally, before I SSH from a remote session[1], I run: gpg-connect-agent updatestartuptty /bye You could put that in a shell script with a shorter name... As long as I don't forget to run the gpg-connect-agent command, it always works fine for me. > ... where ssh-agent used to be, just before starting the window manager. > Then i have this gpg-agent.conf: > > | enable-ssh-support > | pinentry-program /usr/bin/pinentry-curses > | default-cache-ttl 300 > | max-cache-ttl 999999 If you use a graphical pinentry and it needs to pop up on a text terminal instead, it will automatically fall back to the curses based pinentry. So if you want a graphical pinentry, you can use that as well. I don't think a curses pinentry would actually work if some graphical program invoked gpg? Where would it pop up? :-) Furthermore, note that the ttl entries are only for OpenPGP. SSH keys have their own entries, ending in -ssh. > With this config, trying to decrypt a GPG-file, everything stalls > and undescriptive errors appear after staring at a blinking cursor > for quite some time. When using gpg? I only have it with SSH, perhaps you really should switch to a graphical pinentry. I can imagine gpg telling the agent "I'm running on $DISPLAY", and then the pinentry cannot work with that. If gpg is not also telling it on what TTY it is running... > Then, when i then ^C the ssh command that is seemingly hanging because > a pinentry popped up on some other workspace's terminal, the pinentry > program on the unrelated terminal completely messes up said terminal. > > Sometimes resulting in *'s being displayed while typing, or letters > disappearing from the input altogether. In such situations it turns out > pinentry-curses was still running, even though my shell was also > interactive. Yes, this is also what I experience when I forget updatestartuptty and the last updatestartuptty was on a text terminal. I also see some of the letters I'm typing, as they are actually passed to the shell running on the text terminal. I think every other character goes to the terminal, with the messed up pinentry-curses getting half of the keystrokes and the others going to your shell. It's a great way to get half of your password in .bash_history if you just keep on typing. You could at least prevent that last bit by immediately doing: $ unset HISTFILE But it will still end up in swappable memory. So just stop typing your passphrase already! :-) > And i haven't even started looking at "how can u use a gpg-agent that > is already running on a box that i am logging in remotely" yet, sort of > what 'keychain' can do with ssh-agent. This for me is actually the only situation where it goes wrong by default at all. But if you switch between multiple X and/or Linux VT sessions, it'll also happen. I do sometimes have a Linux VT open during an X session, but I never use it for SSH (or GnuPG). I hope this helps you further along. Cheers, Peter. [1] I don't usually nest SSH terminal sessions. However, I /do/ use git remotely every now and then. And git often uses... SSH. So that's still a remote SSH running. -- I use the GNU Privacy Guard (GnuPG) in combination with Enigmail. You can send me encrypted mail if you want some privacy. My key is available at -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: OpenPGP digital signature URL: From gpg at mdsresource.net Wed Mar 29 16:46:28 2017 From: gpg at mdsresource.net (helices) Date: Wed, 29 Mar 2017 09:46:28 -0500 Subject: With which key did I sign my encrypted file? In-Reply-To: References: Message-ID: How can I see if an encrypted file is signed and by whom? Please, advise. Thank you. ~ helices On Tue, Mar 28, 2017 at 8:22 AM, helices wrote: > My company uses several keys for signing files encrypted with one of many > recipient public keys. > > Once in awhile, we get pushback from a recipient that they cannot decrypt > our file, and sometimes they claim it is because the encrypted file is > signed. > > Yesterday, I took the same file, encrypted it and signed it, as well as > encrypting it without signing it. > > $ /usr/bin/gpg --verify signed.pgp > gpg: verify signatures failed: Unexpected error > > $ /usr/bin/gpg --verify NO-sign.pgp > gpg: verify signatures failed: Unexpected error > > $ /usr/bin/gpg --version > gpg (GnuPG) 2.0.14 > > What am I missing? > > Please, advise. Thank you. > > ~ helices > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gpg at mdsresource.net Wed Mar 29 17:55:43 2017 From: gpg at mdsresource.net (helices) Date: Wed, 29 Mar 2017 10:55:43 -0500 Subject: With which key did I sign my encrypted file? In-Reply-To: <073c8a64-f90a-24f9-d115-9f0b00bdf52c@digitalbrains.com> References: <073c8a64-f90a-24f9-d115-9f0b00bdf52c@digitalbrains.com> Message-ID: Peter, Thank you. That suffices. Notice that I did provide --version in my original post. ~ helices On Wed, Mar 29, 2017 at 10:40 AM, Peter Lebbing wrote: > Hello, > > To solve your problem, could you please also post the commands that you > used to create the files? The information you gave is really too little > to go on. And also always include which version of GnuPG you're using > (gpg --version). > > On 28/03/17 15:22, helices wrote: > > Once in awhile, we get pushback from a recipient that they cannot > > decrypt our file, and sometimes they claim it is because the encrypted > > file is signed. > > I do not understand why the file being signed would be a problem. I'd > say it's a good thing it's signed. > > > $ /usr/bin/gpg --verify NO-sign.pgp > > gpg: verify signatures failed: Unexpected error > > That's what I see for a file that isn't signed. I'd say it's expected, > though really terse. You're asking it to verify a signature, but don't > give it a signature. I'd say the file is unexpected rather than the > error! ;-) > > On 29/03/17 16:46, helices wrote: > > How can I see if an encrypted file is signed and by whom? > > If you don't mind decrypted files being saved to disc, either: > > -------------------8<------------->8------------------- > $ gpg enc.txt.gpg > gpg: encrypted with 2048-bit RSA key, ID 73A33BEE, created 2009-11-12 > "Peter Lebbing " > File `enc.txt' exists. Overwrite? (y/N) y > -------------------8<------------->8------------------- > > to invoke the default action on the file, and since this is an > encrypted file that is not signed no signature information is shown. Or > explicitly: > > -------------------8<------------->8------------------- > $ gpg -o /dev/null -d enc.txt.gpg > gpg: encrypted with 2048-bit RSA key, ID 73A33BEE, created 2009-11-12 > "Peter Lebbing " > -------------------8<------------->8------------------- > > Which tells GnuPG to decrypt, but send the result to /dev/null, in > other words, will not create or attempt to overwrite files on disc. > > For an encrypted file with a signature it'll look like this instead: > > -------------------8<------------->8------------------- > $ gpg enc-signed.txt.gpg > gpg: encrypted with 2048-bit RSA key, ID 73A33BEE, created 2009-11-12 > "Peter Lebbing " > File `enc-signed.txt' exists. Overwrite? (y/N) y > gpg: Signature made Wed 29 Mar 2017 17:28:28 CEST using RSA key ID DE6CDCA1 > gpg: Good signature from "Peter Lebbing " > -------------------8<------------->8------------------- > > -------------------8<------------->8------------------- > $ gpg -o /dev/null -d enc-signed.txt.gpg > gpg: encrypted with 2048-bit RSA key, ID 73A33BEE, created 2009-11-12 > "Peter Lebbing " > gpg: Signature made Wed 29 Mar 2017 17:28:28 CEST using RSA key ID DE6CDCA1 > gpg: Good signature from "Peter Lebbing " > -------------------8<------------->8------------------- > > There are commands to really dive into the contents of an OpenPGP file, > but this might overwhelm rather than inform you. > > HTH, > > Peter. > > -- > I use the GNU Privacy Guard (GnuPG) in combination with Enigmail. > You can send me encrypted mail if you want some privacy. > My key is available at > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ssmeenk at freshdot.net Thu Mar 30 22:41:12 2017 From: ssmeenk at freshdot.net (Sander Smeenk) Date: Thu, 30 Mar 2017 22:41:12 +0200 Subject: GnuPGv2 & 'pinentry' on Linux w/ remote access In-Reply-To: <25b5d9d9-9abf-bdac-c4e8-7dd7d993d108@digitalbrains.com> References: <20170322144632.GA17716@dot.dmz.freshdot.net> <7d2e0dfc-6633-f0b1-62ec-44c6a0944402@digitalbrains.com> <20170325144023.GC17716@dot.dmz.freshdot.net> <25b5d9d9-9abf-bdac-c4e8-7dd7d993d108@digitalbrains.com> Message-ID: <20170330204112.GA31565@dot.dmz.freshdot.net> Quoting Peter Lebbing (peter at digitalbrains.com): > > | GPG_TTY=$(tty) > > | export GPG_TTY > > | eval $(gpg-agent --daemon) > This is the style for GnuPG 2.0, not for 2.1. 2.1 uses a standard > socket location and the OpenPGP part of the agent will Just Work(tm). > You still need something for the SSH part, and for GnuPG v1 if you > want to have that use the agent. Thanks for your detailed answer, Peter! Indeed the pain seems to start with 'enable-ssh-support' and actually using that interface. It all seems a bit cumbersome with the updatestartuptty business, broken terminals and other foo. Unfortunately. It would have been nice if this actually worked well. ;-) Currently i *don't* start a "session" gpg-agent on my work station, i leave starting it to whatever needs it and then it keeps on running. This works flawlessly it seems even when connecting remotely through SSH. I only do terminal based GPG interaction... > If you need the agent for GnuPG v1 [ .. ] No, i've committed to 'upgrading' to v2 :-) > Finally, there is the TTY issue. gpg will pass the TTY (or DISPLAY) it > is running on to the agent, so the pinentry pops up on the TTY/DISPLAY > where the invoking gpg was running. Unfortunately, SSH has no facility > for that, so the pinentry pops up on the "startup TTY". When I'm using > SSH from a terminal running on my graphical X session, it turns out > just fine: pinentry-gtk-2 pops up on my X screen. When I'm connecting > remotely, it goes wrong. Now i read this, it makes sense that ssh isn't properly interfacing with gpg-agent to make this operation seamless. Has anyone dared submitting an API-patch to Theo yet? ;-)) > Personally before I SSH from a remote session[1], I run: > gpg-connect-agent updatestartuptty /bye You could put that in a shell > script with a shorter name... As long as I don't forget to run the > gpg-connect-agent command, it always works fine for me. I tried putting that command in my bashrc but that was a bad idea when running with enable-ssh-support. Perhaps one could alias 'ssh' (and friends) to run the updatestartuptty command first... Hm. Smells fish^Whacky. > If you use a graphical pinentry and it needs to pop up on a text > terminal instead, it will automatically fall back to the curses based > pinentry. I'm quite certain all my usage of GPG will be in text terminals, but this is good advise not to mess with that setting and leave it to the defaults. I believe i put that there when i was fighting with the enable-ssh-support TTY-issue. > > With this config, trying to decrypt a GPG-file, everything stalls > > and undescriptive errors appear after staring at a blinking cursor > > for quite some time. > When using gpg? Yes. But perhaps, considering the insights provided by your earlier wisdom, gpg (pinentry) might have misbehaved because of the ssh-agent TTY-issue. Set a broken 'updatestartuptty' and gpg will honour that too? GPG (pinentry) works just fine when not using enable-ssh-support it seems. > > Sometimes resulting in *'s being displayed while typing, or letters > > disappearing from the input altogether. > I think every other character goes to the terminal [ .. ] > It's a great way to get half of your password in .bash_history if you just keep on typing. Hahah. :) -- | 1 1 was a racehorse, 2 2 was 1 2, 1 1 1 1 race 1 day, 2 2 1 1 2 | 4096R/20CC6CD2 - 6D40 1A20 B9AA 87D4 84C7 FBD6 F3A9 9442 20CC 6CD2 -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 819 bytes Desc: not available URL: From gniibe at fsij.org Fri Mar 31 09:21:44 2017 From: gniibe at fsij.org (NIIBE Yutaka) Date: Fri, 31 Mar 2017 16:21:44 +0900 Subject: How U2F works In-Reply-To: <87h937f5zw.fsf@iwagami.gniibe.org> References: <878tortdre.fsf@fsij.org> <2883631.IehI8nyOGf@storm.m.i2n> <87h937f5zw.fsf@iwagami.gniibe.org> Message-ID: <87fuhtud13.fsf@iwagami.gniibe.org> NIIBE Yutaka wrote: > Well, I concluded that it is not worth (for me) to try to integrate U2F > feature into Gnuk. While I am open to discussion, my current position is that it is better for Gnuk not to integrate the U2F feature. I'd rather prefer separate implementation of U2F, if needed, possibly reusing code of Gnuk (crypto, USB, etc.). I mean, by separate device. My reasons are: * The nature of two use case (OpenPGP private key vs. authentication for network service providers) are quite different. Generally, Gnuk users don't want to allow other new additional attack vectors, because of adding "new feature" (and U2F would come with them). OpenPGP private key is so important for Gnuk users. U2F key is just a thing to enter web service which is owned by a device vendor. For me, it is not wise to invite possible attacks just for some usefulness of not-so-important thing. * Resource on physical board is quite limited (20KB RAM and 128KB ROM). For code space, we will need some features of Gnuk if we integrate U2F or other features. * Unfortunately, currently, both of Gnuk and U2F uses same protocol of USB CCID. In a host system, it is the practice of CCID on host side to access the device exclusively to mitigate some attacks (changing while using). For example, GnuPG's scdaemon requires exclusive access to Gnuk Token. I think it is also same or similar to browser access to U2F device. I think that a single CCID device can't serve two different programs on host simultaneously. Well, we can manage and consider possible solutions for the latter two technical problems. The first problem is most important, I suppose. Keep adding things, it will become a system like host system, eventually. The purpose to separate out the management of OpenPGP private key to a dedicated device is: make it simple and easier to achieve better security. --