Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I am looking for a way to set up Google Chrome so that it will run a certain plug-in (Java, what else?) only on whitelisted sites, but other plug-ins (like the PDF viewer) everywhere.

From playing with the policies available for Chrome, I think there are basically two levels of plug-in management:

  • List of disabled plugins/enabled plugins: Controls whether a plug-in exists for the browser at all

    This pair of policies applies to plug-ins, but not to sites.

  • Default plug-in settings/Allow plug-ins on sites: Controls on which sites plug-ins can run

    This set of policies applies to sites, but not to individual plugins, and it cannot override the first pair.

There appears to be no way to configure Chrome so that some plug-ins only run on whitelisted sites, but others run everywhere by default.

I have also looked at filtering content on the firewall/proxy level, but I'm not convinced it can be done securely there. Filtering by URLs (file names) or content types can be circumvented trivially, and identification by content inspection cannot be safe either.

share|improve this question

migrated from serverfault.com Aug 31 '12 at 12:47

This question came from our site for professional system and network administrators.

    
You're asking for a level of control that Chrome is not designed to provide. –  John Gardeniers Aug 31 '12 at 7:18
add comment

3 Answers

The Google Chrome add-on Extension Automation lets you decide on which websites you want an extension to work on, and on which it should be disabled.

Extension Automation makes it easier to manage other extensions by automatically enabling
or disabling them based on the webpages you visit. This extension helps reduce the visual
clutter of other extensions and keeps them from running unnecessarily in the background.

Or you can use this Automatically Enable Incognito Mode For Specific Websites method.

share|improve this answer
    
Perfect in principle, but, alas, it only controls extensions, not plugins. –  Christian Feb 18 '13 at 14:12
add comment

Have a look at ScriptNo. It's very much like a port of the famous Firefox Add-on NoScript.

Basically, by default it blocks all scripts and <OBJECT>, <EMBED>, etc. unless you explicitly allow it.

See also:

share|improve this answer
    
Thanks for the tip, but ScriptNo's also an all-or-nothing thing. –  Christian Sep 2 '12 at 16:23
add comment

Issue 155743 on the Chromium tracker is open for this. Star it if it matches your needs.

I'll try to come back and update this post if the feature gets implemented (but if you notice I haven't, comment below)

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.