888888
By glazou on Monday 15 November 2004, 16:02 - AOHell - Permalink
So AOL is about to extend its offer with a securID-based access for anyone. Just in case you are interested, you have to know those securIDs die from time to time from the 888888 disease: the display starts blinking and shows only 888888. The battery is not the problem. The only thing that can help you in that case is a new securID. Of course, you don't need just the securID itself: you also need an administrator to bind your securID to your AOL account. During my last year at AOL, it happened to me twice. Of course, as an AOL/Netscape employee having the Internal Computing guys on the same floor, that was easy to fix. I wonder how long it's going to take for customers of this PassCode Premium Service... Ah, let's just hope this six-digits securID is more reliable than the ten-digits employees have.
Comments
Le premier lien est une invitation à écrire sur ton blog ?
my favorite is when you accidentally forget the damn thing in the office and your home... or vice versa.
Don't want to keep it on the keychain... since you know if you do that, you'll break.. and still have a problem.
Yea... they suck.
The problem with early-death of SecurID fobs was primarily isolated to a bad batch of tokens, and is no longer a common problem.
I manage a site with 7,000+ tokens, and while we still get a few people who manage to crack the LCD or static-zap their token into "ProG" mode, we no longer see any new cases of the "Flashing eights" disease.
I'm not the world's biggest fan of RSA, but they do have a simple and effective web-based self-enrollment solution for deploying replacement tokens to users without a lot of admin hand-holding.
The unofficial SecurID Users group is always looking for new, verifiable horror stories about SecurID (ones not involving the lavatory are preferred):
groups.yahoo.com/group/se...