pc issue WebRTC IP leak again

[Galileusz]

@BugSir006 About eight months ago I wrote about problems with WebRTC IP leak. And so it looks today:

                             

Unfortunately, this has not been fixed yet. It is a pity because in this case Maxthon 5 is not suitable for safe use. I currently use version 4.4.8.2000 which does not have this problem. But since this version is no longer being developed, I will probably have to look for another alternative than Maxthon.

[BugSir006]

Hi Mr.G, I searched the topic of WebRTC IP leak on the internet again, and most media said it's a loophole on webRTC around two year ago, and it affects chromium based browsers under windows system. So maybe the most effective method to solve this problem maybe for WebRTC to fix it.

You can try this site (https://ipleak.net/) on your different browsers to see if it shows your IP address. I'm using a VPN, and it shows my real IP on Chrome, MX4 and MX5.

And you can solve it by installing this extension: https://chrome.google.com/webstore/detail/scriptsafe/oiigbmnaadbkfbmpbfijlflahbdbdgdf?hl=en

So the problem now is that maybe Maxthon needs an extension like this. How about we contacting the builder of this extension and ask that if he/she could build one for MX as well? I believe you can find his contact info here: https://www.andryou.com/

I'll also let our PM know this, and assess the severe level of it.

[Galileusz]

On Friday, April 21, 2017 at 4:14 AM, BugSir006 said:

Hi Mr.G, I searched the topic of WebRTC IP leak on the internet again, and most media said it's a loophole on webRTC around two year ago, and it affects chromium based browsers under windows system. So maybe the most effective method to solve this problem maybe for WebRTC to fix it.

@BugSir006  I know that this loophole exists for a long time but in most browsers it can be remedied. In Maxthon, there is unfortunately no option to disable WebRTC, nor there is no an extension to remedy it.

Quote

You can try this site (https://ipleak.net/) on your different browsers to see if it shows your IP address. I'm using a VPN, and it shows my real IP on Chrome, MX4 and MX5.

Yes, I did a test on different browsers using at the same time NordVPN. Here are the results:

Maxthon 5 

 

Maxthon 4 

 

Comodo Dragon & ScriptSafe 

 

FireFox with Disable WebRTC option  

 

FireFox without plugins 

 

Cent Browser, UnGoogled Chromium, CyberFox, Vivaldi, K-Meleon and SlimJet without plugins !!! 

Quote

And you can solve it by installing this extension: https://chrome.google.com/webstore/detail/scriptsafe/oiigbmnaadbkfbmpbfijlflahbdbdgdf?hl=en

 Namely, how would I install this extension in Maxthon?

Quote

So the problem now is that maybe Maxthon needs an extension like this. How about we contacting the builder of this extension and ask that if he/she could build one for MX as well? I believe you can find his contact info here: https://www.andryou.com/

Yes, Maxthon needs an extension with similar action. The scriptsafe you suggested I translated into Polish and I sent to Andrew. In my email, I have sent also a question, whether it possible to adapt the ScriptSafe for Maxthon browser. If I get an answer then I will write you about it.

Quote

I'll also let our PM know this, and assess the severe level of it.

This is too serious a matter to neglect this.

[Galileusz]

@BugSir006  Did you see the tests which I inserted above. Any conclusions?

[BugSir006]

Hi G, I just saw your reply, sorry for the late.

So the difference is that in MX5, this part it what missed by other browsers? And this is the leak part which you care about, your real IP addresses?

All others, including MX4, don't have this issue according to your test? And you also don't have the extension for MX4.

So the conclusion you want me to draw is that Maxthon5 can avoid the leak just like MX4? which I also believe in haha.

On 4/27/2017 at 8:44 PM, Galileusz said:

Yes, Maxthon needs an extension with similar action. The scriptsafe you suggested I translated into Polish and I sent to Andrew. In my email, I have sent also a question, whether it possible to adapt the ScriptSafe for Maxthon browser. If I get an answer then I will write you about it.

 

Thanks for the reaching out for Maxthon browser, we are waiting for some good news.

 

On 4/27/2017 at 8:44 PM, Galileusz said:

This is too serious a matter to neglect this.

They seem to be too busy to handle this and haven't figure our what's the difference between MX5 and MX4 for this part last time I report this issue to them, 

But I'll reinforce the importance of this issue with them face to face this time!

[Galileusz]

5 minutes ago, BugSir006 said:

So the difference is that in MX5, this part it what missed by other browsers? And this is the leak part which you care about, your real IP addresses?

Yes, I'm worried because MX5 shows the IP addresses of my private home network.

Quote

All others, including MX4, don't have this issue according to your test? And you also don't have the extension for MX4. So the conclusion you want me to draw is that Maxthon5 can avoid the leak just like MX4? which I also believe in haha.

As you can see MX4 copes with this problem quite well. So probably MX5 after a little analysis of the code should also.

Quote

But I'll reinforce the importance of this issue with them face to face this time!

Thanks, I enjoy it very much 

[BugSir006]

56 minutes ago, Galileusz said:

As you can see MX4 copes with this problem quite well. So probably MX5 after a little analysis of the code should also.

that's useful info!