Skip to main content

The WiKID Blog

Viewing posts tagged Two Factor Authentication

X2Go on Centos

I recently did a tutorial on how to add two-factor authentication to X2Go via pam-radius on Ubuntu.  I've been playing with X2go since then on CentOS. I've released the scripts that I used to create my X2Go virtual boxes on Github. In addition, since packer can output AMIs, we've released a public AMI of the output. It is ami-c854d7a0 (based on a Rightscale image).

Update Bash if you are running OpenVPN

You can see the details about the attack. All of the OpenVPN tutorials we have done use "auth-user-pass-verify" on the client side to get the client to prompt for a username and password.  The exploit can be delivered as part of the username.  And it is before authentication.

More on the security concerns for SSH and Key Management

We've blogged previously about the potential compliance issues around SSH keys and about the risks of poor SSH key management.  A recent Forrester survey (PDF warning!)  revealed:

Are we royally screwing up two-factor authentication

One of our stated goals has always been to help get rid of passwords (alright,  reduce their prevalence).  They aren't secure enough and are a big pain for the end user.  Attempts to make them stronger, such as 60 day expirations and complexity requirements, make them much much worse.  

memeI have watched as a number of attacks have shown the weaknesses and hacks have exposed personal data and yet there was no movement for change until Mat Honan's attack.  Then all of the sudden, OMG, we all need two-factor auth and shame on those services that do not provide it.  Web services started adding two-factor authentication and there's even a web site listing which services do and shaming those that don't offer two-factor. There's a full-on rush to two-factor all the things. 

So what's my problem?  We are *adding* two-factor authentication.  We aren't getting rid of passwords at all.  Users now typically login with their usernames and password and are then prompted to authorize the access (as with Twitter, though I haven't been prompted for that in a long while) or to enter an OTP (as with Amazon's EC2).

Even most corporate sysadmins struggle with this concept. Most assume that you need to perform authorization against AD or LDAP using both the username and static password and that the OTP should be an additional process.  This is not case since Windows Server 2008 and IAS for Windows and never for RADIUS/LDAP.  IAS (now NPS) will do the authorization in AD based on the username alone.  If authorization passes, then the username and OTP are proxied to the authentication server as per the RADIUS standard.  Yet many admins still want both an AD password and OTP. If the OTP encompasses both factors then asking for the AD password is just more of the same factor, more risk that the password will be compromised and more hassle for your users.

In addition to being weak, passwords are huge pain in the ass.  We should be taking advantage of this opportunity to vastly improve authentication and we are not.

Our big list of two-factor authentication tutorials

There's a great new site promoting the use of two-factor authentication by various web services:

Recent Posts







RSS / Atom