Add support for '3bdf18ff8191fe1fc30031b8640c01ecc173940180829000b3' token

[jcr-rfa]

Reader name: 9693 miniLector Pocket V2
ATR: 3BDF18FF8191FE1FC30031B8640C01ECC173940180829000B3

{
   "cards": [{
   	"atr": "3BDF18FF8191FE1FC30031B8640C01ECC173940180829000B3",
   	"name": "Token name",
   	"driver": "49026459ADEAA6C9274F7D5C2B7D28DB9B5CD2CD"
   }],
   "drivers": [{
   	"id": "49026459ADEAA6C9274F7D5C2B7D28DB9B5CD2CD",
   	"name": "Driver name",
   	"file": {
   		"windows": "path/to/pkcs11.dll",
   		"osx": "path/to/pkcs11.dylib"
   	}
   }]
}

Smart card ATR parsing 3BDF18FF8191FE1FC30031B8640C01ECC173940180829000B3

[Kharya1337]

Thank you for the bug, if you could provide additional information we would love to try to make this card work without error.

We need to know:

Who makes the card?
What middleware is used with the card?
What is the name and path of the PKCS#11 library in that middleware?

Also we have done some more exploration, it seems that MAYBE this card works with:
/usr/local/lib/libASEP11.dylib

If so adding this one card to cards.json should in theory make this card work.

{
	"cards": [
	  {
		"atr": "3BDF18FF8191FE1FC30031B8640C01ECC173940180829000B3",
		"name": "Central Bank of Costa Rica smartcard",
		"driver": "29a2bd60c4b841c686be68d2874c0c02"
	  }
	]
}

Unfortunately without a user who can work with us to confirm the above we can not add this to the formal definition of supported cards.

[Kharya1337]

Dupe of #3

[jcr-rfa]

Who makes the card? Bit4id What middleware is used with the card? Gaudi (working) Fortify (not working) What is the name and path of the PKCS#11 library in that middleware? Within Gaudi is: ## OASIS PKCS #11 Cryptographic Token Interface v3.0 ### OASIS PKCS #11 Cryptographic Token Interface License <pre> Copyright ¬© OASIS Open 2020. All Rights Reserved.     All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website: [http://www.oasis-open.org/policies-guidelines/ipr]     This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to OASIS, except as needed for the purpose of developing any document or deliverable produced by an OASIS Technical Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must be followed) or as required to translate it into languages other than English.     The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors or assigns.     This document and the information contained herein is provided on an "AS IS" basis and OASIS DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. OASIS AND ITS MEMBERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF ANY USE OF THIS DOCUMENT OR ANY PART THEREOF.     [OASIS requests that any OASIS Party or any other party that believes it has patent claims that would necessarily be infringed by implementations of this OASIS Standards Final Deliverable, to notify OASIS TC Administrator and provide an indication of its willingness to grant patent licenses to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this deliverable.]     [OASIS invites any party to contact the OASIS TC Administrator if it is aware of a claim of ownership of any patent claims that would necessarily be infringed by implementations of this OASIS Standards Final Deliverable by a patent holder that is not willing to provide a license to such patent claims in a manner consistent with the IPR Mode of the OASIS Technical Committee that produced this OASIS Standards Final Deliverable. OASIS may include such claims on its website, but disclaims any obligation to do so.]     [OASIS takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this OASIS Standards Final Deliverable or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on OASIS' procedures with respect to rights in any document or deliverable produced by an OASIS Technical Committee can be found on the OASIS website. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this OASIS Standards Final Deliverable, can be obtained from the OASIS TC Administrator. OASIS makes no representation that any information or list of intellectual property rights will at any time be complete, or that any claims in such list are, in fact, Essential Claims.] </pre> ## IAIK (Institute for Applied Information Processing and Communication) PKCS#11 wrapper files v1 ### IAIK License <pre> Copyright (c) 2002 Graz University of Technology. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this    list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice,    this list of conditions and the following disclaimer in the documentation    and/or other materials provided with the distribution. 3. The end-user documentation included with the redistribution, if any, must    include the following acknowledgment:    "This product includes software developed by IAIK of Graz University of     Technology."    Alternately, this acknowledgment may appear in the software itself, if and    wherever such third-party acknowledgments normally appear. 4. The names "Graz University of Technology" and "IAIK of Graz University of    Technology" must not be used to endorse or promote products derived from this    software without prior written permission. 5. Products derived from this software may not be called "IAIK PKCS Wrapper",    nor may "IAIK" appear in their name, without prior written permission of    Graz University of Technology. THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE LICENSOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. </pre> Ing. Juan Carlos Rodriguez RF Automatizacion S.A. Mob +506 60432999 / +506 83942526 Tel +506 22490910 / +506 22970707 Skype rfautomatizacion / IET-25562 De: Illia Kharlamov ***@***.***> Responder a: PeculiarVentures/fortify-releases ***@***.***> Fecha: lunes, 16 de diciembre de 2024, 4:10 a. m. Para: PeculiarVentures/fortify-releases ***@***.***> CC: Juan Carlos Rodriguez ***@***.***>, Author ***@***.***> Asunto: Re: [PeculiarVentures/fortify-releases] Add support for '3bdf18ff8191fe1fc30031b8640c01ecc173940180829000b3' token (Issue #25) Thank you for the bug, if you could provide additional information we would love to try to make this card work without error. We need to know: Who makes the card? What middleware is used with the card? What is the name and path of the PKCS#11 library in that middleware? Also we have done some more exploration, it seems that MAYBE this card works with: /usr/local/lib/libASEP11.dylib If so adding this one card to cards.json should in theory make this card work. {         "cards": [           {                "atr": "3BDF18FF8191FE1FC30031B8640C01ECC173940180829000B3",                "name": "Central Bank of Costa Rica smartcard",                "driver": "29a2bd60c4b841c686be68d2874c0c02"           }         ] } Unfortunately without a user who can work with us to confirm the above we can not add this to the formal definition of supported cards. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: ***@***.***>