Showing posts with label Passwords. Show all posts
Showing posts with label Passwords. Show all posts

Thursday, April 10, 2014

Heartbleed - Should I change my passwords?

Ok, so most of you should have read by now the headlines about the Heartbleed bug and it's consequences. For those of you who haven't, there is an abundance of resources out there that explain the issue (just google it). The gist of it is that an attacker could leverage the bug and access memory on the server that could contain the SSL certificates private key. Using this, they could create fraudulent certificates, mount a man-in-the-middle attack to get your credentials or, if they have been monitoring traffic between the clients and the server, decrypt the (under TLS) encrypted traffic. Additionally, the issue only exists in OpenSSL implementations that implement the SSL heartbeat feature (which is more or less 17 percent of the worlds web servers).

Ok, so, I've been getting a lot of emails from services informing me they have patched the issue and that I should change my credentials. Is this something you should do for all your online accounts?

Monday, April 7, 2014

User Authentication/Life-Cycle Management Best Practices

The last couple of years, we have witnessed an ever increasing number of pwnage to various sites, leading in compromised user accounts. A lot of these sites do not even have the user credentials hashed (even using the least amount of effort) but rather have the username/password pairs as plaintext. You can go to haveibeenpwned.com for a small list of such compromises. And the ones mentioned are mostly fairly recent to the blogs posting.

This allows malicious users that gain access to this data to possibly use the same credentials on different sites (because nobody reuses passwords, right?).

A greater concern is also the fact that the compromised site/services do not disclose the issue in a timely manner (in a lot of cases they are unaware the compromise happened!!!), so the user is unaware that their credentials have been leaked, allowing them (if we are talking about a slightly above average internet user) to do anything possible to protect themselves. Of course, little can be done if the site/service has very poor security mechanisms (if the user changes their password, the hacker could simply re-dump the password database for example). But, this is a conversation for another time.

What I will be focusing in this blog post is how to correctly manage user accounts in a web application. There is an abundance of frameworks out there that provide all the piping necessary to help a developer correctly set up the whole identity life-cycle. Some have more features than others, but at least they provide a start point for a developer to create more secure code. Why on earth a developer would try to re-invent the wheel is beyond me - after all, one of the basic principles of programming is code re-usability.

The blog post was heavily influenced by daily news, and Episode 1 of the Professionally Evil Perspective podcast which mentions some of the below points I will be making.

For the purposes of the blog post, I have created a Web Site project using Visual Studio 2010, which is available on codeplex.com here. I leverage the ASP.Net Application Services framework for the piping, but the same concepts hold for most of the other authentication and user management frameworks available out there.

Friday, December 28, 2007

Popular Game Machine used for password cracking

As I was looking for some information on the web about MD5, I stumbled across this article from PC World Magazine. The article mentions about the efforts of a senior security consultant at an Auckland based security firm, who managed to dramatically increase the processing capability of cracking passwords by use of a Playstation 3.

By use of the PS3's Cell processor technology, the aforementioned security consultant could crack passwords by a factor of a 100 (and that is not a small factor) faster than Intel based processor architecture, for MD5 hashing (Message-Digest algorithm 5), one of the most widely used cryptographic hashing functions. I will not go through the technical details, however brief they are discussed in the article, but I will try to convey the significance of this effort.

As we all know, technology is progressing at increasingly fast paces. Cryptography (and Information Security in general), are not keeping up with it. Although there are cryptographic algorithms and techniques that provide a level of security that is acceptable (and even unbreakable), these are often computationally heavy on the underlying hardware, thus making both encryption and decryption/verification too heavy for most popular devices (a variety of hand held devices use very simplistic encryption/decryption schemes).

Having a $400 gaming machine, that can be outfitted with Linux in the hands of a capable hacker (which most of them are extremely good programmers), that can be turned into a password cracking machine, personal information is starting to become more and more prone to leaking into the wrong hands. As a student, I was told that certain algorithms where good for encryption, as it was, as stated, "computationally infeasible to generate the passphrase from the encrypted text". As it seams, this is not the case any more.

So, better algorithms are needed, and unfortunately, they are needed right now. The general public does not have the luxury of a million dollar security system, but needs their personal information to remain personal. All that can be said in the end is that nowadays, safely surfing the net and surviving is not just for the technologically literate, but also for the very lucky.