Re: ePass2003 status
NdK <[email protected]>
| Newsgroups | gmane.comp.encryption.opensc.devel |
|---|---|
| Message-ID | <[email protected]> |
Il 11/08/2016 14:53, Dirk-Willem van Gulik ha scritto: >> IIRC SO-PIN on the ePass2003 requires secure messaging to be used, but >> SM was not yet present in opensc when the epass2003 driver got added. >> Did that change? From your answer it seems it didn't change. :( > Below script does the trick for me (key generated ‘off line’ — as to circumvent the 512 len limit). No need to do that, unless you need to backup the private key. For me, a plain pkcs15-init -G rsa:2048 --auth-id 1 -l "key label" does the job. Once the keypair is there, associating a certificate is not a problem. BTW, in your script it could be better to use a tmpfs instead of a normal file. But there are other risks anyway, unless you're using it on an offlined single-user machine. > pkcs15-init -E || exit 1 Erase, ok. > pkcs15-init --create-pkcs15 --profile pkcs15+onepin --use-default-transport-key --puk 111111 --label $LABEL --pin 1234 || exit 1 Init with onepin option, so you're not using SOPIN, just the User-PIN. >> PS: pkcs15-init -F always reports "Failed to delete object(s): Not >> supported". Is that normal? Is the card finalized anyway? Is the >> finalize step actually required on ePass2003? In the script you don't finalize the token. For Aventra MyEID the pkcs15-init -F step is needed to activate access control, but ePass2003 seems not to need it. Good to know -- could be useful to have it on the wiki page? And maybe opensc could avoid generating an error? BYtE, Diego ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohodev2dev _______________________________________________ Opensc-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensc-devel