Pinned Tweet
A: Good to see you here again!
B: It's my first time
A: You were here yesterday
B: You should have forgotten that
-> EU privacy regulation
Not entirely 100% tongue in cheek, this alone should be enough to secure an anti-trust conviction.
This quoted post is unavailable.
1
26
My wife and I wanted to buy someone an Uber gift card. No dice. No apps, web, payment methods would allow it. The fraud detection was too strong.
So we went on amazon and bought an Uber gift card there no problem.
I know something about fraud, but that seems kind of nuts.
1
4
74
I think we may be in the Golden age of chatbots. Think Google search when PageRank was important and SEO hadn't turned the corpus into sludge.
27
crankycatcoder retweeted
In your ideal system, yes there will be some absentee ballots, but most people will vote in person in a polling place behind a screen where nobody can see or control their vote.
This is a story.
Years ago, I took physics and there was this nut who they only let loose on the grad students. But, of course, a prof got sick and he was assigned to teach us a class. It was basically a train wreck, but there was a phrase I remember from over 40 years ago. /1
1
89
I'm not asking for the answer to be perfect, although I understand why you think it needs to be (FU, tort bar) but I'd like some reasoning going on beyond "well the RCT says" thinking. I'm fully in favor of RCT as the gold standard.
/4
1
23
Decades ago a friend and I were drinking beer in my living room and listening to "Israelites" on a loop. My wife gets home and it takes her about 10 minutes to ask what on earth we're doing.
Listening to a song on repeat is a sign of autism. Familiar music will trigger a dopamine hit and help regulate the brain.
I found this out as I listened to the same song about forty times tonight.
38
> TLS traffic over DHE ciphers have a 1-byte secret, "04"
presented without comment
Announcing 3 Critical vulns for hundreds of millions of IoT, Firewalls, OT, and Military devices including: Palo Alto Networks, Comcast, D-Link, HP, Canon, Honeywell, GE, Oracle, Siemens, Rockwell, Digi, Lockheed Martin, Boeing...
The vulns are with GoAhead Web Server which is a backend library used by these devices. There's a patch available from GoAhead but that doesn't mean there's a patch available for the devices yet -- that's up to the manufacturer.
- TLS traffic over DHE ciphers have a 1-byte secret, "04", meaning anyone can decrypt connections to these devices and steal login credentials and session tokens if the client negotiated with DHE ciphers like the latest TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256, which is extremely likely.
- LibreSSL mTLS has been completely bypassed, meaning anyone can connect over mTLS. If you have one of these devices listening on the internet and are expecting mTLS to protect it from attackers, take it offline or patch asap.
- OpenSSL Certificate Revocation Lists (CRLs) are not enforced, meaning if a user device is stolen or compromised, and you revoke that mTLS cert, nothing actually happens. There are a lot of other attacks this can be used for.
These are critical because these types of devices run our world. Water systems, electricity, military, firewalls, critical infrastructure.
foxio.io/blog/choose-your-ba…
1
96
crankycatcoder retweeted
Replying to @KelseyTuoc @CharlesFLehman
yes; also plausible IMO is “Cloudflare will run your AI defense swarm and you just pay a small monthly fee and don't really have to think about it”
This is hilarious and very common.
(It's the kind of thing that makes me unsympathetic to the Google employees who complain about 'excessive' process.)
Security called me at 6:12 AM today.
"Patch every PHP server immediately."
I asked what happened.
"Two critical vulnerabilities. Remote code execution. No authentication required."
Cool.
How many PHP servers do we have?
According to inventory: 12
According to reality:
Nobody knows.
We found one running WordPress.
Three running old internal tools.
One under someone's desk.
Two inside vendor appliances.
A forgotten employee directory from 2016.
And a server named:
PHP-OLD-DO-NOT-TOUCH
Naturally, that one runs payroll exports.
Then we found a PHP 5.6 box.
I asked who owned it.
The documentation said:
BRIAN.
Brian left in 2019.
We called Brian.
He said:
"Oh wow, that's still running?"
Excellent.
By 8 AM, leadership joined the incident call.
CEO:
"Can hackers actually get in?"
Security:
"Potentially yes."
CEO:
"Without a password?"
Security:
"Yes."
CEO:
"Then why do WE need passwords?"
Not the lesson.
Finance asked if we could wait until the weekend to patch because downtime affects revenue.
Security explained that the alternative was letting strangers execute code on our servers.
Finance asked for a cost comparison.
At 9:17, someone suggested temporarily taking the vulnerable websites offline.
Marketing refused.
"Our campaign is live."
So for the next hour, the company officially decided maintaining a landing page for 20% off webinar registration was more important than preventing remote server takeover.
We finally patched everything we could find.
Then our scanner discovered another PHP server.
Hostname:
TEMP-PHP-2014
Uptime:
4,512 days.
Nobody knows what it does.
Nobody owns it.
Nobody can shut it down.
But every time we block network access, the warehouse stops printing shipping labels.
Security has classified it as critical infrastructure.
It is running PHP 5.4.
The vulnerability has existed longer than half our employees.
The emergency patch took four hours.
Finding out what PHP actually runs took eleven.
The internet isn't held together with code.
It's held together with servers everyone is afraid to turn off.
2
135












