turcopelier | Why does the name of Joe Biden's former
Internet Technology guru, Warren Flood, appear in the meta data of
documents posted on the internet by Guccifer 2.0? In case you do not
recall, Guccifer 2.0 was identified as someone tied to Russian
intelligence who played a direct role in stealing emails from John
Podesta. The meta data in question indicates the name of the person who
actually copied the original document. We have this irrefutable fact in
the documents unveiled by Guccifer 2.0--Warren Flood's name appears
prominently in the meta data of several documents attributed to
"Guccifer 2.0." When this transpired, Flood was working as the CEO of
his own company, BRIGHT BLUE DATA. (brightbluedata.com). Was Flood
tasked to masquerade as a Russian operative?
Give Flood some props if that is true--he fooled our Intelligence
Community and the entire team of Mueller prosecutors into believing that
Guccifer was part of a Russian military intelligence cyber attack. But a
careful examination of the documents shows that it is highly unlikely
that this was an official Russian cyber operation.
Here's what the U.S. Intelligence Community wrote about Guccifer 2.0
in their very flawed January 2017 Intelligence Community Assessment:
We assess with high confidence that the
GRU used the Guccifer 2.0 persona, DCLeaks.com, and WikiLeaks to release
US victim data obtained in cyber operations publicly and in exclusives
to media outlets.
-
- Guccifer 2.0, who claimed to be an independent Romanian hacker, made multiple contradictory statements and false claims about his likely Russian identity throughout the election. Press reporting suggests more than one person claiming to be Guccifer 2.0 interacted with journalists.
- Content that we assess was taken from e-mail accounts targeted by the GRU in March 2016 appeared on DCLeaks.com starting in June.
The laxity of the Intelligence Community in dealing with empirical
evidence was matched by a disturbing lack of curiosity on the part of
the Mueller investigators and prosecutors.
0 comments:
Post a Comment