cmx(4) [debian man page]

CMX(4)							   BSD Kernel Interfaces Manual 						    CMX(4)

NAME

     cmx -- Omnikey CardMan 4040 smartcard reader device driver

SYNOPSIS

     device cmx

DESCRIPTION

     The cmx driver provides support for the PCCARD based Omnikey CardMan 4040 smartcard reader.  The driver provides a character device special
     file based Chip/Smart Card Interface Devices (CCID) interface.  The driver implements what the vendor calls the Synchronious API onto the
     smartcard reader device.

     Reading and writing is synchronious, meaning that a call to write(2) directly corresponds to a complete CCID command sent to the device,
     while the following read(2) will return the complete answer from the reader.  There is no support for partial reads or writes.  There is no
     upper limit on CCID request or response sizes, but the complete CCID request must be sent to the driver in write(2) and the complete CCID
     response must fit into the buffer supplied to read(2).

     Non-blocking I/O, select(2) and poll(2) are supported and work as expected.  An open file descriptor will always be ready for writing, but
     only ready for reading if the device indicates that it has data available.

COMPATIBILITY

     Userland smartcard code written for the vendor's Linux drivers should work with the cmx driver without modification.

FILES

     /dev/cmxn			 Character device special file.
     /usr/ports/security/openct  OpenCT, a userspace smartcard daemon containing a CCID driver which directly supports cmx devices.

SEE ALSO

     pccard(4)

HISTORY

     The cmx driver first appeared in FreeBSD 7.1.

AUTHORS

     The cmx driver was written by Daniel Roethlisberger <daniel@roe.ch>, originally based on the Linux driver v1.1.0 by Omnikey GmbH
     <www.omnikey.com>.  Early testing and bug fixes by Marcin Cieslak <saper@system.pl>.

BUGS

     The way the cmx driver talks to the CardMan 4040 is a bit rough.  Due to the complete lack of hardware documentation other than vendor driv-
     ers for other operating systems, the gory details of the device's I/O registers are not understood very well.  There may be error conditions
     which can only be solved by physically reinserting the reader.

BSD
								   July 7, 2007 							       BSD

SmartCardServices-legacy(7)			       BSD Miscellaneous Information Manual			       SmartCardServices-legacy(7)

NAME

     SmartCardServices-legacy -- overview of legacy SmartCard support

DESCRIPTION

     SmartCardServices-legacy is a set of components which add native support for SmartCards to OS X based on Tokend modules. Since OS X 10.12,
     there is  SmartCard support which is described in SmartCardServices(7)

     Supported SmartCards appear as separate keychains.  A Tokend module for each SmartCard you wish to use must be installed in
     /Library/Security/tokend

USB SMART CARD READER DRIVERS

     OS X has built-in support for USB CCID class-compliant SmartCard readers.	For other readers, install the reader driver in
     /usr/local/libexec/SmartCardServices/drivers.  Each driver is a bundle.  The bundle contains an XML file Info.plist which contains the
     device's USB vendor ID and product ID.  For detailed description of the plist format and how to write a reader driver, see
     http://pcsclite.alioth.debian.org/api/group__IFDHandler.html

SMART CARD APDU LOGGING

     It is possible to turn on logging for SmartCards by setting the global preference:

     sudo defaults write /Library/Preferences/com.apple.security.smartcard Logging -bool yes

     After a SmartCard reader is connected (or after reboot) all operations including contents of sent and received APDU messages are then logged
     into the system log.  Logging uses the facility com.apple.security.smartcard.log so it is possible to set up filtering of these logs into
     custom targets (see asl.conf(5))

     To avoid security risks that could occur if logging is turned on indefinitely, the logging setting is one-shot - it must be turned on by the
     command above to start logging again with a new reader.  This includes unplugging and replugging the same reader.

DISABLING NEW SMART CARD SUPPORT

     It is possible to turn of the new tokens by setting the global preference:

     sudo defaults write /Library/Preferences/com.apple.security.smartcard DisabledTokens -array com.apple.CryptoTokenKit.pivtoken

DISABLING SHEET AUTHORIZATION IN PREFERENCES

     When using tokend-based SmartCards, according to your configuration you may not be able to use SmartCards for authorization in System Prefer-
     ences sheets. In such case, you can disable sheets using following command:

     defaults write com.apple.Preferences UseSheets -bool FALSE

     System Preferences will then use the original dialog-based authorization.

ENTITLEMENT

     Sandboxed PCSC clients require 'com.apple.security.smartcard=YES' entitlement. Non-sandboxed PCSC clients do not require such entitlement (in
     order to keep backward compatibility with macOS < 10.10).

SEE ALSO

     SmartCardServices(7), sc_auth(8), defaults(1), asl.conf(5), ssh-keychain(8)

Mac OS X							  August 5, 2014							  Mac OS X