Live data from Hacker News

Technical report on DNC hack [pdf]

us-cert.gov

421–430 of 502 posts

Re: Technical report on DNC hack [pdf]

#421
post #361

Earlier quoted context omitted.

> b) ??? How about the FBI/CIA/DHS/NSA don't like people who don't play by the accepted rules sticking their nose into their business, so they tell a little white lie to try to avoid that? The three letter agencies have had plenty of people killed before, so "they'd never do that" isn't going to get you very far.

Think this through. Multiple people in the FBI, CIA, DHS, and NSA all decided this? Together? Did they have meetings? And no one is spilling the beans, even though there are maybe dozens or hundreds of people in on it? Not one of them has more to gain by revealing the conspiracy than by keeping silent? And they're all so confident that no one will squeal that they're having press releases now? And the point of this w…

Haha, I know, it does sound rather crazy. However, once again I will play the Snowden card: all of that was called crazy conspiracy talk, because there would be too many people involved who so thinking that is just crazy.

It's certainly not crazy to not trust these people. Deceit is their job.

Re: Technical report on DNC hack [pdf]

#422

Earlier quoted context omitted.

True. But the absence of sophistication constitutes evidence neither in favor nor against the "State Actor" hypothesis.

Until a Russian name or IP address is provided, the accusations fail to hold water. An incomplete proof is equivalent to "'cause we said so"

[deleted]

Re: Technical report on DNC hack [pdf]

#423

Earlier quoted context omitted.

The "evidence" boils down to: The Hackers drove a truck. Russians drive trucks. The Russians did the hacking. While its insulting that our government would try to pass off this drivel as "evidence", I'm much more dismayed that so many of my fellow Americans will uncritically accept it as such.

The actual evidence is probably closer to 'we have moles in the kremlin and taps on their phones' but they're not exactly going to publish that are they.

Isn't that kind of obvious to everyone at this point? It's just not out in the explicit open with the right kind of language. By giving such meager evidence of a "certainty", they're essentially giving away that they determined this via other means.

So, right now, let's assume it was a Russian spy agency that hacked the DNC. They're sitting there, thinking, "wow, these FBI folks somehow figured out it was us.". Then after reading this paper, "hmm, that's not a whole lot of evidence, they must have some proof that they're hiding. They must have a mole in our office. Find him, now."

Re: Technical report on DNC hack [pdf]

#425

Earlier quoted context omitted.

It is more like: 1. Hackers drove a custom built tank that has Moscow factory markings. 2. Similar versions of the tank were used in other campaigns attributed to Russian intelligence. 3. Crew in the tank has been associated with Russian intelligence operations going back ten years. 4. The tank left from a building known to be associated with Russian intelligence hacking campaign. Thus, the hackers probably take orde…

You should mention that the tank with the crew they have inside is publicly available to anybody in the malware archives of APT28/29. Anybody can plant it. Also both the powershell and the py2exe are completely reversible so you can take it, modify it and who's creation is that now? If there is kernel-level stuff then it would be a more solid case but not by much. On top of that, it's entirely possible other complete…

Got a link to the archive?

Re: Technical report on DNC hack [pdf]

#427

"At least one targeted individual activated links to malware hosted on operational infrastructure of opened attachments containing malware" - I pity that individual, like I'm sure he's getting blamed in the party like 'Hey, aren't you the piece of work who clicked a link'

It may have been many, I hear stories that the average user isn't that clued up. Dumb users should be sandboxed but if its your main people its a bit tricky i guess

Re: Technical report on DNC hack [pdf]

#428
post #51

This is a magic report. Over the next 24 hours, it will transform a huge number of people into experts on intelligence reporting requirements, hacking, sources and methods, and diplomacy.

Respectfully, do you feel this is constructive discourse? Because to me the purpose of your comment is to drag down other comments, even yet unmade ones, into the mud. Invalidating everyone's opinion on this subject except 0.1% of the population (namely very specific experts). Even politicians or professional political commentators wouldn't meet your high bar. And to the people who do feel like the bar should be set…

I was commenting on the phenomenon in which random "facts" from narrow professional niches are cherry-picked to make politically motivated arguments.

The show is playing now on the usual blogs, so rest easy. If I had been making an oblique argument attempting to shut people up, I failed rather miserably.

Re: Technical report on DNC hack [pdf]

#429
post #317

Earlier quoted context omitted.

Point 7 is the one you're supposed to be trying to explain Except that point 7 isn't at all controversial. EVERYONE hacks EVERYONE ELSE in cyber-espionage; even Canada was probably hacking the lame-ass security DNC email server, if only to fill a dossier. Remember that Clinton was set to be the next president of the United States; it is very much in Russia's (and anyone else's) best interest to know as much about her…

Er, the parent was replying to a poster who implied he did not believe "point 7." >Frankly, I find the suggestion that telling voters more about their candidate constitutes 'interference' to be repugnant Really? By this argument, I take it you believe political candidates' email (or cough tax returns) should automatically be made public? Much as I agree with transparency, I think we need to recognize that everyone--i…

>Much as I agree with transparency, I think we need to recognize that everyone--including political candidates--has some right to private communications.

No, they don't, unless you see the need for them to act against our interests without our knowleddge because markets or something, or see some sort of right for them to rule others.

Re: Technical report on DNC hack [pdf]

#430
post #309

Earlier quoted context omitted.

Point 7 is the one you're supposed to be trying to explain Except that point 7 isn't at all controversial. EVERYONE hacks EVERYONE ELSE in cyber-espionage; even Canada was probably hacking the lame-ass security DNC email server, if only to fill a dossier. Remember that Clinton was set to be the next president of the United States; it is very much in Russia's (and anyone else's) best interest to know as much about her…

Point 7 wasn't that the hack took place or the matter of who did it, it's the three-letter-agencies publicly accusing Russia of it. They did so because a) they believe it's provably true, or b) ???.

b) It justifies their ongoing employment.
Post reply on HN