Talk:EternalBlue

Questions
— Preceding unsigned comment added by 82.24.199.214 (talk)
 * question1: is there any relevant significance to 12 may?
 * http://www.onthisday.com/day/may/12
 * question 2: can bitcoin be traced? should it be traceable?
 * question 3: how long did the worm spend breeding before the strike?
 * question 4: should NSA report any similar exploits to the manufacturers concerned?
 * question 5: force Microsoft to provide critical updates to XP, etc forever?

Styling as EternalBlue vs ETERNALBLUE
I would suggest that ETERNALBLUE is the 'correct' form. This is the form that's used for all the codenames in the ShadowBrokers releases, and all caps is a common convention for codenames (see CIA cryptonym). However, to be honest it looks pretty jarring in prose whether here or in the news media - which is why I think the CamelCased EternalBlue has become far more popular. I personally don't propose changing the title of this article, or references elsewhere in Wikipedia - expect for the article The Shadow Brokers - where it's appropriate to use the original form. Snori (talk) 21:36, 14 May 2017 (UTC)

More info
"SMB ... of Microsoft Windows accepts specially crafted packets from remote attackers, allowing them to execute arbitrary code on the target computer". But the question is: why did MS comply with the (NSA?) request to provide such access? Why has it not been detected by outside parties (walled garden?). Technical details are needed. Zezen (talk) 12:38, 28 June 2017 (UTC)

Logo is Fan Art, REMOVE
I don't think EternalBlue has its own official logo? So why fool people and make a logo for it? Fan art has no place on Wikipedia. — Preceding unsigned comment added by 81.182.48.107 (talk) 16:46, 27 July 2018 (UTC)

Who is to "blame" for Baltimore? City vs. NSA vs. several others
First I know a bit about computers, so there's a "common sense" perspective to be had that I can help provide. There has been a patch available for this exploit for over two years, and IMO the City of Baltimore has some share in the "blame". The reason for the focus on "blame" is that today's news mentions the idea that the NSA is to "blame" for the existance of the malware, which has some truth, but it's also true that the City of Baltimore failed to properly update their computers like any average person with a computer would be expected to do, and despite millions of dollars being spent by the City on "IT", and a history of scandal. Four of their IT chiefs have resigned under cloud of scandal since 2012. I have RS for all of this, and limited Wikipedia skills. My proposal is to insert a balanced perspective, citing both the "blame the NSA" side of the issue, and also the "it's Baltimore's own fault" side of the issue. Which my limited Wikipedia awareness tells me is going to require some "synth". Is anyone interested on doing this with me. I'd rather not "go it alone" here. I've got RS to support both sides (for balance), and I suppose the 1st thing to do is get them into the list of citations at the bottom of the Article, but tbh I don't even know how to do that yet. Help?Tym Whittier (talk) 20:40, 28 May 2019 (UTC)
 * No. Victim blaming shouldn't be encouraged. 194.207.86.26 (talk) 06:29, 6 July 2019 (UTC)


 * Um no blame for Microsoft? They're the ones responsible for the vulnerability in the first place. 206.125.145.230 (talk) 13:40, 18 July 2020 (UTC)
 * You're forgetting an enormous amount of people who use PCs don't even know how to check for a Windows update and are overwhelmed by setting up a new account on Windows. So victim blaming, aside from being not cool in any context, in this sense is not even logical. Warm Yellow Sunflower (talk) 17:25, 3 November 2022 (UTC)


 * Hi, I just read this article wanting to learn more about it. I vaguely remember that this is related to wannacry. I had to go to that page to figure out the millions to billions in damages that happened as a result. All this is to say that this article needs more on that in its introduction. That's important information that's related to why this article is worth reading. 50.104.95.67 (talk) 02:49, 6 May 2023 (UTC)