|Installing chrome extension on windows in the future||ludovic paquet||11/8/13 12:39 AM|
As regards these changes ("Protecting Windows users from malicious extensions"), will it be possible (like today) to drag'n drop crx extension for installing them ?
|Re: Installing chrome extension on windows in the future||Tim Robinson||11/8/13 1:30 AM|
I'm assuming not.
What a shambles - It looks like a lot of my corporate customers will have no choice but to go back to "good old" Internet Explorer :-( I didn't think I'd ever be saying that.
|Re: Installing chrome extension on windows in the future||RichardS||11/8/13 1:51 AM|
I hope the drag and drop option is retained (even with the use of a flag). We have an internal extension that contains private information that we would not put in the Chrome Web Store. Our internal users simply drag and drop our crx to install at the moment in their stable channel browsers.
I can understand stopping silent installation for consumers but what I have described is a very common use case in business.
|Re: Installing chrome extension on windows in the future||Tim Robinson||11/8/13 2:16 AM|
I hope so too but I suspect we're hoping in vain. As far as I'm aware they have already changed it so that extensions not from the app store have to be explicitly dragged and dropped. If they were keeping the same behaviour there would be no need for this announcement.
|Re: Installing chrome extension on windows in the future||RichardS||11/8/13 2:33 AM|
The announcement suggests they are targeting bundled extension installed through this mechanism: http://developer.chrome.com/extensions/external_extensions.html
This is different to the drag and drop mechanism which an additional step the average user would not use. Some clarity from Google would be good here.
|Re: [crx] Re: Installing chrome extension on windows in the future||David Mohl||11/8/13 5:16 AM|
What I got from the message is, that you have to activate developer mode first before being able to drag and drop (a.k.a. tick the small box and put chrome into developer mode).
Would love some verification on this
|Re: [crx] Re: Installing chrome extension on windows in the future||Antony Sargent||11/8/13 3:27 PM|
Unfortunately the bad actors we've seen in the wild have been writing the chrome preferences file (after killing running instances of chrome) and/or modifying shortcuts to insert command-line flags. So anything we could write into your chrome preferences to say "they manually installed this via drag and drop", the bad actors can just write. (In fact we've found that many already do something very much like this today, to bypass the "users must opt in" protections we added a while back - they just set the "this user said yes to that dialog" flag to true).
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/etPan.527ce43e.acc2ae2.bf%40Davibook.local.
|Re: [crx] Re: Installing chrome extension on windows in the future||David Mohl||11/8/13 5:45 PM|
Thanks for clearing this up Antony.
Since I am maintaining a popular (300k) non-webstore extension right now that got kicked out of the webstore, this is affecting me and my userbase pretty strong.
Pushing my addon back to the webstore listing will very likely not work. Would pushing it as a private addon be an option for us non-webstore-devs? Since only users with the URL would be able to find the extension.
Or does this change indeed require us to publish a manual how to load a unpacked extension into chrome? This case would have an huge impact and basically killing off all non-webstore extensions that are targeting non-tech users. Imagine advising every user to go to github and download a zip from your source code (or is this what google wants? Webstore or nothing?)
|Re: [crx] Re: Installing chrome extension on windows in the future||Antony Sargent||11/11/13 9:26 AM|
Sorry this change will negatively impact you! If for some reason your extension actually does comply with the webstore's program policies / terms of service and it was removed in error, you can start a new thread at http://groups.google.com/a/chromium.org/group/chromium-apps/ and our developer relations folks may be able to help get things straightened out. Also, it's worth reiterating that these restrictions only apply to extensions, not apps, and only on windows stable/beta channel.
Assuming none of the above helps, you can notify your users of the options they have for running extensions not hosted in the webstore:
-Use any verison of chrome on mac or linux, where we are not enforcing these restrictions
-On Windows, install the canary channel alongside the existing stable/beta install (since canary can co-exist and uses a different profile directory), or replace chrome stable/beta with the dev channel.
-Users who are very technical could even build their own copy of chromium from the open source repository, or download one of the continuous builds). This isn't a good option in general since you don't get autoupdates and would need to keep it up to date yourself, but I include it for completeness.
We don't recommend trying to have people run the extension unpacked in developer mode, because we will be adding UI safeguards to steer regular users away from this, and if we find abuse by some of the same bad actors who have been force installing extensions to date we may need to start flagging extensions that push developer mode on users as malware.