mancalled.horse
Cats! feed enjoyer. Distributor of likes. (he/him) PFP: a little baby octopus Banner: "I'm doing my part!"
👤 Joined on 19 August 2023
Followers
Following
Total Posts
@johnchivall.bsky.social@johnchivall.bsky.social → @mancalledhorse.bsky.social@mancalledhorse.bsky.social → @mancalledhorse.eurosky.social@mancalledhorse.eurosky.social → @mancalled.horsearpixa.bsky.social
ra030e5.bsku.social
grgrfrlmkkmj.bsky.social
99montez34.bsky.social
vistarian.bsky.social
ntb-of-earth.bsky.social
Not Found
coolxenu.bsky.social
cancelled-by-elon.bsky.social
epicthundercat.bsky.social
mattstern.bsky.social
newtometoo.bsky.social
w2u0b2b5.bsky.social
Not Found
umlegacypress.com
freespeechuk.bsky.social
zululima9.bsky.social
sundodger97.bsky.social
antifunkaf.bsky.social
craigmurrayorg.bsky.social
Not Found
allitude.bsky.social
saemg.bsky.social
darrenharingey.bsky.social
gravitywavematt.bsky.social
the hilarity of "we used a private key of 4" is starting to really sink in now and i am besides myself with laughter
Show Post4. fucking 4. i’m doing incident response because of the number fucking 4.
Show Postactually, 4 is a very hard to guess number, and is secure from modern attacks
Show Postto be clear the reason this is not a patch is because this mega-vuln is actually TWO mega-CVEs and this only "resolves" one of them (i think). we still have to wait and see for full detais but... yeah
Show Postthere is a one-liner mitigation available ( session.upload_progress.enabled = 0 ) but THIS IS NOT A FIX and PHP developers have said it. IT DOES NOT RESOLVE THE ISSUE, YOU ARE STILL VULNERABLE. the only permanent solution is to patch, and EOL'd PHP versions might not receive the patch
Show Post