Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

CryptoCertum 3.6 card support

Aperta
  • Qualcosa non va?
#3,498 12 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 2 giorni

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
c
Ambito
security

Direzione di ricerca

Start by reading card-starcos.c and comparing its existing Starcos 3.5 ATR and eSign AID handling with the ATR and AIDs in this issue. Re-run the reported pkcs15-tool command with the explicit Starcos driver and AID as a baseline. Done means OpenSC recognizes the CryptoCertum 3.6 card and can handle the reported eSign application.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Input needed Wishlist

Hi, I have a CryptoCertum 3.6 card from Certum that doesn't seem to be recognized by OpenSC 0.26.1.

The ATR of the card is 3b 7f 96 00 00 80 31 80 58 43 65 72 74 75 6d 30 31 82 90 00.

The card has two "profiles" in the Certum terminology:

  • The "Secure profile":
    • Pin locked, it requires a PUK provided bu Certum to unlock
    • Apparently preloaded with 5 RSA 3072 and 5 ECC P-384 keys (according to the data displayed by the Certum diagnostic tool)
    • As I understand this profile is expected to handle eIDAS qualified certificates
  • The "Common profile":
    • Not initialized when received, the PIN/PUK can be set freely upon initialization
    • Certificates and privates keys can be imported from a PKCS#12 file. I haven't figured out how to generate a key pair.

The PIN/PUK of the two profiles are independent so I guess each profile is mapped to a different application on the card.

I traced the USB packets with USBPcap and Wireshark when running the Certum diagnostic tool and signing with signtool (using a key loaded on the common profile). This revealed two application AIDs:

  • a0 00 00 01 67 45 53 49 47 4e (eGK-ESIGN)
  • a0 00 00 01 67 45 53 49 47 4f (eSign) -> this one was selected when signing with signtool

I assume it's a Starcos card. OpenSC supports the version 3.5, but card-starcos.c doesn't list the ATR for the 3.6 card and checks a different AID for the eSign application (a0 00 00 02 45 53 69 67 6e).

I ran pkcs15-tool with the driver and AID set explicitely but it didn't work:

$ OPENSC_DRIVER=starcos pkcs15-tool --dump --aid a000000167455349474f
Using reader with a card: ACS ACR40U ICC Reader 0
Connecting to card in reader ACS ACR40U ICC Reader 0...
Failed to connect to card: Card is invalid or cannot be handled

Please let me know if I can provide any relevant information.

Lingua principale
C
Stelle
3.1k
Fork
858
Merge medio
4g 4h
PR unite (30g)
16

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di OpenSC/OpenSC

Tutte le issue di OpenSC/OpenSC

Issue simili

Altre issue su C

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.