Article View: alt.games.warcraft
Article #340851Re: Threat to authenticators?
From: Cryptoengineer
Date: Mon, 21 Mar 2011 18:37
Date: Mon, 21 Mar 2011 18:37
57 lines
3801 bytes
3801 bytes
On Mar 21, 6:16 am, Urbin <ur...@invalid.invalid> wrote: > On Mon, 21 Mar 2011 09:45:46 GMT, Ashen Shugar wrote: > > I think it was Urbin <ur...@invalid.invalid> that wrote something > > like... > > > >On Sat, 19 Mar 2011 21:09:06 +0000, Catriona R wrote: > > > >> On Sat, 19 Mar 2011 21:03:26 +0000 (UTC), ScratchMonkey > > >> <ScratchMonk...@sewingwitch.com> wrote: > > > >> >http://threatpost.com/en_us/blogs/rsa-warns-customers-targeted-attacks- > > >> >wake-hack-031811 > > > >> Guess not: > > > >> "The Blizzard Authenticators are based off modified Vasco tokens. I'm > > >> sorry to hear about RSA's troubles, but it will not affect the > > >> Blizzard Authenticator." > > > >> http://blue.mmo-champion.com/topic/164619/rsa-compromise-concerns-abo... > > > >Hm, famous last words or justified consolation? > > > Well, it sounds like the Blizzard authenticators use a somewhat > > different algorithm to the RSA ones, so nothing about the RSA stuff > > would give a direct method to hacking Blizzard authenticators. The > > only possible problem that I could see would be if the RSA stuff isn't > > actually properly designed. A properly designed encryption method is > > secure even if people know exactly how it works. If however, the RSA > > stuff *isn'* properly designed and the Blizzard authenticators use a > > similarly improper design, then knowing how the RSA stuff is weak > > could show someone how the Blizzard authenticators are probably weak > > and thus how to "hack" them. > > > RSA's comments suggest that their design is probably designed properly > > and their suggestions to be careful are just ones that everyone should > > be doing anyway all the time to avoid man in the middle attacks that > > circumvent the protection from having an authenticator. > > Oh, I agree with your conclusion. It was more the wording of the blue poster > that prompte my post. The "but it will not affect the X" sounds a lot like > "but there is nothing to worry about" often heard in disaster scenarios > before people grasp the full potential of what occurred. > > Cheers > Urbin I used to work at RSA - in fact, I created a number the software token implementations for PDAs and cellphones. The algorithms used have had a lot of review, both internal and external, but are not made public for business competition reasons. The security of the system doesn't rely on keeping the algorithms secret. The recent attack, while embarrassing, isnt really significant. pt
Technical Details
Message-ID:
<800b2f91-722e-4006-8093-fa09839d7be7@z27g2000prz.googlegroups.com>Path:
mbox-mo1.pugleaf.net!g2news2.google.com!postnews.google.com!z27g2000prz.googlegroups.com!not-for-mailReferences:
<Xns9EAD8EFCB92E2scratchmonkey@85.214.73.210> <8ukkapFbvcU1@mid.individual.net> <slrniodvaq.p9k.urbin@stinky-local.trash.net> <4d871ae8.894431@News.Individual.NET> <slrnioe9bd.gf8.urbin@stinky-local.trash.net>Show Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!g2news2.google.com!postnews.google.com!z27g2000prz.googlegroups.com!not-for-mail From: Cryptoengineer <pete...@gmail.com> Newsgroups: alt.games.warcraft Subject: Re: Threat to authenticators? Date: Mon, 21 Mar 2011 11:37:23 -0700 (PDT) Organization: http://groups.google.com Lines: 68 Message-ID: <800b2f91-722e-4006-8093-fa09839d7be7@z27g2000prz.googlegroups.com> References: <Xns9EAD8EFCB92E2scratchmonkey@85.214.73.210> <8ukkapFbvcU1@mid.individual.net> <slrniodvaq.p9k.urbin@stinky-local.trash.net> <4d871ae8.894431@News.Individual.NET> <slrnioe9bd.gf8.urbin@stinky-local.trash.net> NNTP-Posting-Host: 71.233.180.137 Mime-Version: 1.0 X-Trace: posting.google.com 1300732643 30888 127.0.0.1 (21 Mar 2011 18:37:23 GMT) X-Complaints-To: groups...@google.com NNTP-Posting-Date: Mon, 21 Mar 2011 18:37:23 +0000 (UTC) Complaints-To: groups...@google.com Injection-Info: z27g2000prz.googlegroups.com; posting-host=71.233.180.137; posting-account=BUItcQoAAACgV97n05UTyfLcl1Rd4W33 User-Agent: G2/1.0 X-HTTP-UserAgent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.15) Gecko/20110303 Firefox/3.6.15,gzip(gfe) Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit