{"id":27863,"date":"2020-01-14T20:22:00","date_gmt":"2020-01-15T01:22:00","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=27863"},"modified":"2022-07-14T15:05:19","modified_gmt":"2022-07-14T19:05:19","slug":"the-security-of-safari-extensions","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2020\/01\/14\/the-security-of-safari-extensions\/","title":{"rendered":"The Security of Safari Extensions"},"content":{"rendered":"

Jeff Johnson<\/a>:<\/p>\n

\n

Every Safari extension that runs JavaScript — in other words, almost every Safari extension — will have these same warnings, so what are users supposed to do with the warnings? Avoid Safari extensions entirely? Then why does Apple provide a developer API for Safari extensions, if they aren’t meant to be used? Why are Safari extensions available in the Mac App Store? Why does Apple advertise that they’re available in the Mac App Store? You get the feeling that different teams within Apple are not on the same page here, and they’re giving unhelpful mixed messages to users.<\/p>\n

[…]<\/p>\n

In general, my view is that you shouldn’t install software on your Mac unless you trust the developer. You can’t rely on the system to protect you from malicious software, because there are always vulnerabilities and ways to get around the system.<\/p>\n<\/blockquote>\n

It’s a recurring theme. Without the scary warning, Apple gets blamed for any problems. With the warning, developers blame Apple for scaring customers away from their products, and if anything bad happens everyone blames the customer for ignoring the warning that they had no way to evaluate.<\/p>\n\n

Previously:<\/p>\n