SeaMonkey 2.53.10.1 has been released !!!

[ElTxolo]

• SeaMonkey 2.53.10.1 has been released (December 13, 2021)
  
  
  
  
  
  
  
  
  
  
  
  
  • - Official announcement and release notes:
  • https://www.seamonkey-project.org/news#2021-12-13
  • https://www.seamonkey-project.org/relea ... 2.53.10.1/
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  Cheers!

[Peter Creasey]

Bravo!

[frg]

Because of this one you should probably update a bit faster if you use mail: https://www.mozilla.org/en-US/security/ ... sa2021-51/

[therube]

.

[ndebord]

• • - Official announcement and release notes:
  • https://www.seamonkey-project.org/news#2021-12-13
  • https://www.seamonkey-project.org/relea ... 2.53.10.1/
  Cheers!

ElTxolo

Good news... works great.

Nick

[4td8s]

does the http://www.microsoft.com web site work correctly with the SM 2.53.10.1 release?
it stopped working with SM 2.53.10.x and older a few days ago and produced a "MOZILLA_PKIX_ERROR_OCSP_RESPONSE_FOR_CERT_MISSING" error message

edit - I downloaded & installed wg9s's SM 2.53.11b1pre 12/15/2021 build and the problem still remains as I still encounter ""MOZILLA_PKIX_ERROR_OCSP_RESPONSE_FOR_CERT_MISSING" error message when trying to go to the Microsoft web site

looks like it's NOT fixed with SM 2.53.10.1 as I don't see any mention of bug 1745600 in the SM 2.53.10.1 release notes

[RDaneel]

Well, "WFM"... with the 64-bit 12/15 Build By Bill(tm).

I do use the "legacy" uBlock Origin version for SM, and I have what I believe is the default UA:

"Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0 SeaMonkey/2.53.11"

There are piles of complaints in the error console about MSFT assets, mostly stuff like

Warning: Expected media feature name but found ‘-ms-high-contrast’.

and

Warning: Error in parsing value for ‘display’. Declaration dropped.

... but the site appears functional.

[ElTxolo]

does the http://www.microsoft.com web site work correctly with the SM 2.53.10.1 release?
it stopped working with SM 2.53.10.x and older a few days ago and produced a "MOZILLA_PKIX_ERROR_OCSP_RESPONSE_FOR_CERT_MISSING" error message
[....]

• 
  Well, personally I have no problem, visiting (forcibly to test, the crappy 'Mi€ro$oft' site).
  
  Using SeaMonkey 2.53.10.1 on SparkyLinux (debian testing)
  (with uBlock Origin 1.16.4.30 & NO workarounds ....)
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  
  

[rainyd]

does the http://www.microsoft.com web site work correctly with the SM 2.53.10.1 release?
it stopped working with SM 2.53.10.x and older a few days ago and produced a "MOZILLA_PKIX_ERROR_OCSP_RESPONSE_FOR_CERT_MISSING" error message

edit - I downloaded & installed wg9s's SM 2.53.11b1pre 12/15/2021 build and the problem still remains as I still encounter ""MOZILLA_PKIX_ERROR_OCSP_RESPONSE_FOR_CERT_MISSING" error message when trying to go to the Microsoft web site

looks like it's NOT fixed with SM 2.53.10.1 as I don't see any mention of bug 1745600 in the SM 2.53.10.1 release notes

There's no problem with that page while using most recent official version.

[Peter Creasey]

Yes, the site opens fine for me with SM 2.53.10.

[4td8s]

ok thanks guys. seems that I'm a little puzzled on this one

I installed official SM 2.53.10.1 on another PC a few hours ago and the http://www.microsoft.com site opens up fine without errors

on the affected PCs where I encountered the "MOZILLA_PKIX_ERROR_OCSP_RESPONSE_FOR_CERT_MISSING" problem in SM, I had to clear the browser cache & cookies (and run ipconfig /flushdns) and reboot to see if SM will load the Microsoft site without those errors and the Microsoft web site is now working fine

edit - it's only with some of the wg9s's SM 2.53.11b1pre builds I was using that had the problem, not with official SM 2.53.10.1

[raj_bhaskar]

I had that same error on a docs.micrsoft.com site that I was trying to visit yesterday (worked in Firefox). I'm working from home at the moment, RDP-ing to my office PC and it was the office SeaMonkey that was failing. I tried it on my home instance of SeaMonkey before I raised the same query here, and it worked okay. I just put it down to weirdness with my work network. I am using official 2.53.10.1.

Oddly, it seems to work today though - https://docs.microsoft.com/en-us/sql/li ... rver-ver15

[raj_bhaskar]

Oops, just seen this this post from frg explaining it.