30112853

Newcomers
  • Posts

    4
  • Joined

 Content Type 

Profiles

Forums

Release Notes

Bug Tracker

Help page

Help page-CN

Release Note5

Rules and recruitment

Release Note6

Posts posted by 30112853

  1. Dinataspace replied at 2015-2-24 22:12 back.gif

    I don't think Mx not checking certificates. On my trial error with this url https://superfish.xmarks ...

    Yes sometimes Maxthon does, that's what makes this so strange, but there are also sites where it appears it doesn't.

    Including the test sites for SuperFish: https://filippo.io/Badfish/ & https://lastpass.com/superfish/

    All other browsers work fine on those sites (including chrome/chromium/internet explorer, of which Maxthon uses it's engines), so apparently there is an issue somewhere in Maxthon.

    Also when you go to https://nl.surveymonkey.com/ there is no lock icon to see if the certificate is being checked, whereas there is one on https://google.nl/ (using .nl because I get redirected see next point).

    Strangely though when I enter https://www.google.com I get redirected to https://www.google.nl/?gfe_rd=cr&ei=AKHtVMDMKc-Y-AbMlYGAAg and I get no lock icon, if I then enter that url manually, the lock icon suddenly appears.

    I'm not saying this is related or that it means there are no checks, but it does appear there are some issues with certificate checking.

    As you pointed out, this could pose a serious security risk it's better to be safe than sorry.

    Dismissing an issue like out of the box wouldn't be professional and I'm sure the guys from Maxthon won't do that.

  2. moss33 replied at 2015-2-22 18:47 back.gif

    So, is it safety using maxthon before they fix this?

    Basically no, because if certifices aren't check for validity, then a corrupt party could inject their own certificate and intercept all traffic you send/receive.

    For instance, if you go to your online banking account and enter your login information a third party could intercept your codes and use them to make transactions to themselves.

    This is called a man-in-the-middle attack.

    http://en.wikipedia.org/wiki/Man-in-the-middle_attack

    So for websites which only show you some info, this isn't too big of a deal, but for any site where you enter user-data it is a serious issue.

    So until this is fixed, I would suggest not doing anything which requires you to enter usernames/passwords and the like.

    For those instances I'd suggest using another browser (chrome, firefox, opera).