Supermium

[UCyborg]

Did anything come out of getting GPU canvas acceleration working and WebGL running on GPU on XP?

[dmiranda]

I find the developer of this fork to be very conscientious. Against clamor and scorn, he took a year to produce a first solid (albeit a bit leaky) first alpha for XP. Each subsequent release has shown, so far the same care, and each has brought improvements. And if you do things right, changing the engine has little to no impact (in my case, no impact of notice, so far) on your profile. I switch as soon as he releases.

[grey_rat]

superfox very slow https://github.com/win32ss/supermium/issues/986

[CIACIACIACIACIACIA]

@NotHereToPlayGames i want to talk to you.

I have a bug with supermium (versions 126,124,122),they show the certificate authority error on windows xp what ever you do.

Other browsers don't have that problem (kafan mini browser,360 extreme explorer).

Question is why?

 

[NotHereToPlayGames]

Click your padlock and view the Details tab of the certificate.

Scroll down to Key ALGORITHM and click.

View the Field Value and my guess is that you are seeing ELLIPTIC CURVE for each and every web site that shows this certificate authority error on WinXP.

[CIACIACIACIACIACIA]

Some sites doesn't display at all and show the PKCS #1 RSA Encryption in field value.

 

[NotHereToPlayGames]

What does Certificate Signature Algorithm say for SHA?

I'd have to review, but I don't think XP can do anything higher than SHA-256.

[CIACIACIACIACIACIA]

Says PKCS #1 SHA-256 With RSA Encryption.

 

 

Edited November 4 by CIACIACIACIACIACIA

[NotHereToPlayGames]

Can you share the web site URL?

[CIACIACIACIACIACIA]

Of course:

https://www.sciencedaily.com/

We had extensively discussed this with Dave-H and he told me to report the error and suggest about the kafan mini browser built-in certificate method and synchronization.

Display is a working Supermium version 126-r4.

 

 

Edited November 4 by CIACIACIACIACIACIA

[NotHereToPlayGames]

20 hours ago, CIACIACIACIACIACIA said:

@NotHereToPlayGames i want to talk to you.

I have a bug with supermium (versions 126,124,122),they show the certificate authority error on windows xp what ever you do.

Other browsers don't have that problem (kafan mini browser,360 extreme explorer).

Question is why?

 

I cannot replicate your errors.  Supermium v124 and 360Chrome both show secure connection for ScienceDaily.

All I can add is that I have never, and I really do mean *NEVER* "updated my root certificates".  There are several threads here at MSFN that are dedicated to "updating root certificates".  I HAVE NEVER DONE ANY OF THEM!

My XP root certificates are AS MICROSOFT INTENDED THEM, I have not "intervened" in any way, shape, or form and my root certificates WORK AS INTENDED.

I can only state the FACTS as they pertain to my XP - I have never manually updated my root certificates and I cannot replicate your certificate authority errors.

Unsure how relevant that FACT is, but it is a fact!  My root certificates are as OFFICIAL XP intends them to be.  I do not even use/install POSReady2009.  Again, unsure if relevant, just a FACT as it pertains to my XP.

Edited November 5 by NotHereToPlayGames

[CIACIACIACIACIACIA]

Does versions of windows XP play a role to the compatibility of Supermium?

In order to make a browser more compatible with windows 2000  (i suppose) you have firstly make it more compatible with windows XP is that correct?

 

[NotHereToPlayGames]

You'd have to post those types of questions here  --  https://github.com/win32ss/supermium/discussions

Unless Supermium becomes truly "ungoogled", I basically have no use for it.  I remain optimistic towards its development.

Though I do wish that an older version of Chrome was "matured" *before* the project started "chasing" more recent versions.

[Dave-H]

Just FWIW, I have no security errors shown on the ScienceDaily site either, in Supermium 126, Thorium 122, or 360Chrome 13.5.
I had a long discussion with CIACIACIACIACIACIA by PM about this, and I could not explain why he was seeing security errors which I wasn't.
Good to have it confirmed that others are not seeing errors either, but it's still puzzling why they are happening for CIACIACIACIACIACIA.
I was clutching at straws a bit, suggesting that it might be a Root Certificates problem, obviously it isn't!

[NotHereToPlayGames]

The screencap indicates he is using ProxHTTPSProxy.  That "intervenes" with certificate chain so the issue could be ProxHTTPSProxy.  But I would assume that ProxHTTPSProxy is being used for "all browsers" and not just Supermium.