i'm not getting paid for this shit, i strongly believe "responsible" disclosure is a fucked up concept, and slopgenerators have made computers deeply unfun recently, so fuck it all.
disable http2 in your nginx instances
good luck, have fun
i'm not getting paid for this shit, i strongly believe "responsible" disclosure is a fucked up concept, and slopgenerators have made computers deeply unfun recently, so fuck it all.
disable http2 in your nginx instances
good luck, have fun
@ar HTTP should never have gone past 1.1.
@dalias@hachyderm.io don't worry, HTTP 1.1 is also insecure
@goat7658 Whole page is bullshit.
@ar .... what did I miss?
( asking as I've been looking without success )
@aaron it's not yet public
@ar I asked in part as it would explain some ... things that have taken over my time today.
Sorry for my lack of reading comprehension, it's been lots of "Oh no shut that off RIGHT NOW as well" today
@ar sudo sed -i -e 's|http2 on\;|\#http2 on\;|g' /etc/nginx/sites-available/*
@swirly except "responsible" disclosure only cares about big vendors and corporations, not people's servers.
@swirly they aren't the only ones, but that way they get treated exactly like everyone else. no preferential treatment.
@swirly exactly, *everyone*
big vendors don't get preferential treatment with full disclosure. arguably this is even better for regular people, as everyone will be busy probing big vendors infra that can be more interesting than what regular people have
@swirly @ar 'responsible' (coordinated) disclosure has always been a tenuous standoff and concession, and full disclosure has always been the stick to force corporations into doing their part
when the corporate world starts lackadaisically wrecking the commons and breaking social contracts, it is not surprising that we're going back to full disclosure
you break the fragile agreement of mutual good faith inherent in coordinated disclosure, you get people saying "fuck it" and just dropping 0days
and arguing about how it's "reckless" (is it? as that's *quite* a bit more complicated than it's painted here) is a mostly pointless endeavour in that context
@joepie91 @swirly @ar
I totally agree that trad responsible disclosure practices tend to just prioritize the corpos.
But a flippant post on mastodon isn't an equitable way to distribute the info either, it prioritizes people who are On Here and know+trust the OP. It's not the same as like "doing full disclosure as a protest meant for political impact", that would require preparation and organizing to make sure that corporations face the majority of the effects.
Like I don't actually care about this that much, im not the "disclosure cops", just thought that was worth saying
@ar do you know offhand a way to verify that it's off?
@ar and to answer my own question, `curl -v --http2-prior-knowledge https://example.com` will error out if http2 is not supported.
@ar I've been linked this post from elsewhere. I have no idea who you are and I'd like to have something besides a vague statement on social media to back me up before I start pulling the proverbial fire alarm.
@lily i explained elsewhere why i dislike delayed disclosures, and i got asked about certain (unavoidably public) commits of mine to public repos before posting this, so 🤷
@ar i dont think i have it even turned on, on the few public facing servces i host, i dont think its on by default
@ameoverflow it's not on by default in upstream nginx, but it's often enabled by admins/users