2/ Looking at charts, #EVERFORWARD may have slightly deviated from dredged navigation channel into shallower waters after departing Baltimore.
And got stuck.
She's apparently not blocking the navigation channel, but is quite close to it.
3/ The #EverForward's AIS track is... interesting.
People may read it as: she missed a waypoint (didn't make a turn) heading from Craighill Angle into Craighill Channel.
Caveat: accidents = complicated & AIS tracks can be *imprecise* so take all guesses w/big grain of salt!
4/ UPDATE: was going through wind records (not substantial), speed (she kept speed), draught (lot of empty containers), load condition.. when... @mercoglianos with a video!
Takeaway: he also thinks #EverForward missed the turn!
Now, here's the thing...
5/ The #EverForward is aground in a shoal area of ~24 feet of water.
She lists as 42.6 feet of draught (depth below waterline).
Takeaway: VERY stuck. Getting her un-stuck & back into the 51 foot deep Craighill Channel is likely to be a *big production.*
6/ When you talk about ships aground, tides come up.
NEW: fresh trouble for mercenary spyware companies like NSO Group.
@Apple launching substantial bounties on the zero-click exploits that feed the supply chain behind products like Pegasus & Paragon's Graphite.
With bonuses, exploit developers can hit $5 million payouts. 1/
2/ Apple is introducing Target Flags which speeds the process of getting exploits found & submitters rewarded.
This faster tempo is also a strike against the mercenary spyware ecosystem.
And the expanded categories also hit more widely against commercial surveillance vendors.
3/ If I contemplating investing in spyware companies I'd want to carefully evaluate whether their exploit pipeline can match what @apple just threw down.
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