Jesus | DevOps | Nonprofit | United ❤️ | 🎹
Lagos, Nigeria
Joined August 2020
- Tweets7.4K
- Following1.3K
- Followers1K
- Likes12.6K
04 ✨ retweeted
Lowkey miss the days when solving technical problems meant calling your tech friends. Now everybody just dey prompt Claude. AI has replaced bonding on technical challenges 😭
A vulnerability in PHP's core code dates back to 2012. What does this teach us about DevOps and security?
The PHP2Shell vulnerabilities disclosed on October 21, 2026, raised an important question: what happens when a critical security flaw affects the infrastructure running our applications?
Imagine you're managing an e-commerce platform. Orders are coming in, payments are processing, and business is going smoothly.
Then you discover your PHP runtime may be vulnerable to remote code execution.
Do you take the website offline to patch it, potentially losing customers and revenue? Or keep it running while you investigate, risking a security breach?
That's the difficult trade-off between availability and security.
Here's what DevOps engineers should take away:
🔹 Know your infrastructure. Maintain an inventory of servers, containers, dependencies and runtime versions. You can't patch what you don't know exists.
🔹 Test, then deploy. Run automated tests against security updates. Check application compatibility and have a rollback plan. For critical vulnerabilities, use an expedited patching process.
🔹 Understand the risk. Consider exposure, potential impact and available mitigations. Isolate or take affected services offline if the risk cannot be adequately controlled.
🔹 Automate security. Integrate dependency and container-image scanning into CI/CD. Monitor security advisories and rebuild images when their underlying components need patching.
🔹 Don't stop at patching. If exploitation is suspected, investigate logs, assess potential compromise and rotate exposed credentials.
🇳🇬 A thought for Nigerian businesses:
A website working perfectly doesn't mean it's secure.
Security monitoring, timely patching and recovery planning may seem like extra expenses until an incident disrupts operations, compromises customer data or damages trust.
Downtime has a cost. So does a security breach.
The goal isn't to avoid every interruption at all costs. It's to make informed decisions that protect both the business and its customers.
Question for DevOps engineers: When a critical vulnerability affects production, how do you balance emergency patching, testing and customer availability?
#DevOps #DevSecOps #CyberSecurity #CloudSecurity #SRE
04 ✨ retweeted
21 years ago I named "Reddit" and everyone said it was a horrible name, but I insisted one day people would say "I read it on reddit" and used my CEO-privilege to overrule everyone + kept the name. Now the company twitter account (unbeknownst to them) is making the joke. Heh.
04 ✨ retweeted
The Prime Minister of Japan is tweeting to apply the PHP fix patch.
WTF.
皆様に、今夜に対応して頂きたい大至急のお願いです。
多くのウェブサイトで使用されているPHPに関し、PHPのセキュリティチームが、重大な２件の脆弱性に関する注意喚起を行っています。
公開しているウェブサイトでPHPを使用しているか確認し、今夜、10月21日午後11時（日本時間）に公開される修正パッチについて、可及的速やかに適用できるよう準備をお願いします。
修正パッチを速やかに適用することが困難な場合は、例えばウェブサイト等を一時的に停止させることも、リスクを低減させるための有効策の一つと考えられます。
国家サイバー統括室のXアカウントでも関係する情報を発信していますので、そちらも参考にして下さい。
国家サイバー統括室(注意・警戒情報)（@cyber_forecast） / X
04 ✨ retweeted
As if PHP2Shell wasn't enough for one day... now GitLab. 😅
🚨 CRITICAL GITLAB ALERT (CVSS 10.0)
CVE-2026-110264 could allow unauthenticated RCE on self-managed GitLab servers.
⚠️ Potentially affects 12 years of releases, dating back to 2014.
Patches available. Update immediately!
docs.gitlab.com/releases/pat…
#gitlab #cybersecurity
04 ✨ retweeted
This is the question every WordPress website owner should be asking: Who is responsible for PHP security updates on my server?
I manage my own server, so that responsibility falls on me.
With PHP’s scheduled security release addressing CVE-2026-109618 and CVE-2026-109619 today, don’t assume updating WordPress core and plugins is enough. Your underlying PHP runtime needs to be patched too.
Know who owns the update. Patch promptly. Verify the fix.
🚨 A PHP zero day drops today.
Two critical flaws (CVE-2026-109618 and CVE-2026-109619) let attackers run code on your server without logging in, and PHP powers around 75% of the web including every WordPress site.
The patch releases at 14:00 UTC, and attacks are expected within minutes of it going live, so message your host or developer NOW and have them ready to update the moment it lands.
Who manages PHP updates on your site? 👇
04 ✨ retweeted
I love relationships with smooth and matured understanding. There's a way your woman will want to fight you with respect and caution and you'll find it romantic, to the extent that you will apologize and make her feel safe.
If this woman had thrown tantrum at her man, matter would have gone out of line. Well, I watched this video severally and I want to watch more.
What do you all think about this little drama between this couple?
04 ✨ retweeted
These Linux commands helped me most in last 13 years of IT career
Daily stuff:
• ps aux | grep {process} - Find that sneaky process
• lsof -i :{port} - Who's hogging that port?
• df -h - The classic "we're out of space" checker
• netstat -tulpn - Network connection detective
• kubectl get pods | grep -i error - K8s trouble finder
Log related commands:
• tail -f /var/log/* - Real-time log watcher
• journalctl -fu service-name - SystemD log stalker
• grep -r "error" . - The error hunter
• zcat access.log.gz | grep "500" - Compressed log ninja
• less +F - The better tail command
Container cli:
• docker ps --format '{{.Names}} {{.Status}}' - Clean status check
• docker stats --no-stream - Quick resource check
• crictl logs {container} - Raw container stories
• docker exec -it - The container backdoor
• podman top - Process peek inside containers
System Detectives:
• htop - System resource storyteller
• iostat -xz 1 - Disk performance poet
• free -h - Memory mystery solver
• vmstat 1 - System vital signs
• dmesg -T | tail - Kernel's recent gossip
Network stuff:
• curl -v - HTTP conversation debugger
• dig +short - Quick DNS lookup
• ss -tunlp - Socket statistics simplified
• iptables -L - Firewall rule reader
• traceroute - Path finder
File and stuff:
• find . -name "*.yaml" -type f - YAML hunter
• rsync -avz - Better file copier
• tar -xvf - The unzipper (yes, we all google this)
• ln -s - Symlink wizard
• chmod +x - Make it executable
Performance:
• strace -p {pid} - System call spy
• tcpdump -i any - Network packet sniffer
• sar -n DEV 1 - Network stats watch
• uptime - Load average at a glance
• top -c - Classic process viewer
Git Essentials:
• git log --oneline - History simplified
• git reset --hard HEAD^ - The "oops" eraser
• git stash - The work hider
• git diff --cached - What's staged?
• git blame - The "who did this?" resolver
Quick Fixes:
• sudo !! - Run last command with sudo
• ctrl+r - Command history search
• history | grep - Command time machine
• alias - Command shortcut maker
• watch - Command repeater
