MarcellusDrum@lemmy.mlM to Linux@lemmy.mlEnglish · 21 hours agoThe king is backlemmy.mlimagemessage-square53linkfedilinkarrow-up1316arrow-down19
arrow-up1307arrow-down1imageThe king is backlemmy.mlMarcellusDrum@lemmy.mlM to Linux@lemmy.mlEnglish · 21 hours agomessage-square53linkfedilink
minus-squareredrum@lemmy.mllinkfedilinkarrow-up6·4 hours agoIf that server includes the security repository in its source files, I disagree. In fact, the use of the security repository in Debian has a history spanning more than 20 years.
minus-squareNalivai@lemmy.worldlinkfedilinkarrow-up1arrow-down3·4 hours agoUntil some fucking php vulnerability grants root access
minus-squareredrum@lemmy.mllinkfedilinkarrow-up2·3 hours agoIf you are speaking about the latest php bug, debian stable and old stable were updated days ago, see https://security-tracker.debian.org/
minus-squareCommanderCloon@lemmy.mllinkfedilinkarrow-up1·3 hours agoit might be a failure to read on my part but this reads as unfixed on Debian but fixed on Arch Edit: Oh, yeah ok, in the security repo it’s fixed, why is the vulnerable version distributed to stable though?
minus-squarefurry toaster@lemmy.blahaj.zonelinkfedilinkEnglisharrow-up2·3 hours agowould arch have fixed this? no, what is your point?
If that server includes the security repository in its source files, I disagree. In fact, the use of the security repository in Debian has a history spanning more than 20 years.
Until some fucking php vulnerability grants root access
If you are speaking about the latest php bug, debian stable and old stable were updated days ago, see https://security-tracker.debian.org/
it might be a failure to read on my part but this reads as unfixed on Debian but fixed on Arch
Edit: Oh, yeah ok, in the security repo it’s fixed, why is the vulnerable version distributed to stable though?
would arch have fixed this? no, what is your point?