Dragoncho Posted December 23, 2015 Report Share Posted December 23, 2015 The latest beta 4.9.0.2200 still does not solve the certificate list problem, which was introduced a long time ago in Ultra mode. It was reported by me, but the report died in vain. When opening a site that requests certificate authentication in Ultra mode, the list of the certificates that is presented is not filtered as it should be and it presents also Intermediate and Root certificates, which is wrong. This is not an issue with the Core, as Chrome does not have this problem and it exists it every Maxthon 4 version (not sure when it was introduced, but this bug was reported in August 2012). In version 4.4.1.2000 this bug featured a new double-selection option with both Ultra and Retro mode dialogs for certificate selection at the same time. In the attached image you may see the correct display in Retro mode and in Chrome to the left and the Ultra mode display to the right. All Intermediate and Root certificates should be hidden from this dialog. Link to comment Share on other sites More sharing options...
BugSir007 Posted December 24, 2015 Report Share Posted December 24, 2015 Hi, Thanks for bringing up this problem. Would you please give us the specific website url on which this issue is occurring ? We will do our best to fix it. Thanks. Link to comment Share on other sites More sharing options...
Dragoncho Posted December 24, 2015 Author Report Share Posted December 24, 2015 You can use any site, which requires a client certificate. However, here are the ones that I usually provide here: https://www.epay.bg/v3main/front?lang=en https://e-fibank.bg/EBank/ (you may change the language in the top right corner if needed) https://ebb.ubb.bg/Log.aspx?lng=EN https://online.bulbank.bg/page/default.aspx?user_id=&session_id=&xml_id=/en-US/.loginAll You may try using both Ultra and Retro mode. Link to comment Share on other sites More sharing options...
BugSir007 Posted December 24, 2015 Report Share Posted December 24, 2015 Thanks for the links. The problem has been confirmed as a bug and it will be looked into very soon. Please stay tuned for future versions. Thanks again for your support. Link to comment Share on other sites More sharing options...
Dragoncho Posted December 28, 2015 Author Report Share Posted December 28, 2015 Thank you, the bug confirmation is very important, so I appreciate it. Link to comment Share on other sites More sharing options...
Dragoncho Posted January 15, 2016 Author Report Share Posted January 15, 2016 Hi again, may I have the JIRA bug number, please. Currently I don't see this in the Confirmed bug section, maybe because it was not moved there? Link to comment Share on other sites More sharing options...
BugSir007 Posted February 18, 2016 Report Share Posted February 18, 2016 Hi, Have you tired the latest RC version 4.9.0.3000RC to see if the problem still exists? Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.