Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

LOL, you try and get the DNS communication records from Biden's white house and see how far that gets you.

You don't even know what "DNS Communication records" means by virtue of typing it. Laugahable.

At least one of us has looked at PCAP logs using Wireshark to troubleshoot layer 3 communications issues.

Wireshark is for n00bs.

That's a "n00b" remark regarding Wireshark. There are other sniffer front ends and traffic analyzers that can provide more sophisticated analysis, but Wireshark is in every professional's tool kit for quickly digging into a raw capture file.

Lol. Is that what was written in the introductory paragraph of your Wireshark For Dummies book?

Anonymous wrote:NP... I think this filing was nothing but partisan political theater intended to falsely enrage the right wing. Durham should be fired for this stunt.

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:So the same folks accusing Trump of insurrection, we now find out were spying on him. Interesting development

They weren't spying on him. Read the primary source documents. It was a contract under the Obama administration that tracked DNS records (public) to mitigate hacking threats. You would know that if you consumed reliable sources of news, but instead, you go with the ones that also told you Trump was a legit billionaire, that Seth Rich was murdered and there was a child sex ring operating out of Comet Pizza's nonexistant basement.

Why do you like being lied to, and why do you propagate the lies?

BTW they are still lying about Seth Rich despite having to pay his family a settlement.

Wait. So Russia didn’t hack the DNC?

Of course Russia hacked the DNC.

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

LOL, you try and get the DNS communication records from Biden's white house and see how far that gets you.

You don't even know what "DNS Communication records" means by virtue of typing it. Laugahable.

At least one of us has looked at PCAP logs using Wireshark to troubleshoot layer 3 communications issues.

Wireshark is for n00bs.

That's a "n00b" remark regarding Wireshark. There are other sniffer front ends and traffic analyzers that can provide more sophisticated analysis, but Wireshark is in every professional's tool kit for quickly digging into a raw capture file.

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

LOL, you try and get the DNS communication records from Biden's white house and see how far that gets you.

You don't even know what "DNS Communication records" means by virtue of typing it. Laugahable.

At least one of us has looked at PCAP logs using Wireshark to troubleshoot layer 3 communications issues.

Wireshark is for n00bs.

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:So the same folks accusing Trump of insurrection, we now find out were spying on him. Interesting development

They weren't spying on him. Read the primary source documents. It was a contract under the Obama administration that tracked DNS records (public) to mitigate hacking threats. You would know that if you consumed reliable sources of news, but instead, you go with the ones that also told you Trump was a legit billionaire, that Seth Rich was murdered and there was a child sex ring operating out of Comet Pizza's nonexistant basement.

Why do you like being lied to, and why do you propagate the lies?

BTW they are still lying about Seth Rich despite having to pay his family a settlement.

Wait. So Russia didn’t hack the DNC?

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

LOL, you try and get the DNS communication records from Biden's white house and see how far that gets you.

You don't even know what "DNS Communication records" means by virtue of typing it. Laugahable.

At least one of us has looked at PCAP logs using Wireshark to troubleshoot layer 3 communications issues.

Anonymous wrote:

Anonymous wrote:

LOL, you try and get the DNS communication records from Biden's white house and see how far that gets you.

You don't even know what "DNS Communication records" means by virtue of typing it. Laugahable.

Anonymous wrote:

Anonymous wrote:

LOL, you try and get the DNS communication records from Biden's white house and see how far that gets you.

You don't even know what "DNS Communication records" means by virtue of typing it. Laugahable.

Anonymous wrote:

LOL, you try and get the DNS communication records from Biden's white house and see how far that gets you.

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:

Anonymous wrote:Where and when was this information shared and by whom?

Here:

http://www.slate.com/articles/news_and_politics/cover_story/2016/10/was_a_server_registered_to_the_trump_organization_communicating_with_russia.html

https://www.cnn.com/2017/03/09/politics/fbi-investigation-continues-into-odd-computer-link-between-russian-bank-and-trump-organization/index.html

I don't really think the biggest issue is the access to DNS info of Trump's private companies and organizations. Those ISPs probably have agreements in place that allow them to disclose such information to a third party, buried in their service agreement. The bigger issue is the EOP. Any electronic communications from that entity are almost certainly privileged.

What you are missing here....they were not in possession of the actual content of the communications and transmissions. This was ONLY DNS information. Numbers. that is it.

I am not referring to the contents of emails or messages. DNS lookup is a type of electronic communication, and in the case of the EOP, likely protected against public sniffing.

I'm not sure about that. Might be. Or might be considered public communications.

In any event, Sussman had nothing to do with the CIA meeting that happened later.