Leaderboard

MailNews is basically an XP/Vista-compatible build of Interlink, which explains the link in the about: window seen above going back to Tobin's site. With browsers (particularly Serpent), @roytam1 occasionally reverts some changes to retain useful features removed in "official" builds, so even users of newer Windows versions may prefer his builds to the official ones. That's not really the case with MailNews; there's little reason to deviate from an official build of an email client, other than branding. @VistaLover found the source code for the about: window. It's an .xul file. I made a trivial change in my copy of the Interlink repo, pointing to @roytam1's page vs. Tobin's (roytam1 is free to incorporate this change in his builds if he wants); unfortunately the link destination isn't controlled by a pref, so it's not so easily moved to the "branding" folders of the source tree as the Help menu links were.

Well, the best encryption today is so strong that not even the US NSA can crack it. Of course, that just means they turn to hacking techniques; i.e., finding vulnerabilities in OSes and ways to exploit them, which naturally cause havoc when they get leaked, as with the WannaCry debacle. I believe the idea of universal HTTPS was a good one: if everyone uses it, then its use won't be looked on with suspicion, so we paranoid types won't be targeted by the likes of the NSA or MI5/6 as "potential terrorists" just for trying to protect our privacy. That's also why the UK took the extreme (IMO) step of banning end-to-end IM encryption: if they could crack the encryption, they wouldn't have bothered; but if, instead, encryption is outlawed, they can just "assume" anyone using it is up to no good and investigate them. (It won't work though: the "real" terrorists will just use steganography to conceal encrypted messages in innocuous-seeming images, audio files, etc.; the ones that'll get busted are folks just trying to conceal an affair or something.) What does annoy me, though, is the way Web sites keep disabling older, less secure protocols and ciphers. Sure, the newest protocols and ciphers should always be the first choices, but there's no good reason to lock folks out of your Web site just because they're still on Android 4.0 or XP or whatever. But at least we have @roytam1's browsers with the latest NSS versions to handle those sites that require the latest security.

KB4034775, KB4343674, KB4458000, KB4458006, KB4462987, KB4463573, KB4473077, KB4487085-v2, KB4487385, KB4489977, KB4490385, KB4493793, KB4493794, KB4493795, KB4493796, KB4493797, KB4494528, KB4495022.