I know it wasn't intentional. Its just unfair to those who worked on the problem.
Samsung: Disable_Windowsupdate.exe
- Thread starter niemiro
- Start date
I am sure posting inaccurate information was not intentional either. But blogging is a form of journalism and to that, there are Journalism ethics and standards that includes truthfulness and accuracy. That means journalists must do their "due diligence" to ensure accuracy before going to press - at least if they wish to be viewed as a professional and taken seriously.
So, IMO, whether it be laziness, a rush to meet some deadline, or whatever, it was an intentional decision to not take the time for due diligence to ensure the accuracy of the reporting.
FTR - I don't recall such mis-information ever posted at Security Garden! :rose: :) :thumbsup2:
This is the problem, it's a very easy assumption to make. From another person's point of view, that article makes it seem like Patrick made the discovery with a little bit of help from others. I told my friend that a former trainee had made a huge discovery and linked him the article, to which he replied "Is Patrick the trainee?" Funny that.
So going back to how this thread started: congratulations on your discovery Brian (and Ryan!). Sorry that your moment of glory ended this way and I hope the next one doesn't get tainted in the same way :)
Jared
Sysnative Staff, BSOD Kernel Dump Expert
- Feb 3, 2014
- 1,591
It's quite a valid one though to be honest.
Patrick hasn't explicitly stated that he never made the discovery, and that's why people make the assumption. Usually, if nobody states otherwise, it usually means they were the ones who found it. Hence the reason why sources should be used.
Last edited by a moderator:
Okay, I just got home from work and read the replies and I'm really upset because this is not how I meant this to turn out whatsoever.
First off, never anywhere do I take credit for the discovery of this. Since the original #1 first literal creation of my blog post, I gave credit where credit was due to everybody involved + Sysnative. I said wavly was the user with the problem right off the bat with a hyperlink to the thread right in the words, BrianDrab provided the invaluable Windows Update help, and even pasted a link to the thread, etc. I went to bed, woke up, and there were articles everywhere. No one ever asked me any questions from the news sites about who found it, they just wrote their articles. Remember I even mentioned somewhere earlier in this thread that I noticed one of the articles said I was the discoverer, the Windows update fixer, etc, and that it was not true, and I was going to speak with the editor to fix it? So even I was bothered by being labeled the sole person involved, since there were multiple people, and I mentioned them all right in my own blog post. Any other emails I've received from news websites are just general side questions from editors, and I never explicitly stated that I am the sole #1 behind this entire ordeal. I would never do such a thing, because it's simply not the truth. I've clarified at the very top of my blog post all of the users involved in-depth.
Next, I had absolutely no idea that Richard was in active private discussion with Microsoft to fix this. No idea. If I knew, I wouldn't have publicly blogged about it. I hope everybody knows this to be true, because I've been here for a long time, and you guys hopefully know I'm not a malicious person. I did not do this to do ANY HARM to any of my friends, or anyone in general. This is just a really unfortunate misunderstanding that occurred from me trying to do a good thing, which backfired into a bad thing, especially for Richard.
I got excited that you guys found such a security issue, that I felt we should all be noticed for it. This backfired by a lot of news articles thinking that just because I wrote the blog post, that I was the only one involved, even though I have everyone involved written in my blog post. I guess they don't care to include that, apparently. This also further (more seriously) backfired by Microsoft's behavior towards Richard after the ordeal.
I'm really upset, and I'm really sorry. I don't know what else to say. I didn't mean from any harm to come from this, I was really just trying to help people. I did not mean for it to be a "leak", I didn't know I was leaking anything. I was just trying to help people become aware of a security risk, not make people angry at me or ruin relationships. This has all gone horribly wrong...
First off, never anywhere do I take credit for the discovery of this. Since the original #1 first literal creation of my blog post, I gave credit where credit was due to everybody involved + Sysnative. I said wavly was the user with the problem right off the bat with a hyperlink to the thread right in the words, BrianDrab provided the invaluable Windows Update help, and even pasted a link to the thread, etc. I went to bed, woke up, and there were articles everywhere. No one ever asked me any questions from the news sites about who found it, they just wrote their articles. Remember I even mentioned somewhere earlier in this thread that I noticed one of the articles said I was the discoverer, the Windows update fixer, etc, and that it was not true, and I was going to speak with the editor to fix it? So even I was bothered by being labeled the sole person involved, since there were multiple people, and I mentioned them all right in my own blog post. Any other emails I've received from news websites are just general side questions from editors, and I never explicitly stated that I am the sole #1 behind this entire ordeal. I would never do such a thing, because it's simply not the truth. I've clarified at the very top of my blog post all of the users involved in-depth.
Next, I had absolutely no idea that Richard was in active private discussion with Microsoft to fix this. No idea. If I knew, I wouldn't have publicly blogged about it. I hope everybody knows this to be true, because I've been here for a long time, and you guys hopefully know I'm not a malicious person. I did not do this to do ANY HARM to any of my friends, or anyone in general. This is just a really unfortunate misunderstanding that occurred from me trying to do a good thing, which backfired into a bad thing, especially for Richard.
I got excited that you guys found such a security issue, that I felt we should all be noticed for it. This backfired by a lot of news articles thinking that just because I wrote the blog post, that I was the only one involved, even though I have everyone involved written in my blog post. I guess they don't care to include that, apparently. This also further (more seriously) backfired by Microsoft's behavior towards Richard after the ordeal.
I'm really upset, and I'm really sorry. I don't know what else to say. I didn't mean from any harm to come from this, I was really just trying to help people. I did not mean for it to be a "leak", I didn't know I was leaking anything. I was just trying to help people become aware of a security risk, not make people angry at me or ruin relationships. This has all gone horribly wrong...