PrivDog Connections

Discontinued Products News / Announcements / Feedback - PrivDog
1

  1. Would there be any disadvantage to PrivDog using HTTPS: for its transactions with AdTrustMedia ?
    ( Instead of HTTP: )

  2. Flip side of this question = Would there be any Privacy advantage to be gained for End Users if PrivDog used HTTPS: ?


http://s1.bild.me/bilder/260513/thumb_7609553Untitled.jpg

Edit : Also for anyone elses use this topic to include issues / concerns / suggestions for change to how PrivDog extension Communicates with AdTrustMedia ( and any related ideas ).

2

Hi,

To answer your questions.

  1. The disadvantage for Adtrustmedia would be increased load on the servers.
  2. With HTTPS there is a potential to prevent man in the middle attack vectors.

We’ll consider adding it after the current upgrade to handle the high load.

Shane.

3

Which strengthens the goals of PrivDog

We'll consider adding it after the current upgrade to handle the high load.

:-TU Thank you :wink:

4

yes actually pushing all the ads thru https will eliminate the MITM attack vectors…nice…

5

And use SPDY.

6

Is it Possible to have a page on this forum under Privdog for all the sites that need to be Blocked.

I.E. The Site that have a lot of counters I.E. Over 9 or whatever you think ?

So that the Comodo staff that look after Privdog can go straight to the page and get the ads to block, than looking all around the forum for them.

So what do you think

Regards

Nigel

7

Maybe add a feature “Report” - you can report any element on a website which you consider not detected and blocked.

8

Yeah something like that morphiusz but I guess that will come up in later builds ?

9

Off topic but do you two know about the PrivDog Wish List child forum https://forums.comodo.com/wishlist-privdog-b307.0/

There is also the Ads that need to be blocked section https://forums.comodo.com/ads-that-needs-to-be-blocked-b308.0/

… I am pretty sure what you are looking for being added, already has a wish topic. If not … make one.

The purpose of this topic ( though not clearly defined ) should be evident just by the topic title and the content of the first post - How PrivDog extension Communicates with AdTrustMedia ( and any related ideas ).

10

.
Noticed that PrivDog is now using some HTTPS connections …

Using ://ad as a filter on chrome://net-internals/ - Events


http://s1.bild.me/bilder/260513/thumb_5222482Untitled1.jpg

( in fact I think you started implementing this within a week of me posting this topic )

I have been watching it since, and consistently see results similar to the above screenshot …

Whereby there is a mixture of similar events in both HTTP: and HTTPS:

Is this intended ? - Or are you just keeping legacy connection methods as a fall back in case HTTPS: is problematic in some cases ?