p0sql

38.6K posts

p0sql banner
p0sql

p0sql

@p0sql

Cloud Native & Infosec enthusiast in telco world. Let's break things ! Bike Life 🏍️ 🇲🇶 || Some cool stuff :: https://t.co/nhqotQKrrA

France 参加日 Haziran 2011
244 フォロー中369 フォロワー
固定されたツイート
p0sql
p0sql@p0sql·
I currently do analysis of PKU2U protocol which is used by joined clients to Azure AD during an authentification. For my part, this protocol is very interest because we can call it "The Kerberos of Web" lol.
English
2
3
8
0
p0sql
p0sql@p0sql·
@ThisIsJaxxou Qui est l’auteur du livre ? Y’a un lien pour achat ?
Français
1
0
0
607
p0sql がリツイート
vx-underground
vx-underground@vxunderground·
"You penetration test 'em so you simulate the pressure" 🗣️🔥🔥
English
35
260
1.8K
48.7K
p0sql がリツイート
Graham Helton (too much for zblock)
In a few days I will be publishing a guide on how to exploit this RCE to get code execution on any control plane node from a worker node. (without the commands being logged of course). Or you could just steal all the certificates, compromise etcd, and control the cluster.
Graham Helton (too much for zblock) tweet media
Graham Helton (too much for zblock)@GrahamHelton3

Excited to disclose my research allowing RCE in Kubernetes It allows running arbitrary commands in EVERY pod in a cluster using a commonly granted "read only" RBAC permission. This is not logged and and allows for trivial Pod breakout. Unfortunately, this will NOT be patched.

English
2
29
193
18.5K
p0sql がリツイート
Graham Helton (too much for zblock)
Excited to disclose my research allowing RCE in Kubernetes It allows running arbitrary commands in EVERY pod in a cluster using a commonly granted "read only" RBAC permission. This is not logged and and allows for trivial Pod breakout. Unfortunately, this will NOT be patched.
Graham Helton (too much for zblock) tweet media
English
47
377
2.6K
410.6K
p0sql がリツイート
TDM (e/λ) (L8 vibe coder 💫)
Defending my Spring Boot Java app that uses 64GB RAM to return { "status": "ok" }
English
74
740
11.4K
540.8K
p0sql がリツイート
Kubernetes
Kubernetes@kubernetesio·
Ingress NGINX is being retired in March 2026. After this date, no security patches or bugfixes will be issued. Plan your migration to Gateway API or a supported controller now. Read the retirement guide: kubernetes.io/blog/2025/11/1…
English
9
92
458
62.5K
p0sql がリツイート
Branko
Branko@brankopetric00·
Microservices turned a 5-second monolith debug session into a 3-hour distributed tracing archaeology expedition.
English
86
299
5.4K
191.3K
p0sql がリツイート
Vincent Flibustier 👽
Vincent Flibustier 👽@vinceflibustier·
Premier jour à la Poste, fait une petite mise à jour informatique et pris mon après midi
Vincent Flibustier 👽 tweet media
Français
100
335
10.1K
1.5M
p0sql がリツイート
Akhilesh Mishra
Akhilesh Mishra@livingdevops·
Kubernetes is retiring the NGINX Ingress Controller by March 2026. And the internet is having another meltdown. "NGINX is dead!" "Kubernetes is abandoning us!" It's the Docker panic all over again. NGINX, the web server, is completely fine. It powers half the internet and isn't going anywhere. It's the Ingress NGINX controller that is retiring. This is one specific Kubernetes project that uses NGINX under the hood to route external traffic into your cluster. Why is it happening? The Ingress NGINX project has been running on fumes with just one or two people maintaining it in their spare time. Security holes kept showing up. They tried building a replacement and begged for help. Nobody came. So instead of pretending everything’s fine while your clusters are at risk, Kubernetes is being honest and saying, “This thing can’t continue safely, please move on by March 2026.” Unfortunately, even that announcement failed to generate additional interest in helping maintain the project. What should you do? Move to Gateway API. It's more powerful, better maintained, and where the ecosystem is headed. Cloud providers are already adopting it by default. Or switch to another Ingress controller like Traefik or HAProxy. Many support both Ingress and Gateway API, giving you time to migrate properly. You have options. You have time. Don't panic. it This is progress, not the end of the world. Read the full breakdown here: @akhilesh-mishra/nginx-ingress-controller-is-retiring-and-no-nginx-isnt-dying-b67a166b36de" target="_blank" rel="nofollow noopener">medium.com/@akhilesh-mish…
Akhilesh Mishra tweet media
English
19
94
612
65.4K
p0sql がリツイート
bunnysayzz
bunnysayzz@bunnysayzz·
First day in #Cloudflare as system engineer 😍 wish me luck
bunnysayzz tweet media
English
3.4K
25.9K
328.2K
29.5M
p0sql がリツイート
Tom Dörr
Tom Dörr@tom_doerr·
Collection of over 65 tools for blue teaming activities
Tom Dörr tweet media
English
2
35
296
111.1K
p0sql がリツイート
Robert Graham
Robert Graham@robertgraham·
Anybody can run Wireshark and see for themselves how much "Encrypted Client Hello" is supported. It'll work between your Chrome browser and Google, but it's rarely supported otherwise. I'm at a public WiFi and just went to PronHub to demonstrate this. It's TLSv1.3, which supports ECH in theory, but not practice. The website name is right there in the packets. In other news, it appears the site is block in the state of Georgia due to age verification laws. This is probably why people actually use VPN, to make it appear they live in a different state. BTW, you don't have to trust me because I'm an expert (though I am), but because I show data.
Robert Graham tweet mediaRobert Graham tweet media
Dave W Plummer@davepl1968

@BuckedUnicorn As an expert, then, I defer to you to show me how any of this is false on an ecrypted DNS channel like 1.1.1.1 that supports ECH. Maybe "expert" is too strong a word, then? Or perhaps a little knowledge is a dangerous thing.

English
47
104
1.6K
333.1K
p0sql がリツイート
Steve the Beaver
Steve the Beaver@beaversteever·
"after 11 technical interviews" "your work has been accepted into our codebase" interviews are getting out of hand
Steve the Beaver tweet media
English
3.7K
4.4K
73.2K
7.1M