samuarl
Other articles referring to this 'cover-up' which do have references, refer to articles saying that there is no emergency at the plant.
Soon the baseless articles will just start referencing one and other and because mainstream news hasn't reported on the baseless allegation it proves to conspiracy nutjobs that the article is correct because there is a media news blackout.
Getting a VPS was my first real foray into Linux and I've learnt so much since I started by just messing around. The Linode library has also been a great source of help.
I recommend anyone who likes to spend hours perfectly configuring services they will likely never use, because it's fun, should get one to hone their terminal chops.
In order to clone a given token you require the token seed, token serial and its current token code[1]. The attacker my have the token seeds and serial numbers from the RSA security hack but not a token code without physical access to the token or a keylogger.
If the attacker could install a keylogger on some employee computer they could perhaps capture a token code and then use that to start emulating say 20,000 tokens with the seed and serial pairs stolen from the database. Next time they capture a code compare it with all the tokens being emulated to see if there is a match, if yes, possible success, you have cloned their token and a keylogger will also capture their pin. If there is no match, move onto next set of seed serial pairs with the code you just captured.
It almost seems like they didn't actually know for definite if the database had been stolen and where unwilling to burden the cost of replacing all the tokens as a precaution. Now with the Lockheed Martin incident they know it was compromised and are forced to.
If I know the song well enough and I am able, playing it out to the end in my head gets rid of it.