(07-02-2015, 07:56 PM)reactor Wrote: thank you. Great!
1
clear browsing data on exit = not working ( Cannot remove URL history )
2
Webrtc not fully blocking
http://www.browserleaks.com/webrtc
Audio Context true
RTP-based Data Channels true
SCTP-based Data Channels true
For question 1, I want to clarify what uncleared is autocomplete URL not history URL.They are similar but not the same things.
It is my mistake that I didn't treat this as a bug.Will fix it in the next version.
For question 2, I have spent half a day to carefully research your concern.And I can assure you that you are 100% safe against webrtc leaks while you checked the "Disable WebRTC" options.
There are more reasons.Firstly the testing page tests audio context and data channels simply by javascript code like this:
var rtc_isAudioContextSupported = !! window.AudioContext || !!window.webkitAudioContext;
var rtc_isScreenCapturingSupported = h && 26 <= m && (u ? !0 : "https:" == location.protocol);
var rtc_isSctpDataChannelsSupported = !! navigator.mozGetUserMedia || h && 25 <= m;
The results are true just means these javascript objects are existed, but not means they can really work.In fact javascript objects can be created at anytime anywhere.
Secondly the audio context and data channels can't work independently, they are part of webrtc and rely on webrtc.If webrtc is disabled, nothing related can actually work.
At last I want to tell you this kind of security warnings may scare the average users, but in most cases things are not that serious.