Skip to main content

The WiKID Blog

Viewing posts tagged WiKID

new-software-token-release-fixes-compilation-error

We've released version 3.0.9 of the J2SE software token. If you downloaded 3.0.8 and found it didn't work it was because it was accidentally compiled with Java 6. If you were running Java 6, you didn't notice.

new-software-tokens-for-windows-smartphone-and

Just a quick announcement about our new software token clients for Windows Smartphone and Windows Mobile 6 Professional. Please give them a test!

new-wikid-pricing

We have recently posted new pricing on the Website. We have lowered the server price to $0 from $1,500. We were getting feedback from some prospects that our prices were too high for smaller companies that might be required to do Visa/Mastercard PCI compliance or HIPAA, etc.

on-the-security-of-software-tokens-for-two-factor

Securology has a post about RSA's software tokens. In it, two key issues with are raised, one is specific to tokens that use symmetric encryption such as the RSA software tokens:

Distributing the seed record requires a confidential channel to ensure that it is not perfectly duplicated in transit. Distributing seed records to many of the supported platforms of soft token vendors involves plaintext transmission, such as sending the seed record as an email attachment to a Blackberry client. An administrator may provision the seed record encrypted using an initial passphrase that is distributed out-of-band, but it is common practice for seed records and initial passphrases to be distributed side-by-side. Whereas a physical token can only be in one place at a time, a soft token could be perfectly duplicated by an eavesdropper, even complete with its initial passphrase (especially when it isn't distributed out of band). If Alice receives her soft token and changes its passphrase, Eve could keep her perfect copy with the intial passphrase or choose to change the passphrase-- either way, the back end of the one-time-password authentication system will receive a valid token code (time value encrypted with the seed record).
Note that this is not an issue with WiKID's software tokens as we use public key encryption. The private key remains on the device and only the public key is transmitted. It is the out-of-band method of verifying the user's registration code that matters for WiKID. This could be done over the phone or via an application which uses some existing trusted information or credentials. (We protect against a man-in-the-middle attack in this process by hashing the registration code with the WiKID server's public key before presenting it to the user. Thus, if someone is trying to impersonate the server, the registration with the real server will fail.)

open-source-two-factor-authentication-for-google

Gotta love open source. To paraphrase, if the project you are looking for doesn't exist, just wait (or start it yourself). I've been wanting to do a proof-of-concept on adding two-factor authentication to Google Apps for you Domain for a long time. And while we will probably put this functionality into the WiKID server down the road, I wanted something right now :).

Recent Posts

Archive

2018
2017
2016
2015
2014
2013
2012
2011
2010
2009
2008

Categories

Tags

Authors

Feeds

RSS / Atom