/what/ - ...

Yo real whatmin I tried upgrading PHP on the server cause of the exploit and you have some third party "sury-php" repo or something causing a gpg key error idk wtf you did

Maybe you want to fix it or just let everyone pwn this site, Whatever

>>6950
doesn't the update release at 14:00 UTC?

>and you have some third party "sury-php" repo or something causing a gpg key error idk wtf you did
yeah i don't remember what i did either, i'm going to bed now i'll take a look at it after i wake up..

>>6951
I should probably do it, it would consist of finding out what you installed from this third party repo and then installing the normal official packages.

>>6952
iirc i think might've added the repo to match whatever was the recommended php version on the vichan github that time which might be 7 4 because the official repos were too new? i also installed mbstring, php-gd and php-pdo
i wonder if vichan will even work on a newer php version, seems like 8 2 is the oldest one that will be getting patched

I will probably fuck it up, do it yourself if you want

perl imageboards and textboards are winning btw

>>6955
w2ch guy here, what I was going to say.

What's the problem? Just never update lol

PHP updated to a confirmed fixed version and everything is working fine.

I ssh'd in to deal with the Debian package mess earlier today and saw you were in there doing stuff, I found communicating with Unix wall command to be hilarious

4chan and a bunch of other sites still down

nothingburger

>>6968
Look at all those males in her discord DMs. Bet she talks with all of them.

>>6968
imagine being this much of a cuck

>>6968
yeah.. i first realised you were ssh-ed in when apache started restarting on its own after i stopped it while i was trying and failing to get sriracha to run in docker, which is what i wasted the most time on

upgrading debian in comparison was actually very straightforward, it just worked, just had to manually install the php related extensions vichan depends on in the end

i re-enabled apache to autostart because i disabled it and removed docker just now, i also installed unattended-upgrades because why not

regarding your comment you made on running vichan and patching it yourself for new php releases using ai, wouldn't it be nicer if the board software was maintained by someone who can actually code or at the very least the software wasn't using php? sriracha does support migrations from vichan btw but i never really tested it so who knows how it works

like, debian 12 is already LTS and gonna be completely EOL in two years which means a bump to php 8 4 when you upgrade to trixie, but on the other hand maybe it doesn't really matter, it's not like this is a bank site

anyway, so what is the actual plain english possible ramification of this vulnerability?
"difficult in practice" does not seem really scary

wow, not even critical..

php and go is bloat we should go back to c

holy c