OpenSC · frankmorgner · Aug 12, 2026 · Aug 12, 2026 · Aug 12, 2026
diff --git a/Aladdin-eToken-PRO.md b/Aladdin-eToken-PRO.md
diff --git a/Creating-applications-with-smart-card-support.md b/Creating-applications-with-smart-card-support.md
@@ -41,7 +41,7 @@ Windows applications use CryptoAPI to do native SSL connections and to use the W
 
 ### CDSA/Keychain (Mac OS X)
 
-Mac OS X implements CDSA as the cryptography API for the Mac platform (in theory it is a universal specification but in practice only implemented by Apple). OS X 10.4 and above implement Tokend, what is similar in nature to BaseCSP on Windows - it provides a plugin architecture to add support for smart cards into the system. Applications using CDSA can then transparently make use of smart cards. Applications usually use higher level API-s (like Keychain or SSL socket API-s) that internally make use of CDSA. Trust management is exposed centrally via Keychain.app. Use Keychain API-s if writing a native application for Mac OS X or if you want to have a smooth "Mac style" user experience.
+Mac OS X implements CDSA as the cryptography API for the Mac platform (in theory it is a universal specification but in practice only implemented by Apple). OS X 10.4 until 10.11 and above implement Tokend, what is similar in nature to BaseCSP on Windows - it provides a plugin architecture to add support for smart cards into the system. Applications using CDSA can then transparently make use of smart cards. Applications usually use higher level API-s (like Keychain or SSL socket API-s) that internally make use of CDSA. Trust management is exposed centrally via Keychain.app. Use Keychain API-s if writing a native application for Mac OS X or if you want to have a smooth "Mac style" user experience.
 
 * [Mac Documentation: Security](https://developer.apple.com/documentation/security/)
 

diff --git a/GoID-fingerprint-card.md b/GoID-fingerprint-card.md
@@ -18,7 +18,7 @@ on-card-applications. It is compatible with every contactless smart card reader
 In the default configuration, the GoID card ships with the following on-card-applications:
 
 * [SmartCard-HSM](https://github.com/OpenSC/OpenSC/wiki/SmartCardHSM) as PKI
-  application (available via PKCS#11, Minidriver, Tokend, CKT)
+  application (available via PKCS#11, Minidriver, CTK)
 * [PAccess](https://www.cryptoplexity.informatik.tu-darmstadt.de/media/crypt/publications_1/access_control.pdf)
   for physical access control
 

diff --git a/OpenPGP-card.md b/OpenPGP-card.md
@@ -313,7 +313,6 @@ $ opensc-tool -s 00:20:00:81:08:40:40:40:40:40:40:40:40 \
 ### Mac OS X
 
 * Use <https://gpgtools.org/> to get GnuPG2 for Mac OS X
-* Remove OpenSC.tokend from `/System/Library/Security/tokend` when personalizing your token. `scdaemon` requires exclusive access which can not be shared with OpenSC.tokend, which is started when OpenPGP Card/token is inserted.
 * kill `scdaemon` and re-insert your reader if you still see this:
 
 ```sh

diff --git a/Portuguese-eID.md b/Portuguese-eID.md
@@ -88,4 +88,4 @@ Documentation or sample code contribution is appreciated.
 
 Starting with version 0.12.0, OpenSC supports the Portuguese eID card - both Authentication and Digital Signature keys.
 
-Full Mac OS X support is available through OpenSC.Tokend.
+Full Mac OS X support is available through OpenSCToken.
diff --git a/Quick-Start-with-OpenSC.md b/Quick-Start-with-OpenSC.md
@@ -8,7 +8,7 @@ A word of warning: these experiments can destroy your card (e.g. if we have a bu
 
 ## Install the required middleware
 
-Some older card readers (or standalone USB tokens) use a nonstandard wire format for communicating between the computer and the device. You will need to get the corresponding (often proprietary) software up and running first.  For USB tokens see the respective page on this Wiki (e.g., [[Aladdin eToken PRO]], [SafeNet tokens](SafeNet-cards)).  For card readers, you should get to the point where the LED turns on when you plug it into the USB socket.
+Some older card readers (or standalone USB tokens) use a nonstandard wire format for communicating between the computer and the device. You will need to get the corresponding (often proprietary) software up and running first.  For USB tokens see the respective page on this Wiki (e.g., [SafeNet tokens](SafeNet-cards)).  For card readers, you should get to the point where the LED turns on when you plug it into the USB socket.
 
 ## Install OpenSC
 

diff --git a/SSL-Choices.md b/SSL-Choices.md
@@ -12,9 +12,9 @@ If you plan a windows only application and want to develop with Visual C/C++/C#/
 
 ## Mac OS X
 
-In theory the same situation (use Mac OS X developer tools, use the Apple [CDSA](https://developer.apple.com/library/archive/documentation/Security/Conceptual/cryptoservices/CDSA/CDSA.html)/CSP API).
+In theory the same situation (use Mac OS X developer tools, use Apple [CryptoTokenKit](https://developer.apple.com/documentation/cryptotokenkit)).
 
-In practice there is no bridge between OpenSC and the Apple CDSA/CSP API, so currently you won't be able to use OpenSC. But work is in progress, see [OpenscTokend](OpenSC.tokend).
+In practice, you need install OpenSC from its official installer to correctly register the plugin in the system. For details how this works, see [OpenSCToken](https://github.com/frankmorgner/OpenSCToken).
 
 ## Linux
 

diff --git a/Siemens-CardOS-M4.md b/Siemens-CardOS-M4.md
@@ -6,9 +6,7 @@ There are two versions of CardOS cards. The first old, version 4 works in OpenSC
 
 Siemens CardOS M4 smart card should work fine with OpenSC.
 
-Supported smart cards are the [Aladdin eToken PRO](Aladdin-eToken-PRO) and the [CryptoIdentityItsec Eutron ITSEC-I](Eutron-CryptoIdentity-ITSEC-I-ITSEC-P) USB tokens.
-
-Currently only the [Aladdin eToken PRO](Aladdin-eToken-PRO) is tested often (a usb crypto dongle that contains a card with this operating system). It works fine, so all other smart cards with the same card operating system should work fine, too.
+Supported smart cards are the Aladdin eToken PRO and the [CryptoIdentityItsec Eutron ITSEC-I](Eutron-CryptoIdentity-ITSEC-I-ITSEC-P) USB tokens.
 
 Siemens CardOS M4 does not allow a key to be used for signing and decryption. OpenSC has a workaround for this restriction, you can generate or store a private key with the `--split-key` flag which will store the key twice, with different usage options, but hide this detail.
 

diff --git a/Smart-Card-Release-Testing.md b/Smart-Card-Release-Testing.md
@@ -38,7 +38,7 @@
     * [Windows Login or Unlock](#windows-login-or-unlock)
     * [TLS Client Authentication with Internet Explorer, Edge or Chrome](#tls-client-authentication-with-internet-explorer-edge-or-chrome)
     * [Change PIN](#change-pin)
-  * [macOS Tokend](#macos-tokend)
+  * [macOS CryptoTokenKit](#macos-cryptotokenkit)
     * [Keychain Access](#keychain-access)
     * [TLS Client Authentication with Safari or Chrome](#tls-client-authentication-with-safari-or-chrome)
   * [Detaching and attaching reader with card inserted](#detaching-and-attaching-reader-with-card-inserted)
@@ -1048,7 +1048,7 @@ User is authenticated.
 **Expected Result:**
 PIN is changed.
 
-### macOS Tokend
+### macOS CryptoTokenKit
 
 #### Keychain Access
 

diff --git a/Supported-hardware-(smart-cards-and-USB-tokens).md b/Supported-hardware-(smart-cards-and-USB-tokens).md
@@ -58,7 +58,7 @@ Each entry on this list possibly represents a whole family of tokens. See each p
 
 * [Aktiv Co. Rutoken ECP](Aktiv-Co.-Rutoken-ECP)
 * [Aktiv Co. Rutoken S](Aktiv-Co.-Rutoken-S)
-* [Aladdin Etoken Pro](Aladdin-eToken-PRO)
+* Aladdin Etoken Pro
 * [Athena ASEPCOS / ASEKey](Athena-ASEPCOS-ASEKey)
 * [CardContact SmartCardHsm](SmartCardHSM)
 * [Crypto Stick](OpenPGP-card)
Original file line number	Diff line number	Diff line change
Expand Up		@@ -88,4 +88,4 @@ Documentation or sample code contribution is appreciated.

		Starting with version 0.12.0, OpenSC supports the Portuguese eID card - both Authentication and Digital Signature keys.

		Full Mac OS X support is available through OpenSC.Tokend.
		Full Mac OS X support is available through OpenSCToken.