Loading Profile...
Twitter,
Facebook, or email.
Please provide a secure (https) page for updating bug lists.
Please provide a secure (https) page for updating bug lists.
Promoted
Response
-
HTTPS for updates is now enabled for current dev release of Ghostery v2.7 for Firefox. All future releases of various Ghosteries will use the secure channel.
CHAMP
-
Hi My Name, thanks for using Ghostery.
This is currently in plans, and will be deployed in the next several month.Comment -
-
I’m
silly
please confirm this is still being deployed, or has it been? :) -
-
I can see why it might take a while to implement this. Simply wrapping https around the current mechanism wouldn't scale well. If the goal is simply to protect against man-in-the-middle attacks, snapshots could be versioned and hashed, then distributed via unsecured HTTP (more or less the way AMO works now). This preserves the ability to use web acceleration and client-side caching technologies. If the goal is total end-to-end security, the costs involved might necessitate only offering this through some sort of paid subscription. I don't think anyone wants to open that particular can of worms.
-
Ghostery for Firefox v2.6, which was released two months after I posted this, introduced the use of versioned bug lists as a way to improve GhostRank's efficiency.
Even though this topic has been dormant for some time, that doesn't mean no progress is being made. (It's just not happening all at once.)
-
-
-
-
-
HTTPS for updates is now enabled for current dev release of Ghostery v2.7 for Firefox. All future releases of various Ghosteries will use the secure channel.
-
CHAMP
