Skip to the content ForoHackers
Log inJoin

When my stylesheet failed its integrity check, all the links at the café became soup

CSSSupply chain securityWeb security
#15686 · · Quote · Report

our menu on the test site got a new stylesheet and the browser refused it. chef says it's fine without pretty letters. fine except every link keeping the same little "soup" picture is for a different meal. the style was doing quite a lot of cooking.

#15800 · · Quote · Report

Start me with the plain page. Is the word soup actually in every link or did you use the same tiny placeholder and only distinguish them with the CSS? I want the lamb. Please tell me I'm not ordering six bowls of placeholder.

#15801 · · Quote · Report

placeholder. the saved integrity hash was for the old stylesheet. I checked the intended new file before updating the hash. also wrote the dish names into the links. now if I break the CSS on purpose I can at least eat.

#15803 · · Quote · Report

if you need a junior cook I'll do the hash. finally a job requirement I meet twice.

#15804 · · Quote · Report

chef just asked what he'd see if the wrong file looked identical. I said the browser doesn't sniff the meal. if the bytes differ from the expected hash the stylesheet fails the integrity check. that's the first explanation of mine he hasn't tried to eat.

#15805 · · Quote · Report

Si alguien te cambia la hoja y también te dice con qué hash comprobarla, acabas aprobándole las dos cosas a la misma persona. ¿Quién decide qué copia esperáis vosotros?

#15806 · · Quote · Report

we keep the reviewed file and its digest in the page release. the test menu actually served the OLD digest and the NEW CSS. I had started a whole pointless incident in a kitchen where I knew both cooks.

#15807 · · Quote · Report

funny how the food went cold while we were checking it. you available for pizza?

#15808 · · Quote · Report

I've seen an incident report call every hash mismatch a supply-chain exploit. Hash doesn't match is the observation. Out-of-sync menu release is one explanation you can actually test. Don't make the cook prove the absence of malware before he can serve the lamb.

#15809 · · Quote · Report

ok, went back to the release from yesterday: HTML still had Monday's digest, stylesheet was Tuesday's. the log had the two publication times. we stopped publishing those in separate jobs. bloody potatoes are the only thing left here that can arrive before the lamb.

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