|
|
|
Rainbow iKey technology in Co-Mail
|
An important step has been taken to enhance the protection of encrypted messages in the Co-Mail environment. Following a test period, iKey technology is now available at Co-Mail for authentication purposes. It carries out authentication operations using a token that contains usernames, passwords, private key and other data. This integration combines use of a token with secure application technologies, and makes Co-Mail more convenient and secure for users.
Now with Co-Mail, it’s possible to export the private key used with
Co-Mail, onto the iKey produced and distributed by Rainbow Technologies Inc. Furthermore, users can put in their PIN-code used with iKey, and sign into their secure mailbox at Co-Mail. A virtual keyboard can be activated by double clicking on the password field on the login page, making it possible for any user to perform both operations – exporting Co-Mail’s private key on the token and entering iKey’s PIN to sign-in.
To use iKey, simply plug it into an USB-port. To export the Co-Mail private key onto the iKey token, USB plug-in and virtual keyboard activation is required on the login page. This is done by double clicking on the password field. Then push the button «Export private key to iKey», enter your username, password, PIN of iKey and click Export. To enter your mailbox, activate the virtual keyboard on the login page as described above, enter iKey’s pin in the field «Enter your PIN» and push the «Ok» button.
Co-Mail servers automatically find and retrieve your username, private key and other data needed by PIN-code reception in the authentication process. While processing the data requested and checking the digital signature, the server accepts user authentication. After that, the entire sign-in is completed, simplified by iKey. This innovation provides access to secure email via iKey, resulting in increased email security and trust in the secure services at Co-Mail.
Users need to have a Co-Mail account and Rainbow iKey to carry out this process. This requirement provides integrative protection at both the token and application level.
|
|
