User: Password:
|
|
Subscribe / Log in / New account

Why a different distribution mechanism

Why a different distribution mechanism

Posted Sep 22, 2011 23:01 UTC (Thu) by droundy (subscriber, #4559)
In reply to: Why a different distribution mechanism by otaylor
Parent article: Managing GNOME shell extensions

Actually, the version requirements sounds like a strong argument in favor of using the existing distribution infrastructure. That and the security question are sufficient for me to hope that when this is released in Debian stable any integration with browsers allowing remote code to take control of my desktop will be disabled by default.


(Log in to post comments)

Why a different distribution mechanism

Posted Sep 23, 2011 17:13 UTC (Fri) by otaylor (subscriber, #4190) [Link]

Want to be clear about "allowing remote code to take control of my desktop" - what happens is that when you click on the website to install an extension, this triggers the downloading code (not in the same process as the browser plugin) to put up a dialog asking if you want to download and install an extension. So, if you consider a MIME-type helper secure, you shouldn't be too afraid of this. The advantage of a plugin, beyond slickness, is that we can do additional security checks to avoid users being tricked by arbitrary websites into installing extensions. Debian of course, is free to package the browser plugin as a separate subpackage.


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds