Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Comments
How Guccifer 2.0 Got 'Punk'd' by a Security Researcher
Newest First  |  Oldest First  |  Threaded View
antivirussupport12
50%
50%
antivirussupport12,
User Rank: Strategist
3/12/2018 | 11:46:13 AM
Re: Why would anyone still believe YOU KNOW WHAT YOU TALK ABOUT?
I totally agree with you.This the way we can tackle this situation.if you know the situation and all other prospects you can handle it in a better way. visit https://antivirussupport.org for more.
ellascottgm123
50%
50%
ellascottgm123,
User Rank: Apprentice
3/11/2018 | 10:07:03 PM
Re: Why would anyone still believe Guccifer was driven by Russians?
Such a very useful article. Very interesting to read this article.I would like to thank you for the efforts you had made for writing this awesome article.
Gorilla Hunter
67%
33%
Gorilla Hunter,
User Rank: Strategist
3/9/2018 | 10:21:49 AM
Re: Why would anyone still believe YOU KNOW WHAT YOU TALK ABOUT?
So because he stopped talking to a reporter, he was punked? You demand facts, yet you are unable to back up your claim with any of your own. Julian Assange, the publisher of the hacked emails and knows who the source is, has came out time and time again saying the Russians had nothing to do with it.

http://thehill.com/policy/cybersecurity/346904-assange-meets-us-congressman-vows-to-prove-russia-did-not-leak-him

https://www.democracynow.org/2017/4/12/full_interview_julian_assange_on_trump 

https://www.huffingtonpost.com/entry/donna-brazile-owes-an-apology-to-julian-assange-and_us_59fe1c3ae4b076eaaae2701d

I doubt the story because I looked at the authors twitter feed, saw her politics, and then read her parroting the same agenda, and  once again hear the clams of "Russia did hax", when everyone who is involved with the DNC email dump says otherwise.  Also included three sources from both left and right. But hey, a dude stopped talking to a reporter, ao case closed, right?

 
Dong_Johnson
50%
50%
Dong_Johnson,
User Rank: Apprentice
3/8/2018 | 1:38:07 PM
Re: Why would anyone still believe YOU KNOW WHAT YOU TALK ABOUT?
You're not understanding the article I guess.  It's pretty clear Gucci was punked because he's no longer responding.  

 

Russia has various means of accomplishing what they want to, and using low-level useful idiots isn't below their means either.  I agree with the premise presented in the article that it's clear Russia wasn't going "all-in" using state resources (which would be attributable directly, of issue) to publish the stolen emails, and instead decided to disseminate them using troll networks rather than official ones.  The fact is you have no compelling or offered reason to doubt anything in this story.  If you did you wouldn't be doing the typical spambot/chatbot song and dance of crying about people focusing on "russia russia russia' for what Russia did did did provably provably provably.  Get your politics out of here, this is a discussion about facts.   The fact is Russia was involved.

Once again, if you want to discredit any aspect of this, you're going to need something to point to.  Whining won't help your case.
Gorilla Hunter
40%
60%
Gorilla Hunter,
User Rank: Strategist
3/8/2018 | 11:02:48 AM
Re: Why would anyone still believe Guccifer was driven by Russians?
Because "RUSSIA, RUSSIA, RUSSIA". There is nothing here that shows that Guccifer was "punked" or that he is even connected to the Russians, but we have to hear once again "RUSSIA, RUSSIA, RUSSIA!!!1!"
SchemaCzar
50%
50%
SchemaCzar,
User Rank: Strategist
3/8/2018 | 10:18:09 AM
Why would anyone still believe Guccifer was driven by Russians?
Everything in this article makes me doubt that Guccifer 2.0 was driven by Russian state actors.  To fall for a trick like this is not what happens with Russian state-level hackers.  If the Russians were paying him/her, the only purpose was to muddy the waters.  It's hard to think of a nation-state, or a trans-national movement, that would be unable to set up a cutout like this to "look Russian."


AI Is Everywhere, but Don't Ignore the Basics
Howie Xu, Vice President of AI and Machine Learning at Zscaler,  9/10/2019
Fed Kaspersky Ban Made Permanent by New Rules
Dark Reading Staff 9/11/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
The State of IT Operations and Cybersecurity Operations
The State of IT Operations and Cybersecurity Operations
Your enterprise's cyber risk may depend upon the relationship between the IT team and the security team. Heres some insight on what's working and what isn't in the data center.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-4147
PUBLISHED: 2019-09-16
IBM Sterling File Gateway 2.2.0.0 through 6.0.1.0 is vulnerable to SQL injection. A remote attacker could send specially-crafted SQL statements, which could allow the attacker to view, add, modify or delete information in the back-end database. IBM X-Force ID: 158413.
CVE-2019-5481
PUBLISHED: 2019-09-16
Double-free vulnerability in the FTP-kerberos code in cURL 7.52.0 to 7.65.3.
CVE-2019-5482
PUBLISHED: 2019-09-16
Heap buffer overflow in the TFTP protocol handler in cURL 7.19.4 to 7.65.3.
CVE-2019-15741
PUBLISHED: 2019-09-16
An issue was discovered in GitLab Omnibus 7.4 through 12.2.1. An unsafe interaction with logrotate could result in a privilege escalation
CVE-2019-16370
PUBLISHED: 2019-09-16
The PGP signing plugin in Gradle before 6.0 relies on the SHA-1 algorithm, which might allow an attacker to replace an artifact with a different one that has the same SHA-1 message digest, a related issue to CVE-2005-4900.