Article View: alt.games.warcraft
Article #340850Re: Threat to authenticators?
From: BombayMix
Date: Mon, 21 Mar 2011 14:08
Date: Mon, 21 Mar 2011 14:08
45 lines
3443 bytes
3443 bytes
On Mar 21, 10: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. ie "Our nuclear power stations are safe and disaster proof!!"
Technical Details
Message-ID:
<46859d97-3591-4872-9253-de32c888b0fd@r13g2000yqk.googlegroups.com>Path:
mbox-mo1.pugleaf.net!g2news2.google.com!postnews.google.com!r13g2000yqk.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!r13g2000yqk.googlegroups.com!not-for-mail From: BombayMix <bomb...@altavista.co.uk> Newsgroups: alt.games.warcraft Subject: Re: Threat to authenticators? Date: Mon, 21 Mar 2011 07:08:44 -0700 (PDT) Organization: http://groups.google.com Lines: 57 Message-ID: <46859d97-3591-4872-9253-de32c888b0fd@r13g2000yqk.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: 163.166.8.13 Mime-Version: 1.0 X-Trace: posting.google.com 1300716525 22063 127.0.0.1 (21 Mar 2011 14:08:45 GMT) X-Complaints-To: groups...@google.com NNTP-Posting-Date: Mon, 21 Mar 2011 14:08:45 +0000 (UTC) Complaints-To: groups...@google.com Injection-Info: r13g2000yqk.googlegroups.com; posting-host=163.166.8.13; posting-account=siEMHAkAAACYqWpxnw68OThaFP_K_98I 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