2/ "...our duty as Americans to fight, kill and die for our rights."
By November 2020 there is talk among the conspirators of the need to get violent..
By Dec. 20 hotel reservations are made by CALDWELL for the 6th... and CROWL has attended a North Carolina training camp.
3/ By Dec 30, WATKINS (Ohio) confirms to CALDWELL (Virginia) that her group will come. They discuss staging, logistics..
CALDWELL says a "full bus 40+" people coming from North Carolina.
[Observation: I suspect we will learn a lot more about NC folks in coming weeks]
4/ "That way the boys don't have to try to schlep weps on the bus"
-CALDWELL to WATKINS on Dec 30, explaining that an unnamed [PERSON THREE] will drive up a truck with weapons separately from one of the bussed-in contingents.
"Leadership only" conference call is named "DC op"
5/ Chats describe how CROWL & WATKINS (and others) will "link up" with the "North Carolina crew" On the 4th they depart Ohio, headed for DC.
On the morning of January 6th, they kit up for battle and head to the #Capitol.
6/ Here they are: CROWL, WATKINS & others in a disciplined, geared-up line... moving up the #Capitol steps on the East side.
Per the indictment, they forced their way past police and into the building.
7/ Meanwhile, over on the West side of the #Capitol, CALDWELL & unnamed others are in the mob fighting through police lines, up the stairs, and eventually breaching the doors.
By 3:05pm he reports making it inside.
8/ After the storming of the #Capitol they start trying to hide their tracks, deleting messages, etc.
WATKINS & CROWL return to Ohio. But after they are identified on the 14th (see tweet👇👇) they head to Virginia to stay w/ CALDWELL.
NEW: @WhatsApp caught & fixed a sophisticated zero click attack...
Now they've published an advisory about it.
Say attackers combined the exploit with an @Apple vulnerability to hack a specific group of targets (i.e. this wasn't pointed at everybody)
Quick thoughts 1/
Wait, you say, haven't I heard of @WhatsApp zero-click exploits before?
You have.
A big user base makes a platform big target for exploit development.
Think about it from the attacker's perspective: an exploit against a popular messenger gives you potential access to a lot of devices.
You probably want maximum mileage from that painstakingly developed, weaponized, and tested exploit code you created/ purchased (or got bundled into your Pegasus subscription).
3/ The regular tempo of large platforms catching sophisticated exploits is a good sign.
They're paying attention & devoting resources to this growing category of highly targeted, sophisticated attacks.
But it's also a reminder of the magnitude of the threat out there...
WHOA: megapublisher @axelspringer is asking a German court to ban an ad-blocker.
Their claim that should make everyone nervous:
The HTML/ CSS code of websites are protected computer programs.
And influencing they are displayed (e.g by removing ads) violates copyright.
1/
2/ Preventing ad-blocking would be a huge blow to German cybersecurity and privacy.
There are critical security & privacy reasons to influence how a websites code gets displayed.
Like stripping out dangerous code & malvertising.
Or blocking unwanted trackers.
This is why most governments do it on their systems.
3/Defining HTML/CSS as a protected computer program will quickly lead to absurdities touching every corner of the internet.
Just think of the potential infringements:
-Screen readers for the blind
-'Dark mode' bowser extensions
-Displaying snippets of code in a university class
-Inspecting & modifying code in your own browser
-Website translators
3/ What still gives me chills is how many cases surfaced of people killed by cartels... or their family members... getting targeted with Pegasus spyware.
The #PegasusProject found even more potential cases in Mexico.