The TeleSec cards of German T-Systems are very popular amongst companies requiring mass-/batch signatures or which need the extra portion of security.
Furthermore it is very popular as digital ID card in various German States.
The Netkey 3.0 is the ideal solution for the extra portion of security since it operates only with secure channels to make USB Sniffing impossible. The Netkey 3.0 Card uses 2048 Bit Signatures.
TeleSec smart cards are based on TCOS 2 (1024 Bit) and TCOS 3 (2048 Bit) and offer an excellent signature performance making it the ideal card for high volume signature service provider.
I am using the Netkey 3.0 Card and was wondering that Aloaha asked twice for a PIN the first time I signed with the qualified certificate.
The Telesec Netkey 3.0 Card requires a secure channel to be able to use the qualified signature. The first time a secure channel is being etablished between Aloaha and the Smart Card Aloahas Public Key has to loaded into the card. Saving of Data into the Netkey Card required the Cardholder PIN.
Is it possible to roll out own certificates to the TCOS3 Card?
Yes, from version 3.9.271 the PFX Writer included in Aloaha can roll out certificates directly to the card (except the QES Certificate).
Just right click on the yellow Aloaha System Tray Icon and choose PFX Writer.
Now choose the CA Certificate Template and the Card Reader and press the button with the Aloaha Logo. Aloaha will automatically send the public key of the card to your local Active Directory Domain Controller. The CA will generate the certificate and the PFX Writer will write it to the card.