Skip to the content ForoHackers
Log inJoin

The kiosk serves NGINX. Is it even the ingress-nginx controller in yesterday's notice?

Cloud securityIncident responseOpen source
#18579 · · Quote · Report

Yesterday's Kubernetes notice. Studio kiosk's inventory says NGINX. Cluster owner says ingress-nginx. The office whiteboard has merged these into a creature called ALL THE NGINX, against which our marker pens have already failed.

#18945 · · Quote · Report

Name the component in the CVE notice. A standalone web server on the kiosk isn't evidence of that Kubernetes controller. Who can read the actual deployed workload inventory for the cluster?

#18946 · · Quote · Report

owner reviewed our authorised inventory. kiosk is the standalone server in this setup. cluster does run the community ingress-nginx controller, so they checked its actual version against the advisory. two distinct records; kiosk still has its normal web-server update responsibility.

#18947 · · Quote · Report

Notice gives fixes v1.11.5 and v1.12.1 on the two branches. Don't mark the separate kiosk affected just because someone scratched "NGINX" into its lunchbox.

#18948 · · Quote · Report

cluster owner put the appropriate fixed release into the planned update and verified the running controller build afterward. no test against a live service needed to establish which software the team deployed. the lunchbox has been referred to catering.

#18954 · · Quote · Report

y que el papel diga quién cotejó la versión después. si el que pinta el punto verde sólo vio el correo que pedía el parche, el viernes vais a volver a bautizar un rotulador.

#18955 · · Quote · Report

two signoffs: change request and post-update inventory. our render queue remained somebody else's boring but lovely job throughout. ALL THE NGINX has been rubbed off except for one antler.

#18988 · · Quote · Report

I read the title as a warning about the wee NGINX sticker on my own lunchbox and got all the way down to the version number before noticing the dates don't match. God help the blue team if I ever join.

You are not logged in, so this goes up anonymously: no account, no name and no address is stored with it, and it may carry no link and no image. Log in or join to post under your name. Our web server's logs keep the address and time of every request for up to 14 days; to keep yours out of them, use Tor. To reach the staff in confidence, use the drop. Sign as a returning source (a key kept only in this browser)

Sending takes a few seconds here: your browser first works out a proof of work against spam.

Reply