Hi CryptoStick/Jan,

Please bear with me, I know very little about PGP but it seems
that the functions you require are supported by most PKI cards
so my question is really: why do you need a patch?

My (not yet activated) plan is emulating a "good card" (which
I don't know yet..), so I don't have to write/support any
middleware at all.

BTW, how are e-mail addresses etc. mapped to PKCS #11?

Regards
Anders

On 2011-12-23 10:22, Crypto Stick wrote:
> Hello developers,
> the German Privacy Foundation is sponsoring to patch OpenSC in order to
> fully support the OpenPGP Card 2 / Crypto Stick. We don't offer a
> fixed-price bounty but ask for bids instead. You are welcome to place
> your bid here:
> https://www.freelancer.com/projects/C-Programming-Computer-Security/patch-OpenSC-support-OpenPGP-Card.html
> 
> Complete Project Description:
> 
> OpenSC [1] is an open source framework which provides a PKCS#15
> interface for smart cards. The OpenPGP Card [2] is an ISO/IEC 7816-4/-8
> compatible smart card that is integrated well with GnuPG. Using this
> smart card, various cryptographic tasks (encryption, decryption, digital
> signing/verification, authentication etc.) can be performed. The smart
> card contains up to three keys (signing, encryption, authentication).
> OpenSC contains basic support for the OpenPGP Card 2.0 [3]. This project
> goal is to patch OpenSC to fully support the OpenPGP Card v2.0. (Note:
> *not* OpenPGP Card v1)
> 
> Required features:
> - Supported key/certificate lengths: 1024, 2048, 3072 and 4096 bit
> - Key/certificate generation on device
> - Import of key/certificate into device
> - Signing (with signature key)
> - Decrypting (with decryption key)
> - Authentication (with auth key)
> - Changing user PIN
> - Changing admin PIN
> - Reading and writing of all available DOs (e.g. card owner name, e-mail
> address)
> 
> Implementation must be compliant to OpenSC's code conventions and
> architecture (no ugly hacks). Implementation must be published/committed
> to get feedback of OpenSC maintainers. OpenSC maintainers' reasonable
> feedback, which otherwise would prevent the patch from being accepted,
> must be fulfilled. Code must be published under the LGPL license version
> 2.1.
> 
> Martin Paljak's OpenSC blob [4] should be taken as a starting point
> because it contains advanced support for OpenPGP Card 2.0 than the main
> OpenSC trunk.
> 
> Required OpenPGP Card (about Euro 20) and smart card adapter or USB
> Crypto Stick (which contains an OpenPGP Card) has to be purchased at own
> cost. See [3] for purchasing details.
> 
> [1] http://www.opensc-project.org/
> [2] http://www.g10code.com/docs/openpgp-card-2.0.1.pdf
> [3] https://www.opensc-project.org/opensc/wiki/OpenPGP
> [4] https://github.com/martinpaljak/OpenSC/blob/openpgp/
> _______________________________________________
> opensc-devel mailing list
> opensc-devel@lists.opensc-project.org
> http://www.opensc-project.org/mailman/listinfo/opensc-devel
> 

_______________________________________________
opensc-devel mailing list
opensc-devel@lists.opensc-project.org
http://www.opensc-project.org/mailman/listinfo/opensc-devel

Reply via email to