3 ms·
Wow props to System76 for coming clean about this despite the fear of a huge public shaming/backlash from a disclosure like this. Although they took a decision
by cssanchez 3y ago
Wow props to System76 for coming clean about this despite the fear of a huge public shaming/backlash from a disclosure like this. Although they took a decision of switching from SSR to SSG as a result, they shouldn’t think that really fixes vulnerabilities in the future. I believe SSG is overall the ‘less secure’ of the two, but no tech stack is perfect and its mostly a matter of use case and performance, not security that should be the decisive factor. At least it wasn’t another Wordpress or PHP breach.
- neohed 3y agoI agree. Just blindly moving from SSR to SSG sounds like it could potentially make things even worse. Especially considering that the breach seems to be due to some interplay between their caching layer and SSR.
- solarkraft 3y agoWhy? With SSG there's no chance of a state change happening without you knowing, so they may be able to do some QC (see automated scans) before release and be confident it won't change afterwards.