Smart Card Middleware, the Big Picture

"Smart Card Middleware" usually means a set of libraries that allows integrating the smart card in third party applications. But the question is which exactly are the libraries supplyed by a smart card middleware? The schema below shows the "Big Picture": [Prosegue]

Smart Card database by ATR

As described in Part 3 of ISO 7816 specifications, the ATR is a sequence of bytes sent by the microchip when replying to a RESET signal. In practical terms, each RESET operation induces on the I/O contact a microchip’s reply constituted by up to 33 characters coding a set of information relating to microchip’s characteristics such as: supported transmission protocols, installed operating system, microchip’s version and manufacturer and so on. [Prosegue]

Web Digital Signature and Authentication using 4Identity

Starting from Chrome 46 and Edge on Windows 10, Java Applets are not more supported. As of this writing, Firefox and Safari still support them but we expect that in a near future they will stop supporting them. For such reason existing solutions for Digital Signature and Authentication based upon Java Applets will not work any more. Bit4id has developed a revolutionary product that empowers web applications with Digital Signature and Authentication processes removing the need of Java Applets or any other third party add-on. 4identity is simple, its is compatible with any web browser and works under the most used operating systems. It gives you the power to develop web signature application and seamlessly deploy to web interfaces. [Prosegue]

Silverlight PKCS#11 with JavaScript Interface

We worked a lot in the past months on NCryptoki, the .NET wrapper to PKCS#11 module and we worked a lot in finding the best way to integrate PKCS#11 tokens in a web page (aspx, php, jsp, etc.). Till now we used a Java based approach using a Java Applet embedded in the web page. Such an applet includes a Java version of NCryptoki (JCryptoki) and a JQuery script that supplies a JavaScript interface to JCryptoki's classes. Such a Java approach works as expected by has some not nice-to-have security issues that: 1) give a bad user experience; 2) are higly dependant on the JRE installed on the client side. So we searched for a better way. We ported the entire NCryptoki package to Silverlight 5 an... [Prosegue]