Block, Siteadmin, SkipCaptcha, Upload, Automoderated users, delete, edit, move, nsTeam2RO, nsTeam2RW, nsTeam2_talkRO, nsTeam2_talkRW, protect, rollback, Administrators, template
293,672
edits
Changes
Jump to navigation
Jump to search
Line 72:
Line 72: − Line 85:
Line 84: − VIPS noted +
Ukrainian collusion (view source)
Revision as of 03:54, September 28, 2019
, 03:54, September 28, 2019→WikiLeaks
===WikiLeaks===
===WikiLeaks===
On May 10, 2016 CrowdStrike installed its Falcon software on DNC servers, two weeks before the last dated email in [[WikiLeaks]]' DNC collection. Adam Carter noted Falcon should have prevented an outside hack, according to its product claims: "either CrowdStrike's flagship product failed miserably to deliver on its claimed capabilities or it could mean CrowdStrike withheld evidence."<ref>http://g-2.space/cs2/</ref>
On May 10, 2016 CrowdStrike installed its Falcon software on DNC servers, two weeks before the last dated email in [[WikiLeaks]]' DNC collection. Adam Carter noted Falcon should have prevented an outside hack, according to its product claims: "either CrowdStrike's flagship product failed miserably to deliver on its claimed capabilities or it could mean CrowdStrike withheld evidence."<ref>http://g-2.space/cs2/</ref>
*June 15, 2016: “Guccifer 2.0” affirms the DNC statement; claims responsibility for the “hack;” claims to be a WikiLeaks source; and posts a document that the forensics show was synthetically tainted with “Russian fingerprints;"
*June 15, 2016: “Guccifer 2.0” affirms the DNC statement; claims responsibility for the “hack;” claims to be a WikiLeaks source; and posts a document that the forensics show was synthetically tainted with “Russian fingerprints;"
Veteran Intelligence Professionals for Sanity noted,
{{Quotebox|"We do not think that the June 12, 14, & 15 timing was pure coincidence. Rather, it suggests the start of a pre-emptive move to associate Russia with anything WikiLeaks might have been about to publish and to “show” that it came from a Russian hack.<ref>https://web.archive.org/web/20171112090338/https://consortiumnews.com/2017/07/24/intel-vets-challenge-russia-hack-evidence/</ref>}}
{{Quotebox|"We do not think that the June 12, 14, & 15 timing was pure coincidence. Rather, it suggests the start of a pre-emptive move to associate Russia with anything WikiLeaks might have been about to publish and to “show” that it came from a Russian hack.<ref>https://web.archive.org/web/20171112090338/https://consortiumnews.com/2017/07/24/intel-vets-challenge-russia-hack-evidence/</ref>}}