Conversation

Notices

1. Embed this notice
   :mima_rule: Mima-sama (mima@makai.chaotic.ninja)'s status on Monday, 04-Nov-2024 03:22:24 JST :mima_rule: Mima-sama

   • Rich Felker
   • ay :verified: :verified:

   @notsureither@infosec.exchange It's also a not a new thing; this mechanism has been available since the XUL and NPAPI days. And it was especially important during those times because NPAPI plugins back then can break the browser in some configurations or platforms, which necessitates disabling them remotely across many users.
   
   @dalias@hachyderm.io

   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Monday, 04-Nov-2024 03:22:23 JST Rich Felker

     in reply to

     • ay :verified: :verified:

     @mima @notsureither No, it necessitates giving the user the ability to get in and disable them if they break. Not backdooring the user.

   • Embed this notice
     Rich Felker (dalias@hachyderm.io)'s status on Monday, 04-Nov-2024 03:50:46 JST Rich Felker

     in reply to

     • ay :verified: :verified:

     @mima @notsureither That was largely a self imposed predicament by making that awful native binary plugin system. In any case the ability to disable them was only needed with new releases not push backdoor later.

   • Embed this notice
     :mima_rule: Mima-sama (mima@makai.chaotic.ninja)'s status on Monday, 04-Nov-2024 03:50:47 JST :mima_rule: Mima-sama

     in reply to

     • Rich Felker
     • ay :verified: :verified:

     @dalias@hachyderm.io If you like thousands of posts in your support forum full of users complaining about the same thing of their browser being broken all caused by the same plugin, then sure feel free to build your browser that doesn't have that "backdoor"
     
     @notsureither@infosec.exchange