19/ We know the flaws of the NYTime live election night data feed, how it didn't accurately reflect the official counts, why it appeared to show flipped votes and jumps on one side or the other. The question is whether such things exist in the raw data.
9
8
1
297
20/ "they work for LeadStories? fact checkers? shame on them!!! .... they are the enemies of the people" That's me!!! That's me!!!! I'm not feeling ashamed, though.
6
10
2
441
21/ "We are going to do a mock election... we'll show you how the routers work ... we'll show packet captures in real time". I'm actually looking forward to this. Dominion machines can be networked, but DEF CON Voting Village didn't have networked machines to play with.
3
12
0
342
22/ "I saw Hari Hursti is here" (and some criticism of Hari). He brings voting machines to the DEF CON hacking conference for hackers to play with, confirming they are easily hackable -- but they don't like him because he still rejects the idea that the 2020 election was hacked.
15
23
2
383
23/ The evidence that I'm here to validate is showing that it was hacked -- not that it could've been hacked. I know it could've been hacked, by either side. I'm hoping to see the raw details showing it was indeed hacked or manipulated or fraud happened.
6
22
5
380
24/ Yes, the schedule is for later today, to have breakout sessions, where (I think) I'll get to sit down and personally look at raw data -- and hopefully, get to post to the Internet for experts like Laura Chappell to see as well.
Replying to @ErrataRob
Rob - Did #Lindell provide a schedule for the event? Is there a time listed for the "packet capture" release? Not sure I can watch much more of this ranting and emotional hype.
5
8
0
283
25/ Phil Waldron kicked off the breakout session. He wasn't involved in collecting the packet-captures, so didn't have clear answers. But he suggested: 1. the packet-captures come from a Chinese network 2. they are in a proprietary BLX/PLX format But he didn't seem sure.
13
10
6
226
26/ ...but we haven't got the actual data yet, but soon. We are still dealing with lunch.
17
6
3
227
27/ They've given us access to a server on the local WiFi network that has the "data" that we are supposed to be analyzing. We are struggling to figure out what this data contains. I've put the smaller files up on github: github.com/robertdavidgraham…
35
80
26
422
They're RTF files, inexplicably converted to hex, each one containing a table of IP addresses without context about where those addresses came from.
8
8
6
176
Must be rusty on my networking knowledge. Could have sworn IP addresses in packet captures used to be encoded in IPv4 packets and not in hex-encoded RTF files over the network.

7:03 PM · Aug 10, 2021

11
16
7
220
It's like a Left Shark but with more Cyber
1
0
0
30
This is not a packet capture, it's just a list of IPs.
2
0
0
16
1,286
IPv5 is RTF encoded
2
0
0
23
.@netspooky was kind enough to point out that all of these IPs except three are in GreyNoise as known internet-wide scanners (mostly mirai and variants)
Out of the 11 IPs in this document provided, only 3 aren't on GreyNoise...And it's all very common web scanner stuff.
1
3
0
27