Feature Request Version 6

[Johnathonm]

Hi,

Is it possible to incorporate something similar to HTTPS Everywhere in version 6? It's a great tool and would be nice to be able to have all security in one place.

Thanks for listening.

J

 

[randomusername]

Adguard is not primarily intended to be a security tool.

 

[vasily_bagirov]

Hi,

Is it possible to incorporate something similar to HTTPS Everywhere in version 6? It's a great tool and would be nice to be able to have all security in one place.

Adguard won't make every website use HTTPS, at least in the forseable future. We believe that Stealth Mode module is enough for now.

 

[avatar]

Adguard won't make every website use HTTPS, at least in the forseable future. We believe that Stealth Mode module is enough for now.

HTTPS everywhere is a bit different thing, why do you compare them?

@Johnathonm, it is a bit out of scope for Adguard. I think it's possible to make a userscript which can be used then in Adguard, but anyway it won't be as good as HTTPS everywhere.

 

[Johnathonm]

Thanks Avatar - Another question

Another question,

Is it possible for AdGuard to block WebRTC requests? That seems to be a nightmare and requires additional plugin's or editing for both FireFox and Chrome.

Just thought I'd ask.

Thanks in advance.

Johnathon

 

[avatar]

We've discussed this recently:
http://forum.adguard.com/showthread.php?6043-Block-WebRTC-IP-address-leaks

There is no such function out of the box.

For now you can do it manually by adding this rule to the user filter:

#%#window.webkitRTCPeerConnection = undefined; window.mozRTCPeerConnection = undefined; navigator.mozGetUserMedia = undefined; navigator.webkitGetUserMedia = undefined; window.MediaStreamTrack = undefined; window.AudioContext = undefined; window.webkitAudioContext = undefined; window.RTCPeerConnection = function() {};

 

[Johnathonm]

Thanks for including that in Version 6! You guys rock as always.

 

[avatar]

Thanks for including that in Version 6! You guys rock as always.

Thanks Btw, the feature is extended in v6. We are blocking WebRTC on the network level (not just with faking JS objects).

I am proud to say this the only stable way to block it in Chrome.

 

[Boo Berry]

Which is useful as I'm beginning to think I should start to use a VPN when browsing. I found a nice (logless) VPN service that offers IPv6 tunneling called Mullvad that I'm interested in trying.