Release Date: 2022-03-08
Main new features
DESFire Proximity check
With Card SDK 5.10, we are adding a new feature of the DESFire EV2 portfolio to make usage of DESFire cards in the field even more secure. DESFire EV2 Proximity Check can now be used in order to detect and mitigate relay attacks on the chip, when users present their card in the field.
Card Designer now allows to activate "Kerning" (format 0 subtable) as an additional format option on text fields, if the selected font supports a corresponding kerning table.
Detailed feature list
|JIRA ticket no||Description|
Introducing Proximity check for DESFire EV2
With this release of Card SDK we are introducing the Mifare DESFire EV2 Proximity Check feature, in order to detect and mitigate relay attacks on the chip. Proximity check can be used with software keys only with this release. SAM support is on the roadmap for later releases.
Mifare Classic Emulation on CardOS DI 5.3
Card SDK has been successfully tested for encoding with the Mifare Classic emulation on the CardOS 5.3 Dual Interface cards with the Omnikey 5x22 CL reader family.
Supporting Kerning in Card Layouts
Card Designer now allows to activate "Kerning" (format 0 subtable) as an additional format option, if the selected font supports a corresponding kerning table.
Supporting Mifare SAM AV3 cards
We are now supporting the latest AV3 SAM modules for Mifare DESFire with the same feature set as for AV2.
600 dpi printing with Magicard Prima 8
Card SDK now supports 600 dpi resolution with the Magicard Prima 8 printer. The printer can be used also in combination with inline RFID and crypto chip encoding with the same encoders and chip combinations as for Prima 8, 300 dpi or Prima 4 printers.
See Card SDK requirements and interoperability, section "Card printers without integrated encoding".
Encoding more than 28 DESFire applications
Card SDK had a limit of maximum 28 applications on a DESFire chip (coming from the hardware limitation of DESFire EV1). This limitation has been removed now for DESFire EV2 and EV3. On EV2 and EV3 chips, up to 255 applications (depending on memory consumption of the applications) can be encoded.
Supporting multi-character application names in encodings
In encoding descriptions (DSC files) the most common approach is to define applications with a one-character name (e.g. Application_A). Now multi-character application names (e.g. Application_MY) can be used and referenced as comma-separated fixed value list via "ApplicationList2=MY, XY, NN", or via database field mapping "ApplicationListField2", also with a comma-separated list of the app names.
|JIRA ticket no||Description|
Fixed an issue when saving specific printer settings in Configuration Manager.
Card Designer was not DPI aware when designing layouts. For example, font sizes were not reflected correctly when displayed in the design. This has been fixed now.
Fixed error handling during ID Production service startup when TCP ports are not available.
Changed log level to from INFO to ERROR when logging expired licenses.
Improved log file entries when creating System ID for licensing. More details are provided in the logs for troubleshooting purposes.
Updated openSSL library in order to fix a vulnerability.
For information regarding support, training and other services in your area, please visit our website at www.nexusgroup.com/.
Nexus offers maintenance and support services for Nexus Card SDK to customers and partners. For more information, please refer to the Nexus Technical Support at www.nexusgroup.com/support/, or contact your local sales representative.