Rickie Loesoe (@CPTNG1) profile picture

Ora pro nobis

XXX
Joined November 2012
Photo by Rickie Loesoe (@CPTNG1)Photo by Rickie Loesoe (@CPTNG1)Photo by Rickie Loesoe (@CPTNG1)Photo by Rickie Loesoe (@CPTNG1)Photo by Rickie Loesoe (@CPTNG1)Photo by Rickie Loesoe (@CPTNG1)Photo by Rickie Loesoe (@CPTNG1)Photo by Rickie Loesoe (@CPTNG1)Photo by Rickie Loesoe (@CPTNG1)Photo by Rickie Loesoe (@CPTNG1)
Rickie Loesoe retweeted
Replying to @chinesechiz
an idiot in motion is better than a genius at rest
6
5
2
244
8,136
Er ligt een dakloze in m’n portiek met van die pluche knuffelbeesten pantoffels aan z’n voeten.
2
105
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.
915
7,055
1,159
57,840
3,861,126
Net als asha wetenschapsjournalist. Ze weten ze wel te vinden bij de kwaliteitsmedia zeg kolere. 🤣🤣
1
102
Rickie Loesoe retweeted
Iemand heeft mijn foto geretweet. Wie? En waarom? Het is nogal ongepast.
71
8
4
67
27,325
De staat van dit land...
1
231
Nou, daar gaan jullie scorito's.
1
188
Rickie Loesoe retweeted
Replying to @CPTNG1
@CPTNG1 – at Amsterdam, The Netherlands
1
1
3
159
Wervelend! Zin in het WK! #neduzb
2
625
Rickie Loesoe retweeted
Bouw maar een nieuwe De Meer ergens in Amsterdam.
7
2
1
82
14,340
Nog één keer ongelukjesonderbroek en ik klaag @HEMA aan voor geleden emotionele schade.
2
197
Net alsof… 🤣🤣
Replying to @cisrits
Een van die gozers zag ik op YT over A'dam. Doet net alsof het een grote tyfuszooi is terwijl hij de (ex-) krakers bij Vrankrijk filmt. Wat een stemmingmakerij. Maar het verkoopt kennelijk goed, dat hitsen.
1
313
Zalig paasfeest. 🥚
224
Ik zie net een reclamespotje "Zuivel, de bouwstoffen voor harde werkers". Met een lichtdonkere meneer van kleur. Ongelukkiger kan je niet inclusiviteitscasten, en dan doel ik niet eens op "harde werkers".
2
231
Wat is dit slecht zeg. 🤣😭 #pecaja
448
Wel lekker rustig op straat zo zonder marokkanen. Nog wel.
1
344
Mijn eerste tweede date in vijftien jaar was een groot succes. <3
1
293