Skip to main content

Join our cause

The Infoseccynic recently posted on twitter:

passwords are dead.... what's the next good authentication mechanism?

Not sure if he means next best, or the next sequentially, but either way we think the answer is WiKID.  Why do we think it is WiKID and why do we think you and the Infoseccynic should join our cause?  What is our cause? 

First our cause:  Our evil plan is to offer low cost/free GPL & LGPL software and libraries to make two-factor authentication as easy and as simple as static passwords.

Why should you join the WiKID cause?

First, our server and software tokens come in GPL versions and our network client API bundles come in LGPL, so it can be included in commercial software.  One customer/VAR didn't like our use of Java on the token, so they re-wrote it in Python.  They wanted a better command line experience.  We even offer a pay-what-you-want option for home users of our commercial version, if you really got to have an iPhone token.

Second, we have also done a whole lot of documentation on how to add two-factor authentication to various remote access solutions.  Most of these involve the use of standard protocols such as radius, tacacs+ and ldap, so they are applicable to many solutions.

Third, we have continued to add functionality such as support for Google sso/SAML and a free openid service. 

Fourth, WiKID is highly extensible.  Because we use public keys instead of shared secrets, we can do a lot more such as mutual authentication and transaction authentication.  The WiKID software token can be used across multiple WiKID servers without a reduction in security.  That multi-domain capability is like having federation on the token.  Moreover, each user can more than one token without a reduction in security.   So, more than likely WiKID can grow to meet the threats of the future.

Finally, I think we're a pretty decent company. We don't send any unsolicited commercial emails, we sponsor things like SecurityBsidesLV and we give back to the open source community. 

And lastly, a call to arms:

Information Security professionals, what are you doing for authentication?  Are you using f*ck.mysql as your mysql password?  I understand that 'it's only the website' or the one about the cobbler's son.   I know it's hard.  Even when it's quite simple, setting up two-factor authentication is not a revenue generating activity.  But information security specialists should practice what we preach.  If you practice with WiKID, you contribute to solving the problem of static passwords in a real and tangible way.  If you can't contribute code, make suggestions, find bugs, create documentation.  Who knows, the data/face you save may be your own.



Current rating: 1

Recent Posts







RSS / Atom