NotHereToPlayGames

"You are the company you keep." https://quoteinvestigator.com/2020/04/04/company-keep/ Another way to say that, especially here at MSFN, is we all know "who is who" by their meaningless "likes". I didn't read the post as a "personal attack", but more of "one school of thought" against "another school of thought" (our "likes" define who we are!) GANG WARS. Do we know if new members can register? I don't recall seeing a mod chime in on that one. But the more I think about it, the more I can't help but think that if these GANG WARS persist, then MSFN is "weighing its options" on whether "to be, or not to be".

I missed them. But even being "directed" to them, I clearly don't see them the same as you "on a scale of 1 to 10". Some of us are biased, whether we intend to be or not. Some of us are paranoid, whether we indend to be or not. Some of us take sides and troll the forum for "likes" that have no bearing on anything whatsoever other than "trolls being trolls". I stopped following these "discussions" because they have become nothing but Gang Wars.

Unbiased readers do not see it as pollution. THIS is why these sorts of "topics" are forbidden on most forums such as this.

Unable to reproduce here. I do no use the --no-sandbox flag (nor recommend it, for that matter). But I'm also on 1030 at the moment.

You may have had a "disappearing fonts" issue. This has been reported on v13.0 builds and in some v13.5 builds though much rarer with v13.5. I've never actually witnessed it in v13.5 but v13.0 builds would do this quite freqently for me (but only when Stylus was editing a userstyle). If it happens again, hover your mouse over where one of the result lines are supposed to be displayed, sometimes a mouse hover "un-disappears" the font. Or do a "Ctrl-A" to highlight the ENTIRE page and see if there is "evidence" of the disappeared font.

how about giving us a screencap or two?

Your red border - are you using jauntePE by chance?

You will need to elaborate. Everything seems to be working perfectly fine for that link here.

The "K" is also their cheap and low quality model. Sometimes "you get what you pay for" so may have to opt for a higher priced unit.

Ugh! Not even gonna look! I find "easter eggs" to be childish. https://en.wikipedia.org/wiki/Easter_egg_(media)

Manually updating the cert store did not resolve. Still getting those pings. I'm getting them in Supermium, 360Chrome, Chromium 39, and Chromium 49. Maybe it's time to put XP x64 to bed? I'm just gonna block 'em in the HOSTS file for the time being.

as far as that goes, Roytam made the discovery, were stones thrown at Roytam for his observation? rhetorical question

same here no clue, despite the "how" it was discovered, should it really matter? needs fixed regardless of how it was found, correct? or if MSFN is no longer accepting new members, shouldn't that be revealed to existing members? at any rate, i'm not concerned with the "why" or the "how" it was found if the mods didn't know about it, then why throw stones at the person that brought it to their attention? i guess that's how i see it -- "why throw stones?"

I did not read his post as attempting to register a fake account. <OT> In my opinion, there kind of is no difference between the "trolls" we have here and a "fake" account - the end result is basically the same. </OT> My hunch is that the registration process may have inadvertently been broken when we were being hit with HUNDREDS of spam-bot posts for a few days in a row and had to solve that very quickly. Sure, I'd rather see "no new members allowed" than those HUNDREDS of spam-bot posts literally SECONDS apart and lasting for HOURS. But MSFN will fade into the sunset if we don't allow new members. Though on the other hand, purely from an economical feasibility perspective, if we were to take our last 5,000 posts and find that 4,900 of them all came from 20 members, then, um, well...

Some Halloween trivia - one of the worst snowfalls ever to land on Halloween was 1917. What followed was the "Purple Death" of 1918 where 675,000 people in the US (21 million worldwide) died from the Spanish flu (more than WWI, WWII, Korean, and Vietnam wars COMBINED). Side note - it snowed on Halloween here in the midwest USA in 2019 - related to Covid 19 that followed? Just a fun fact, I guess, lol. Snow on Halloween is actually extremely rare. Less than 3% chance if I recall.

Good point. I've never really liked these manual updates, TBH. I'm thinking I just need to visit the websites that "trigger" these cert pings via IE8 (or Chromium 39 or 49) and see what that yields.

For reference - https://msfn.org/board/topic/183352-proxhttpsproxy-and-httpsproxy-in-windows-xp-for-future-use/?do=findComment&comment=1213600 And - https://msfn.org/board/topic/175170-root-certificates-and-revoked-certificates-for-windows-xp/#comment-1095349

Will manually update certificate store this evening. This seems the best method - https://msfn.org/board/topic/181915-system-certificates-updater-the-easy-way/

I've been reluctant to perform any of the "manual" updates for XP's certificate store. I kind of remain reluctant. I guess even moreso now that I don't "rely" on XP nearly as much as I did a year ago. I guess to me, 360Chrome has served its purpose (ie, buy some time while tweaking Win10 to my satisfaction).

That didn't take long. I rebooted after unchecking and they are still showing up in my logs. Adding them to my HOSTS file.

Quite possible. I did have that checked and now have it unchecked. Will monitor over the next few days and see if those pings are gone, my network traffic is always logged, if the computer is "on", the network is LOGGED. I can report that this is NOT a 360Chrome issue and these are US DOMAINS. It also seems to be XP Only. I've not yet witnessed these in any of my Win10 machines. I suppose what is happening is that a certificate is trying to update, it FAILS, so it tries again after a set time interval or with the next reboot or something. I personally feel that the whole cert BS is just as INSECURE these days as HTTP versus HTTPS was in the 90s. The "padlock" in a web browser address bar is WORTHLESS these days. Long gone are the days where it was only your BANK that used HTTPS. These days, MALWARE DISTRIBUTION web sites "miraculously" always always ALWAYS have a "secure padlock", even in XP, but web sites like MSFN do not. So seriously, why even "look" at that browser padlock? Hmmm...

And perhaps more importantly, those are all US DOMAINS. No need to throw in the geopolitical "speculatives".

FALSE ALARM !!! I've just witnessed the same pings on another computer that has never had any version of 360Chrome ever installed! I don't really know "how" XP x64's certificate store is "updated" and it seems these pings are "normal", I've just never seen them before.

By all means, create a thread for any-and-all. Just as Astro likes his threads to stay on point, I fail to see how Brisk Bard 2.6.0 pertains to "360Chrome v13.5.2044 rebuild 2". Sure, there might be a case to be made for not having a 2044 thread, a 2036 thread, a 2022 thread, a 1030 thread. But I do that for a reason and forum "activity" will/should roll the old off of "page 1" and keep the "active" at the top. At least, that's what I'm used to, I have this forum so heavily style-sheeted that I have no clue what it's supposed to look like, lol. The just-discovered .crt/.cer/.p7c "pinging" does affect *ALL* versions of 360Chrome (mine, Humming Owl, Russian Repack, upstream). But I maintain that for the most part, issues with 2044 have no bearing on 1030 so issues with 2044 should be contained within the 2044 thread. Et cetera. That was the intent at least. I say that being a "rare user" of Serpent 52 and New Moon 27/28. Being a "rare" user, I don't read that thread daily/weekly. And jumping in once a month is a NIGHTMARE to get one's self "caught up" on Serpent 52 when several other browsers are discussed all within the same exact thread. BOTH approaches are perfectly valid, of course. We all have our own opinions re: thread-count (and forum trolling, I see them as related due to the "parties" that say "this" versus "that"). "Opinions are like butts. We all have them, doesn't mean we all want to hear them."

1030, 2022, 2036, and 2044 all ping these "certificates". Upstream, Russian Repack, my releases, and Humming Owl releases (13.0.2250 and 13.0.2310). The good news is that they are only "pinged", the browser as a "portable" cannot interact with the OS in a way that an "installed" browser would be able to. Those that do not clear their cache with each and every browser exit may have had these "pings" only upon creating their profile afresh. These are the pings I've witnessed thus far, likely more - ht-tp://apps.identrust.com/roots/dstrootcax3.p7c ht-tp://cacerts.digicert.com/CloudflareIncECCCA-3.crt ht-tp://cacerts.digicert.com/DigiCertGlobalG3TLSECCSHA3842020CA1-2.crt ht-tp://cacerts.digicert.com/DigiCertGlobalRootG3.crt ht-tp://cacerts.digicert.com/DigiCertTLSHybridECCSHA3842020CA1-1.crt ht-tp://crt.e2m02.amazontrust.com/e2m02.cer ht-tp://crt.rootca3.amazontrust.com/rootca3.cer ht-tp://crt.usertrust.com/USERTrustECCAddTrustCA.crt ht-tp://e1.i.lencr.org/ ht-tp://secure.globalsign.com/cacert/gseccovsslca2018.crt ht-tp://x2.i.lencr.org/ ht-tp://zerossl.crt.sectigo.com/ZeroSSLECCDomainSecureSiteCA.crt 1030 will be fixed first.