11.26.22

Microsoft is the Problem, Not the Solution

Posted in Deception, FUD, Microsoft, Security at 2:25 pm by Dr. Roy Schestowitz

Video download link | md5sum 7adbcf370ee68a183b5aad2e87f4ff0e
Microsoft Concern-Trolling on Security
Creative Commons Attribution-No Derivative Works 4.0

Summary: The media is doing anything it can to suppress discussion about the national or international security crisis caused by Microsoft; instead, some publishers go as far as lionising Microsoft, portraying it as the ‘Jesus’ of computer security

THE VIDEO above concerns the concern-trolling by Microsoft et al, including Jim Zemlin (Linux Foundation) idolising the practices of the NSA's back doors partner as if Microsoft and security can be uttered in the same sentence (with a straight face). Microsoft and security are polar opposites and there’s ample literature explaining why.

Under the guise of “national security” Microsoft lobbyists are pursuing legislation that marginalises Free software in the US and EU. This is no laughing matter, it’s just regrettable that what’s left of “the media” does not pay attention and instead participates in the FUD campaign (with misleading and loaded terms like "supply chain").

“Microsoft and security are polar opposites and there’s ample literature explaining why.”The video shows the typical chorus from SANS (as of late), weaponising very old news (almost 12 months old!) to divert attention away from the biggest culprits, including back doors, ransomware, and so on (predominantly Windows issues).

As of this week, the Microsoft-connected media has the typical audacity to also portray Microsoft as a security expert when in fact dealing with antiquated software. As an associate of ours explains, “a) Boa was discontinued in 2005, the problem is not “open source software” b) [it's ludicrous that] Microsoft [is] posing as an authority on anything” (including security and “open source”).

The video above goes through these stories and ends with one from our latest Daily Links that said:

Although the Boa web server has been discontinued back in 2005, a lot of businesses still continue to use the same. Companies continue to use Boa web servers as it is bundled in the software development kit (SDKs) of a product. However, according to the latest report from Microsoft, Boa web server comes with potential risks and it is easy for [attackers] to [breach] these services. More importantly, Microsoft’s research showed that Indian power companies have faced several attacks because of the web server.

Do we need “Microsoft’s research” to know that running software discontinued more than 17 years ago is not a good idea? This is a symptom of undermined if not deeply corrupted media.

11.01.22

Red Hat (IBM) Hyped Up a Fair Pair of Flaws That Isn’t Critical, Isn’t Actively Exploited, and Even Red Hat’s Distro Isn’t Patching Yet

Posted in Deception, Free/Libre Software, FUD, GNU/Linux, IBM, Marketing, Microsoft, Red Hat, Rumour, Security, Servers, Standard at 3:14 pm by Dr. Roy Schestowitz

Video download link | md5sum 8de27c8022d55f728a4d1c5eb55026e0
Irresponsible Misinformation About OpenSSL
Creative Commons Attribution-No Derivative Works 4.0

Summary: Fuelling Microsoft-affiliated and sometimes Microsoft-funded “news” (noise) sites, Red Hat — and to a lesser extent Fedora — exaggerated the severity of bugs a week before their details’ release (long and purposeless suspense); it’s a case of a boy who cries “wolf!” to get “likes” in Twitter and media coverage that relies on nothing but lousy (inaccurate) "tweets", where fact-checking is impeded by NDAs/embargo

A few days ago we took note of the overhyped (mostly by Red Hat) impending patch for OpenSSL. Red Hat ended up slipping/changing the release date of Fedora, adding some more to the perceived danger, contributing to the scare, resulting in a week’s worth of media misinformation like calling it "zero day" (even in headlines!). This irresponsible hype turns out to be have been outright disinformation (or at best misinformation) about the severity and it’s worth noting that Red Hat is in no hurry to patch its most important products and there are no actively-exploited aspects; in other words, it is not “0-day” and there is no immediate rush to patch (in some cases there is no patch, either).

“We perceive this to be a bit of a media blunder, taking informal “tweets” at face value and trying to compete over who produces the most scary headline/s for about a week already.”The 8 URLs from the video are listed below in a logical order. To quote [4] below “Q: The 3.0.7 release was announced as fixing a CRITICAL vulnerability, but CVE-2022-3786 and CVE-2022-3602 are both HIGH. What happened to the CRITICAL vulnerability?”

We perceive this to be a bit of a media blunder, taking informal “tweets” at face value and trying to compete over who produces the most scary headline/s for about a week already.

Links from the video above

  1. OpenSSL 3.0 Series Release Notes
  2. Vulnerabilities list
  3. OpenSSL Security Advisory [01 November 2022]
  4. CVE-2022-3786 and CVE-2022-3602: X.509 Email Address Buffer Overflows
  5. Comments: OpenSSL Outlines Two High Severity Vulnerabilities
  6. OpenSSL 3.0.7 released
  7. OpenSSL Releases Patch for 2 New High-Severity Vulnerabilities
  8. OpenSSL 3.0.7 Fixes Two High-CVEs with Buffer Overflow

10.30.22

The Next OpenSSL Bug Will Likely Disappoint Those Who Believe the Linux-Hostile Media

Posted in Free/Libre Software, FUD, GNU/Linux, Security at 6:22 pm by Dr. Roy Schestowitz

Video download link | md5sum 4b7ddbb46fa6769b563d42abfd3763b2
Trusting the FUD Blindly
Creative Commons Attribution-No Derivative Works 4.0

Summary: Fear, Uncertainty, and Doubt (FUD) campaigns have begun based on a lack of information rather than actual substance; Dramatisation of this kind merits a debate as the boy keeps crying “wolf!” in vain (because he sees a dog)

OVER the past 5 or so days we’ve included in Daily Links many articles about an upcoming patch for OpenSSL, not “imminently” as this was disclosed almost a week in advance, which is rather unusual (that long a timespan).

We’ve patiently been wanting to do a a response, waiting for insiders who can tell what the bug was or how severe it really was; we scolded some media for calling it "zero day" because as far as we can tell the term is misapplied, maybe even on purpose.

“A lot of the media reports, not privy to any details, trust the panic makers despite having no details. Where’s the fact-checking?”So many speculative, uninformed and uninformative articles have mentioned the magic “FUDword”, Heartbleed, still failing to recognise that it was a bug first discovered by Google and then hyped up by Microsofters to stigmatise Free software (we wrote a lot about this at the time). This was almost a decade ago; after that we saw many logos and sites (for pertinent bugs, not pieces of software) and even the occasional pranks after that, trying to reproduce that hype’s success [sic] because FUD travels fast and some firms wanted to “make a name” for themselves.

People with access to information or special privileges already caution us that the advanced notice is more about hype than substance. A lot of the media reports, not privy to any details, trust the panic makers despite having no details. Where’s the fact-checking?

Seeing how “Heartbleed” FUD was used by Microsoft for years (and "log4j" a year later, even by the anti-Linux Foundation), it seems likely that this is a campaign of drama, not a real security crisis. How many breaches will be caused by this? Time will tell, but probably not many (same as “Heartbleed”, where reality didn’t match the propaganda).

10.25.22

Layoffs at Microsoft’s Friends, Who Help Spread Anti-Linux FUD and Pay the ‘Linux’ Foundation to Play Along

Posted in FUD, Microsoft, Security at 7:57 pm by Dr. Roy Schestowitz

Good news for a change…

Snyk to cut 14% of workforce in latest round of tech industry layoffs

Summary: The company that pays the Linux Foundation to badmouth GNU/Linux is vanishing little by little; good riddance to bad rubbish (Synk comes from a rogue intelligence agency, which does wiretapping and assassination)

(Microsoft has already had four waves of layoffs this year; the year isn’t even over yet)

10.12.22

Jim Zemlin Idolises Microsoft and Bill Gates (in New Talk Published This Week), Applauding a Back Doors Company and Jeffrey Epstein’s Enabler

Posted in Deception, FUD, Microsoft at 4:04 pm by Dr. Roy Schestowitz

Recent: Sheela Microsoft (Zemlin) Does Not Like Linux and Jim Zemlin Idolises Bill Gates

Summary: Storytelling by Jim Zemlin (11:30-12:55 above; roughly 10% of his keynote!) promotes a Microsoft myth at the latest Linux Foundation event. As a side note, even a year later Jim Zemlin still spreads the “log4j” FUD for Microsoft and friends. It was patched 10 months ago, but he keeps bringing this up while pretending Microsoft is some role model for security. Funny how he didn’t read out any Gates memos on attacking GNU/Linux [1, 2, 3] or cited any reports on Bill’s crimes, including recent scandals that merit prosecution. Microsoft 'bought' him.

10.10.22

Stefano Maffulli, Informally a Microsoft Employee, Salaried Partly by Microsoft

Posted in Finance, FUD, Microsoft, OSI at 1:57 pm by Dr. Roy Schestowitz

Context: Open Source Initiative Controlled (Infiltrated) by Microsoft GitHub: Microsoft Bribes OSI to Justify GPL Violations Under the Guise of ‘AI’, Even Writes the OSI’s Material | Open Source Initiative is a Shameless Megaphone and Advocate for Microsoft’s Proprietary Software (GitHub). It Also Encourages Copyright and GPL Violations (Plagiarism Disguised as ‘AI’).

Hi, I'm Stefano Maffulli; Where Do You Think I Get a 6-Figure Salary From?
A coin-operated Microsoft mouthpiece. Attacking Open Source while wearing an “open source” hat.

Summary: Being full-time staff at OSI means being Microsoft staff. Check where the money comes from and what the job involves these days.

10.08.22

Beware the Distortion of Terms Like ‘Supply Chain’, ‘Zero Day’, and ‘Back Door’ (New FUD Patterns Against Free Software, a Distraction From the Real Culprits)

Posted in Deception, Free/Libre Software, FUD, Microsoft, Security at 11:45 am by Dr. Roy Schestowitz

Proprietary software is being protected by ‘googlebombing’ tactics; the biggest weaknesses of proprietary software are being spun as a key problem with “Open Source” and proprietary software's shortcomings are being blamed on the alternative to it

Linux Foundation: repeat what Microsoft says

Summary: Microsofters spread misinformation/disinformation about Free software and security thereof; the corruption (bribery) of organisations such as the so-called ‘Linux’ Foundation means that Microsoft’s misinformation/disinformation now comes out of the mouths of the supposed opposition, too

THE Daily Links in this site habitually add some “Ed”(itorial) comments to highlight FUD (Fear, Uncertainty, Doubt/fear-mongering) and offer some quick response to it. How much can publishers lie for the likes of Microsoft or VMware before those publishers perish due to a lack of credibility and, in turn, a lack of audience?

Earlier today we posted some more examples of this kind in Daily Links. Not a day goes by without several such ‘incidents’ (misinformation/disinformation).

“The real “supply chain” trouble is Microsoft and proprietary software…”In this post we highlight 3 recent patterns we’ve noticed. They are semantic lies.

Recently, a Microsoft front group called “Linux Foundation” kept using terms like “supply chain”. Years ago nobody used this term in relation to Free software and then Microsoft bought a lot of the so-called ‘supply chain’, in the form of GitHub and then NPM. Would anyone trust the integrity of code and binaries from a platform controlled by Microsoft and the NSA, whose CSO is a decades-long NSA veteran?

The real “supply chain” trouble is Microsoft and proprietary software; you can’t audit what you’re getting and it might be intentionally back-doored, taking advantage of this opacity. So why pretend this is a “FOSS” issue?

“If something was fixed or was already patched upstream before disclosure, then it is not a 0-day.”Speaking of back-doored code or executables, “backdoor” means not a backdoor anymore. Microsoft-controlled media distorted the term and kept mentioning it in false contexts. Nowadays it just means a server got compromised and then the person who took control of it installed some more stuff. But that’s malware and it says nothing about how the malware got on the system in the first place (unless there was an actual back door).

Many would say that servers can be hijacked using critical and remotely-exploitable flaws, set aside bad passwords (those are typically a human failure). But that leads us to the distortion of the definition of “zero day” (or 0-day). If something was fixed or was already patched upstream before disclosure, then it is not a 0-day. If it starts getting exploited the moment it is disclosed, then it’s a “1-day”. But looking around the Web today, we found several examples of lies to that effect. The media keeps badmouthing Zimbra, but this seems to be a way to distract from several critical Microsoft flaws, including those affecting Exchange. Those are actively being exploited, according to a very recent report. the Zimbra issue is old news (about a month old) and servers have already been patched by responsible administrators, such as my colleagues. Although it seems like the Zimbra hole might be a new one, the last patch partly addresses it. Do not forget that CISA released a list with three Microsoft holes that are actively exploited, including in Exchange, so why shift/divert to talking about Zimbra rather than Exchange? Are they trying to reinforce some false perception that moving away from Exchange would mean equally bad or even worse security?

“The scenario, as per Dan Goodin et al (even sued for defamation already, for utterly poor reporting on security), is nowhere as grim as the Microsoft Exchange situation.”What’s bothersome here is the repeated distortion of the term “zero day”. An associate told us that “‘they’ must be really worried about the advance of FOSS to spread so much dated FUD about Zimbra and other projects. One giveaway is the use of the marketing phrase “zero-day”. That used to mean an exploit that was in active use before the vendor admitted to it existing. Now it just means bug with an exploit.”

The scenario, as per Dan Goodin et al (even sued for defamation already, for utterly poor reporting on security), is nowhere as grim as the Microsoft Exchange situation. We already saw that Microsoft goes on for months and months without patching known Exchange flaws, even when it is fully informed that such flaws are actively being exploited already.

Zimbra does E-mail, so that helps distract from what Microsoft is doing, with the real zero days, the real back doors, and the real supply chain crisis. Microsoft monopolises this chain (it’s proprietary) and refuses to fix it, leaving the victims helpless. This must be intentional. Or as out associate put it, “paid-for back doors on behalf of those that pay enough, or more specifically bug doors. Those are exploitable bugs about which the payers are informed long in advance of Microsoft getting around to patching them.”

“Zimbra does E-mail, so that helps distract from what Microsoft is doing, with the real zero days, the real back doors, and the real supply chain crisis.”It’s the Windows [sic] of opportunity… Edward Snowden has already provided ample evidence of this. Microsoft keeps giving the NSA and FBI enough time to install a RAT or bootkit before the patches get deployed (too late). “And the FSB and just about any similar agency in all the other Internet-connected countries in the world,” our associate noted.

So we’re meant to think that the real crisis is Free software and Microsoft lobbyists then push for new, discriminatory laws that stigmatise "Open Source". New zero-day in Microsoft products? Unpatched for months while exploits circulate for months? So the Microsoft shills focus on the something that is “open source”… and repeat endlessly the terms which aren’t even applicable to it.

“CISA is a Microsoft reseller working out of the DHS offices,” our associated concluded, “which itself is a fraud.”

Hostile Microsoft-backed Media Blames “Linux” for Hardware-destroying Intel Driver Bug

Posted in Deception, FUD, GNU/Linux, Hardware, Microsoft at 12:41 am by Guest Editorial Team

Reprinted with permission from Ryan

The hostile Microsoft-backed tech media has been blaming “Linux” for trouble that Intel caused which could destroy Intel hardware.

It all started last week when Intel asked Greg KH, the stable Linux kernel series branch maintainer, to bring in a patch series to better handle display power saving.

The problem was that they only marked part of the patch series for backport and what ended up in Linux 5.19.12 was a half-broken mess that was entirely the fault of Intel.

Users on bleeding edge GNU/Linux distributions, which included this author, brought in Linux 5.19.12 thinking nothing of it.

Fortunately, the problem (flickering display that may cause hardware damage) did not appear to happen to my Gen11 Tiger Lake laptop with Intel IRIS Xe graphics.

I did start experiencing some weird glitches across the system though which freaked me out wondering if they were hardware failure.

My left Ctrl key started working intermittently and my laptop kept forgetting it was plugged in and running on the battery.

Bringing in Linux 5.19.13, which reverted the changes, seems to have resolved whatever the hell was going on. So perhaps Intel caused other problems too.

Not like they’re ever going to admit that.

Intel’s products are fairly buggy.

My other system is a “Skylake” laptop, and that was the buggiest damned thing ever.

My favorite moment on that system was when I had to version lock myself to an outdated kernel in Fedora because Intel decided to turn off the power management to the GPU to try to fix a low impact security hole, and then after leaving it broken for months, gave up trying to fix the hole and turned power management back on.

Whatever Intel wants, Intel gets.

Then they get the “tech media” to “Just Blame Linux” after Intel’s “engineers” screw everything up.

In a way, they are kind of right. -drivers subsystem people, I say “people” but it’s mostly hardware companies and Microsoft, get away with murder, and it’s been like that for a while.

Linus takes the view of giving them a wide berth because if they screw up they just make a big damned problem for their users.

While that may be sort of true, it just ends up giving “Linux” more PR damage when all of the barely informed “press”, who mostly just know how to take Microsoft money to slander Free Software (where everything is also “Linux” you know, even if it isn’t), run the story.

The environment Linus created by allowing hardware companies to do whatever they want in the -drivers tree to get more drivers and marketshare is creating a quality control disaster.

OpenBSD insists on code quality audits, and that slows things down and results in missing drivers. Then people don’t use it, because “Linux has drivers”.

Then shit like this happens, with the drivers.

If you’re wondering how Intel can be so clumsy and stupid that they stopped halfway into their patch series and told Greg KH to backport it, so am I.

Maybe their buddies at Microsoft needed a fresh anti-Linux kerfuffle. That’s just conjecture, though.

Maybe they really are that stupid.

Most of their product bugs affect Windows too, not that you’d notice. Windows is already such a piece of shit you’d be hard pressed to tell where the software problems end and hardware problems begin.

Unlike Windows, GNU/Linux is generally so reliable that you notice when there’s a hardware problem and it really grabs your attention.

Basically the only reason I bought Intel again is extreme cost cutting to try to make up for their customers fleeing to AMD. But is that a longterm strategy? I don’t think that it is.

And it’s not like you can trust AMD doesn’t have bugs. They do. They’re just not as severe.

Before Apple switched to ARM processors, they started putting enablement code in MacOS for a potential switch to AMD x86, which would have been far less painful for their users, but you know Apple…..

« Previous entries Next Page » Next Page »

RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channels: Come and chat with us in real time

New to This Site? Here Are Some Introductory Resources

No

Mono

ODF

Samba logo






We support

End software patents

GPLv3

GNU project

BLAG

EFF bloggers

Comcast is Blocktastic? SavetheInternet.com



Recent Posts