Not really. They don't put their evil changes in the release notes.
So unless you're willing to read through the source code changes, you're just having an outdated version (with potential compatibility/security issues) for no real benefit.
c/cybersecurity is a community centered on the cybersecurity and information security profession. You can come here to discuss news, post something interesting, or just chat with others.
THE RULES
Instance Rules
Community Rules
If you ask someone to hack your "friends" socials you're just going to get banned so don't do that.
Learn about hacking
Other security-related communities [email protected] [email protected] [email protected] [email protected] [email protected] [email protected] [email protected]
Notable mention to [email protected]
Not really. They don't put their evil changes in the release notes.
So unless you're willing to read through the source code changes, you're just having an outdated version (with potential compatibility/security issues) for no real benefit.
My idea is that if I stay on the oldest supported version for as long as possible, that would help me avoid evil changes in new versions, since the news would have gone public before I update. You bring up a good point about security updates tho. How relevant is it to browser extensions? Has there been malware out there that specifically targets vulnerabilities in extensions? Just casually doing git log | grep -E 'vuln|crit|secur|bug'
in two extensions that I use quite extensively (pun intended), I don't seem to find any security-related commits.
Most security fixes come from updating dependencies, which probably wouldn't mention those in the commit messages, since they can be looked up in the release notes of those libraries.