I’m frustrated

My Company's Internet Security Policy Blocks Ghostery Updates

Our company's security policy blocks Ghostery's ability to retrieve updates. Ironically the reason for this is the actual content of the update itself. I noticed in the page source from which the updates are retrieved is plaintext HTML so our policy will not permit access to the data. Is there an alternate method of updating the bugslist to keep this from happening? I work for a large bureaucratic organization, so asking them to make an exception just for Ghostery is out of the question.
1 person has
this question
+1
Reply
  • Hi john, thanks for using Ghostery.

    Does this mean that your company prevents you from going to http://www.ghostery.com/remote/update? You could manually navigate to this page once a week, and that will update Ghostery. If you cannot reach that website, we'll need to think of something else, but its possible to manually update Ghostery as well: the bugs database is just a set of 2 files sitting in your extensions folder. Let me know if the first method works, and If it doesn't, I'll outline what you need to do for manual updates.
    • If the company is using Deep Packet Inspection, you're SOL unless the security administrator is willing to make an exception. It's a reasonable request.

      As for "something else," it's called SSL. I'll leave it to you [Felix] to determine whether that's best handled by EC2, EdgeSuite Secure Content Delivery, or another channel entirely.

      The reason there isn't a problem until Ghostery tries to fetch bug lists is that each Ghostery release is "seeded" with chrome://ghostery/content/ghostery-bugs.js and chrome://ghostery/content/ghostery-lsos.js — which AMO delivers using SSL.

  • (some HTML allowed)
    How does this make you feel?
    Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated