Extreme Explorer 360 Chromium 78-86 General Discussion

[Humming Owl]

23 hours ago, FantasyAcquiesce said:

Hello,

I have tried the latest version of this web browser but get a few certificate errors on western sites. Furthermore, websites cannot stream because of this error.

Is there a solution to this? The Chinese Mini Chrome browser doesn't suffer this issue.

Have you tried these tools to update certificates?

https://msfn.org/board/topic/175170-root-certificates-and-revoked-certificates-for-windows-xp/?do=findComment&comment=1110568

http://i430vx.net/files/wsusstuff/

https://retrosystemsrevival.blogspot.com/2021/03/certificate-updates-for-windows.html

Cheers.

[Cixert]

On 9/5/2021 at 4:17 PM, Humming Owl said:

Have you tried these tools to update certificates?

https://msfn.org/board/topic/175170-root-certificates-and-revoked-certificates-for-windows-xp/?do=findComment&comment=1110568

http://i430vx.net/files/wsusstuff/

https://retrosystemsrevival.blogspot.com/2021/03/certificate-updates-for-windows.html

Cheers.

I have the same problem with the certificates on version 13.
On versions 12 and 11 I haven't problems with the certificates.
I have the root certificates updated by various methods.
Most sites cannot make a secure connection despite the fact that the certificates are up to date.

Sometimes it is solved by manually installing an intermediate certificate. But in the case of MSFN forum site all the certificates are correct, however the secure connection does not occur.

v12 capture

v13 capture


Web site unsafe connect


unsafe connect


Edit:
I have done more tests:
On MSFN.org
2 identical unzipped versions of the mod by Humming Owl
A works https
Another does not work https
I have checked the settings and put it identical on both.
Nothing has changed, one works and another doesn't.
I've also tried installing the original Chinese version and it doesn't show https either

On sites with problems with intermediate certificates
Neither browser v13 connects with intermediate certificates

Edited September 6, 2021 by Cixert

[CIACIACIACIACIACIA]

About the 360 EXTREME EXPLORER i have a newer version of java than yours installed (8v 131 and 8v 152).

Unfortunately i haven't solved the mystery of sudden exiting yet.

 

 

 

 

 

Edited September 6, 2021 by CIACIACIACIACIACIA

[NotHereToPlayGames]

Do you have POSReady updates installed?

I seem to recall that they broke XP's certificate store - but I don't think we ever really got far enough to prove this 100%.

People running un-hacked XP SP2 and un-hacked XP SP3 seem to have zero issues with the "green padlock".

[Cixert]

2 hours ago, ArcticFoxie said:

Do you have POSReady updates installed?

I seem to recall that they broke XP's certificate store - but I don't think we ever really got far enough to prove this 100%.

People running un-hacked XP SP2 and un-hacked XP SP3 seem to have zero issues with the "green padlock".

I have only all XP SP3 updates

[NotHereToPlayGames]

Same here!

It kinda confuses me on wny people install "certificate updates".

I've never needed any of these "updates" and I have a "green padlock".

I personally think that people have "broken" things when they installed these so-called non-Microsoft "certificate updates".

[rereser]

.

Edited Friday at 02:17 PM by rereser

[NotHereToPlayGames]

[Cixert]

Interesting but I don't use noscript. The problem with the certificates only appears on version 13, original or modified. On other versions the certificates work correctly.

[rereser]

.

Edited Friday at 02:17 PM by rereser

[NotHereToPlayGames]

3 hours ago, rereser said:

my question is : are there important changes made in the chrome dll in regards to stability or otherwise between rebuild 3 and 4 ?

The biggest difference between the two is the order in which several hexadecimal values were replaced.

v4 was a complete rebuild from the ground up based on several tweaks and modifications learned over nearly a year of using 360Chrome as my default-for-all web browser.

v3 had all of those tweaks and modifications performed in a rather random order as we-the-community discovered new modifications along the way (and Humming Owl showed up midway through that process).

 

Consider it this way, one of the very first modifications was to remove all hexadecimal occurrences of "360.cn".

Later on, we decided to remove all hexadecimal occurrences of "ext.chrome.360.cn" before we remove "360.cn".

BOTH methods will "break" the URL so I do not think this is the reason for the differnce in bold versus unbold in your GUI (a difference that seems isolated to only your OS config).

But it is a "difference" between v3 and v4.

 

Another difference is that v3 breaks a resolver function (a discovery by Dixel) that "calls" an IP Address while v4 breaks the IP Address (Humming Owl's approach) but leaves the resolver function intact.

Both methods will "break" what the original 360Chrome was attempting to "do" so again I do not think this is the reason for the difference in bold versus unbold in your GUI.

 

The last major difference becomes extremely difficult to isolate.

v3 did not make a "gstatic" connection because of a command line startup prompt that my rebuilds utilize but that Humming Owl's builds do not utilize.

So it was a much higher priority for Humming Owl to hard-code methods to prevent that "gstatic" connection than for my builds.

v4 implements Humming Owl's hard-coded method that prevents this "gstatic" connection (which my version technically did not make anyway).

I do not think this is the reason for the difference in bold versus unbold in your GUI.

 

At the same time, v3 also replaced all hexadecimal "googleapis" values.  But v4 does this also.  I cannot rule this out and this could be a cause for bold versus unbold in your GUI.

 

Again, at the same time, v3 replaced several hexadecimal occurrences of "i.360.cn", "browser.360.cn", "se.360.cn", "360safe.com", "chrome.360.cn" and "360.cn".

This gets tricky to track because "360.cn" was ALREADY removed SEVERAL months prior so a search-and-replace for "i.360.cn" won't find anything because the "360.cn" portion is no longer present.

I do not think this is the reason for the difference in bold versus unbold in your GUI.

But it is a "difference" between v3 and v4.

 

v4 goes one step further and not only removes the hexadecimal occurrences of "i.360.cn", "browser.360.cn", "se.360.cn", "360safe.com", "chrome.360.cn" and "360.cn" but also removes the unicode occurrences.

I do not think this is the reason for the difference in bold versus unbold in your GUI.

 

 

Long story short ( https://www.youtube.com/watch?v=YCP2QQH4uuQ )  --  there is a HUGE list of differences between v3 and v4.

I still "trust" both but I can replicate v4 and recreate it whereas v3 spanned so many months and small changes along the way that the actual "order" cannot be replicated.

It is very interesting that it seems to be tracked down to chrome.dll instead of any of the .srx files, anything inside options.zip, or anything inside resources.pak.

Because all it really takes is accidentally missing a closing quotation mark in a line of code that makes an entry bold and everything BELOW that line of code "could" render in bold.

But something in chrome.dll instead of any of those files?  Very peculiar.

[rereser]

.

Edited Friday at 02:16 PM by rereser

[NotHereToPlayGames]

I do similar to prevent "cleartype" BS.

I have the exact opposite of "color blind" vision.

Cleartype fonts give me migraines because my vision can see the little red and green dots at the font-corners and they dance and flash and gyrate according to my vision - among many others, it was a gigantic ordeal when Microsoft pushed that "technology" into new operating systems. 

[Guest]

What version of Javascript engine does 360 use?

chrome://version

 

 

[NotHereToPlayGames]

JavaScript:  V8 7.8.279.23