“If M&S did security research, the Project Zero team would be the calibre of hackers it employed”

@happygeek

Following on from my “privacy triumvirate” column last month, I’m sticking with the browser theme. Not just from the privacy perspective but [best Cilla voice on] surprise, surprise, the security angle as well. As canny readers have already pointed out, using Brave is like using Chrome as both are powered by the exact same Chromium engine. Canny, but not completely correct.

Sure, Brave, Microsoft Edge, Opera and Vivaldi all use the same underlying Chromium engine, but the bodywork and specs are quite different. Brave chooses to be privacy-focused, and that’s why I like it so much. However, it’s true that if vulnerabilities are found in Chromium then they impact users of all browsers built around it. This is important, not least as that means disclosure and patch release cycles are most often out of sync.

Google will push out an update for Chrome at the same time that it discloses the vulnerability or vulnerabilities being fixed. The technical depth to which these disclosures run varies considerably and will depend on many factors, including whether it’s a zero-day with active