This story is more proof that if you want to be secure on the internet you can only aford to use things which where designed with security in mind at the outset.
In this situation the target for the hack are cookies, which are the perfect example. These little packets of data where never designed with security in mind, or at least not the sort of security that is required to stop this sort attack, but they are still used be countless sites for handling automatic logins.
I don't like this idea and if given the choice I will only ever use this option on my machine at home, which is under my control completely (Only I have access to it) and connected via a wired network and even then I don't really feal comfortable using this method unless a secure, https, transaction is used to transmit the data.
Okay so maybe I'm paranoid about security (I do after all work in computer security) but I think that being paranoid on the internet is the only safe way to be!
Another example of this sort of thing (and it's my pet example, so I've covered this before) is the way javascript has grown to the way it is today. It was never designed to do what it's doing now days and while I think it is very cool, I do worry that the security model was never designed to handle todays threats. On the other hand, Java's security model was designed to handle with a lot what javascript is now capable of. I just worry that the next big threat on the net is going to come from technologies that have evolved much faster than there security features. You could however say that this is always the case and that no matter how much testing you do there are always lots very smart people out there with far to much spare time that they like to use breaking things!
I'm not saying that this is a bad thing, as a lot of so called 'white hat' hackers find these security problems before the bad guys, the back hat hackers.