Even though the focus of Aloaha is put on Smart Cards we do have APIs to read 2W, 3W, i2c Memory Cards such as the famous SLE4428, SLE4442, telephone cards, german KVK (Krankenversicherungskarte), Kinko, Student Card, etc.

The API to read such cards is included in the Aloaha Cardconnector, Credential Provider and Smartlogon. No license is required to just read them!

Code Sample:

dim cr
dim reader

set cr = createobject(“AloahaSync.SyncAPI”)
   reader = cr.ReaderNamesCSV
   reader=split(reader,”,”)(0)

   if reader<>”" then
      If cr.Connect(reader) = True Then
         msgbox cr.hexdump(cr.raw_content)
      end if
   end if
set cr = nothing

For german KVK Cards please also try API: cr.KVK_Content

Please note that for the new German Health Card (eGK / Gesundheitskarte) you should follow the instructions on: http://blog.aloaha.com/2012/03/21/deutsche-gesundheitskarte-auslesen/

KVK Specification

Please make sure that when you are using an HID/Omnikey Reader that you install the Sync API additionally to the reader driver. When using SCM Microsystems Reader you need to make sure that the MCARD API has been installed additionally to the reader driver!

Aloaha accesses per default the connected Smart Card Reader via the Windows PC/SC or CCID driver. In some cases it might be required to use the reader via CT-API. For example in cases that no PC/SC or CCID driver exists. That is the case for most health terminals used in the german health system.

To be able to use CT-API it is required that a recent version of the Aloaha Smartcard Connector is installed. If you find the file AloahaCSPPlugin.exe in <common files>\Aloaha your Version is recent enough to be switched to CT-API.

To activate CT-API there have to be entries in the file CTAPIINI.ini in <program files>\wrocklage and entries in the registry.

CTAPIINI.ini:

[Settings]
activated=1
CTAPI=c:\windows\system32\ct8751.dll
[HID OMNIKEY 8751 e-Health LAN]
port=1
Units=01,02,03,04,40,50

Please note the the settings section is required. The rest Aloaha will try to fill in automatically.

Once the above seetings are done you you re-logged on into your machine you will see your CT-API eHealth Terminal in the Aloaha Systray as shown below:

Aloaha System Tray with e-Health Terminal

Even though any CTAPI Reader should work currently ONLY the ORGA 6041 eGK and OMNIKEY 8751 eHealth terminals have been accredited to work perfectly with Aloaha. More will follow on request!

Windows Logon with e-Health Terminal

Obviously the Aloaha Smartlogon does support Windows Logon via CTAPI based Smartcard Reader. That means that it is possible to use a HID 8751 or Orga 6041 eHealth Terminal to logon to with the german HBA (Health Professional Card).

Per default the e-Health Terminal is NOT connected to the Windows Logon Credentials Provider. To activate that you need to create the following entry in our CTAPIini.ini in your installation folder:

[Settings]
CTAPIAsSystem=1

After you create the key and set your credentials via Aloaha GUI you can logon via the Aloaha Tile as shown below:

Aloaha Windows Logon

You can download the Aloaha Middleware/Credential Provider from http://www.aloaha.com/download/credentialprovider.zip

Please make sure to request an evaluation key from info@aloaha.com

German cutomer should also read: http://blog.aloaha.com/2012/01/03/wie-richte-ich-mein-ehealth-terminal-ein-um-mich-mit-meinem-hba-oder-smc-karte-an-windows-anzumelden/

One popular feature is Aloaha’s shell integrated PKCS7 Validator. The user can just right click on the p7s/p7m file and Aloaha will validate the signature and if that is correct will display the signers certificate.

From this Aloaha Signator/Cardconnectors Version on Aloaha will automatically detect if a file is signed only or encrypted and/or signed. Encrypted files will be automatically decrypted! An easy way to test that out is to save the mime.p7m of an s/mime mail as mail.p7m and then right click on it to choose Validate PKCS7!

PKCS7 Validation

The Aloaha Crypto Card is now also available as Contactless Card. Please contact info@aloaha.com for further information.

Details for the Crypto Card can be found on: http://www.aloaha.com/smartcard-software-en/aloaha-crypto-card.php

All Aloaha products are now natively supporting the OpenPGP Cards (v2.0) and GPF Crypto Stick

To use your OpenPGP Card in Windows does not require any non Aloaha Software anymore!

Many thanks to Achim & Jan!

More on http://www.privacyfoundation.de/aktuelles/detail/zurueck/akutelles/artikel/crypto-stick-in-kommerzieller-software-integriert/

Aloaha Limited, a Malta-based provider of content security, PDF and digital signature software, has announced the new generation or version 2.5 of its popular PDF and smart card applications.

The Aloaha PDF Tools such as the Aloaha PDF Suite are now based on a complete new and faster PDF Engine, its own PDF printer, printer port and print processor.

The new PDF engine introduces new embedded commands. Those new commands are now able to customise outgoing e-mails based on commands embedded into the original document.

A small overview of those commands can be seen on http://www.aloaha.com/cache/aloaha-automation-example.pdf

Other major improvements are also experienced with the Aloaha Smart Card Connector. The Aloaha PKCS11 module supports now more APIs to support also very popular applications such as Lotus Notes. A flash video demonstrating how to use Aloaha in Lotus Notes to sign, encrypt and decrypt e-mails can be found on http://www.aloaha.com/movies/notes.htm

Times of Malta: New generation of PDF and smart card applications