EditorsAbout the SiteComes vs. MicrosoftUsing This Web SiteSite ArchivesCredibility IndexOOXMLOpenDocumentPatentsNovellNews DigestSite NewsRSS

10.16.13

Linux Backdoors Revisited (New Revelations and Old Revelations)

Posted in GNU/Linux, Kernel, Security at 10:43 am by Dr. Roy Schestowitz

Claude Elwood Shannon, the man who introduced entropy

Claude Elwood Shannon

Summary: An anonymous backdooring attempt against Linux goes a decade back, but a randomisation problem in today’s Linux also seems possible (subverting encryption)

Jonathan Allen wrote this article about an incident mentioned also by Freedom to Tinker. Slashdot’s summary goes like this, documenting news from one decade ago:

“Ed Felton writes about an incident, in 2003, in which someone tried to backdoor the Linux kernel. Back in 2003 Linux used BitKeeper to store the master copy of the Linux source code. If a developer wanted to propose a modification to the Linux code, they would submit their proposed change, and it would go through an organized approval process to decide whether the change would be accepted into the master code. But some people didn’t like BitKeeper, so a second copy of the source code was kept in CVS. On November 5, 2003, Larry McAvoy noticed that there was a code change in the CVS copy that did not have a pointer to a record of approval. Investigation showed that the change had never been approved and, stranger yet, that this change did not appear in the primary BitKeeper repository at all. Further investigation determined that someone had apparently broken in electronically to the CVS server and inserted a small change to wait4: ‘if ((options == (__WCLONE|__WALL)) && (current->uid = 0)) …’ A casual reading makes it look like innocuous error-checking code, but a careful reader would notice that, near the end of the first line, it said ‘= 0′ rather than ‘== 0′ so the effect of this code is to give root privileges to any piece of software that called wait4 in a particular way that is supposed to be invalid. In other words it’s a classic backdoor. We don’t know who it was that made the attempt—and we probably never will. But the attempt didn’t work, because the Linux team was careful enough to notice that that this code was in the CVS repository without having gone through the normal approval process. ‘Could this have been an NSA attack? Maybe. But there were many others who had the skill and motivation to carry out this attack,’ writes Felton. ‘Unless somebody confesses, or a smoking-gun document turns up, we’ll never know.’”

Backdoors in Linux are a subject for jokes in Torvalds' mind, but given the above we should take this subject very seriously. In any system, for example, having no mechanism for randomness (like in some embedded devices) typically means that strong encryption (with high entropy) is not possible. Given new alleged “insecurities in the Linux /dev/random,” as Bruce Schneier put it, Linux backdoors seem possible again. David Benfell said:

I’m guessing Schneier knows what the fuck he’s talking about. If it is the same vulnerability, then Torvalds’ defense is that the vulnerable source of entropy is only one of many. But if I read Schneier correctly, the result was still too predictable.

“On the other hand,” says Benfell, “here’s Theodore T’so from the comments:”

So I’m the maintainer for Linux’s /dev/random driver. I’ve only had a chance to look at the paper very quickly, and I will at it more closely when I have more time, but what the authors of this paper seem to be worried about is not even close to the top of my list in terms of things I’m worried about.

First of all, the paper is incorrect in some minor details; the most significant error is its (untrue) claim that we stop gathering entropy when the entropy estimate for a given entropy pool is “full”. Before July 2012, we went into a trickle mode where we only took in 1 in 096 values. Since then, the main way that we gather entropy, which is via add_interrupt_randomness(), has no such limit. This means that we will continue to collect entropy even if the input pool is apparently “full”.

This is critical, because *secondly* their hypothetical attacks presume certain input distributions which have an incorrect entropy estimate —| that is, either zero actual entropy but a high entropy estimate, or a high entropy, but a low entropy estimate. There has been no attempt by the paper’s authors to determine whether the entropy gathered by Linux meets either of their hypothetical models, and in fact in the “Linux Pseudorandom Number Generator Revisited”[1], the analysis showed that our entropy estimator was actually pretty good, given the real-life inputs that we are able to obtain from an actual running Linux system.

[1]http://eprint.iacr.org/2012/251.pdf

The main thing which I am much more worried about is that on various embedded systems, which do not have a fine-grained clock, and which is reading from flash which has a much more deterministic timing for their operations, is that when userspace tries to generate long-term public keys immediately after the machine is taken out of the box and plugged in, that there isn’t a sufficient amount of entropy, and since most userspace applications use /dev/urandom since they don’t want to block, that they end up with keys that aren’t very random. We had some really serious problems with this, which was written up in the “Mining Your Ps and Qs: Detection of Widespread Weak Keys in Network Devices” [2]paper, and the changes made in July 2012 were specifically designed to address these worries.

[2]https://www.factorable.net/paper.html

However, it may be that on certain systems, in particular ARM and MIPS based systems, where a long-term public key is generated very shortly after the first power-on, that there’s enough randomness that the techniques used in [2]would not find any problems, but that might be not enough randomness to prevent our friends in Fort Meade from being able to brute force guess the possible public-private key pairs.

Speaking more generally, I’m a bit dubious about academic analysis which are primarily worried about recovering from the exposure of the state of the random pool. In practice, if the bad guy can grab the state of random pool, they probably have enough privileged access that they can do many more entertaining things, such as grabbing the user’s passphrase or their long-term private key. Trying to preserve the amount of entropy in the pool, and making sure that we can extract as much uncertainty from the system as possible, are much higher priority things to worry about.

That’s not to say that I might not make changes to /dev/random in reaction to academic analysis; I’ve made changes in reaction to [2], and I have changes queued for the next major kernel release up to make some changes to address concerns raised in [1]. However, protection against artificially constructed attacks is not the only thing which I am worried about. Things like making sure we have adequate entropy collection on all platforms, especially embedded ones, and adding some conservatism just in case SHA isn’t a perfect random function are some of the other things which I am trying to balance as we make changes to /dev/random.

T’so, who is the former CTO of the Linux Foundation, at least acknowledges the possibility that there is a real issue here.

Share this post: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • del.icio.us
  • Reddit
  • co.mments
  • DZone
  • email
  • Google Bookmarks
  • LinkedIn
  • NewsVine
  • Print
  • Technorati
  • TwitThis
  • Facebook

If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

Pages that cross-reference this one

What Else is New


  1. Links 25/3/2017: Maru OS 0.4, C++17 Complete

    Links for the day



  2. Judge and Justice Bashing in the United States, EPC Bashing at the EPO

    Enforcement of the law based on constitutional grounds and based on the European Patent Convention (EPC) in an age of retribution and insults -- sometimes even libel -- against judges



  3. Looking for EPO Nepotism? Forget About Jouve and Look Closely at Europatis Instead.

    Debates about the contract of Jouve with the EPO overlook the elephants in the room, which include companies that are established and run by former EPO chiefs and enjoy a relationship with the EPO



  4. Depressing EPO News: Attacks on Staff, Attacks on Life, Brain Drain, Patents on Life, Patent Trolls Come to Germany, and Spain Being Misled

    A roundup of the latest developments at the EPO combined with feedback from insiders, who are not tolerating their misguided and increasingly abusive management



  5. It Certainly Looks Like Microsoft is Already Siccing Its Patent Trolls, Including Intellectual Ventures, on Companies That Use Linux (Until They Pay 'Protection' Money)

    News about Intellectual Ventures and Finjan Holdings (Microsoft-funded patent trolls) reinforces our allegations -- not mere suspicions anymore -- that Microsoft would 'punish' companies that are not paying subscription fees (hosting) or royalties (patent tax) to Microsoft and are thus in some sense 'indebted' to Microsoft



  6. Links 24/3/2017: Microsoft Aggression, Eudyptula Challenge Status Report

    Links for the day



  7. Bernhard Rapkay, Former MEP and Rapporteur on Unitary Patent, Shoots Down UPC Hopes While UPC Hopefuls Recognise That Spain Isn't Interested Either

    Germany, the UK and Spain remain massive barriers to the UPC -- all this in spite of misleading reports and fake news which attempted to make politicians believe otherwise (for political leverage, by means of dirty lobbying contingent upon misinformation)



  8. Links 23/3/2017: Qt 5.9 Beta, Gluster Storage 3.2

    Links for the day



  9. The Administrative Council of the European Patent Organisation Has Just Buried an Innocent Judge That Battistelli Does Not Like

    An innocent judge (never proven guilty of anything, only publicly defamed with help from Team Battistelli and dubious 'intelligence' gathering) is one of the forgotten casualties of the latest meeting of the Administrative Council (AC), which has become growingly complicit rather than a mere bystander at a 'crime' scene



  10. Nepotism at the European Patent Office and Suspicious Absence of Tenders for Big Projects

    Carte blanche is a French term which now perfectly describes the symptoms encountered in the European Patent Office, more so once led by a lot of French people (Battistelli and his friends)



  11. “Terror” Patent Office Bemoans Terror, Spreads Lies

    Response to some of the latest utterances from the European Patent Office, where patently untruthful claims have rapidly become the norm



  12. China Seems to be Using Patents to Push Foreign Companies Out of China, in the Same Way It Infamously Uses Censorship

    Chinese patent policies are harming competition from abroad, e.g. Japan and the US, and US patent policy is being shaped by its higher courts, albeit not yet effectively combating the element that's destroying productive companies (besieged by patent trolls)



  13. 22,000 Blog Posts

    A special number is reached again, marking another milestone for the site



  14. The EPO is Lying to Its Own Staff About ILO and Endless (Over 2 Years) EPO Mistrials

    The creative writing skills of some spinners who work for Battistelli would have staff believe that all is fine and dandy at the EPO and ILO is dealing effectively with staff complaints about the EPO (even if several years too late)



  15. EPO’s Georg Weber Continues Horrifying Trend of EPO Promoting Software Patents in Defiance of Directive, EPC, and Common Sense

    The EPO's promotion of software patents, even out in the open, is an insult to the notion that the EPO is adhering to or is bound by the rules upon which it maintains its conditional monopoly



  16. Protectionism v Sharing: How the US Supreme Court Decides Patent Cases

    As the US Supreme Court (SCOTUS) starts delivering some decisions we take stock of what's to come regarding patents



  17. Links 22/3/2017: GNOME 3.24, Wine-Staging 2.4 Released

    Links for the day



  18. The Battistelli Regime, With Its Endless Scandals, Threatens to Crash the Unitary Patent (UPC), Stakeholders Concerned

    The disdain and the growing impatience have become a huge liability not just to Battistelli but to the European Patent Office (EPO) as a whole



  19. The Photos the EPO Absolutely Doesn't Want the Public to See: Battistelli is Building a Palace Using Stakeholders' Money

    The Office is scrambling to hide evidence of its out-of-control spendings, which will leave the EPO out of money when the backlog is eliminated by many erroneous grants (or rejections)



  20. In the US Patent System, Evolved Tricks for Bypassing Invalidations of Software Patents and Getting Them Granted by the USPTO

    A roundup of news about patents in the US and how the patent microcosm attempts to patent software in spite of Alice (high-impact SCOTUS decision from 2014)



  21. “Then They Came For Me—And There Was No One Left To Speak For Me.”

    The decreasing number of people who cover EPO scandals (partly due to fear, or Battistelli's notorious "reign of terror") and a cause for hope, as well as a call for help



  22. As Expected, the Patent Microcosm is Already Interfering, Lobbying and Influencing Supreme Court Justices

    The US Supreme Court (SCOTUS) is preparing to deliver some important decisions on cases with broad ramifications, e.g. for patent scope, and those who make money from patent feuds are attempting to alter the outcome (which would likely restrict patent scope even further, based on these Justices' track record)



  23. Intellectual Ventures -- Like Microsoft (Which It Came From) -- Spreads Patents to Manifest a Lot of Lawsuits

    That worrisome strategy which is passage of patents to active (legally-aggressive) trolls seems to be a commonality, seen across both Microsoft and its biggest ally among trolls, which Microsoft and Bill Gates helped create and still fund



  24. What the Patent Microcosm is Saying About the EPO and the UPC

    Response to 3 law firms and today's output from them, which serves to inform or misinform the European public at times of Big Lies and fog of (patent) war, revealing the true nature of 21st century asymmetric patent warfare and lobbying



  25. Tough Day for the EPO's Media/Press/PR Team, Trying 'Damage Control' After Important Techrights Publications

    In an effort to save face and regain a sense of legitimacy the EPO publishes various things belatedly, and only after Techrights made these things publicly known and widely discussed



  26. Links 21/3/2017: PyPy Releases, Radeon RX Vega, Eileen Evans at Linux Foundation

    Links for the day



  27. In IAM, Asian Courts That Deliver Justice Are “Unfriendly” and Asian Patent Trolls Are Desirable

    Rebuttal or response to the latest pieces from IAM, which keeps promoting a culture of litigation rather than sharing, collaboration, negotiation, and open innovation



  28. At EPO “I Have the Feeling That Lowering Quality is Part of a Concerted Plan.”

    Growing concern about patent quality at the EPO -- a subject which causes managers to get rather nervous -- is now an issue at the forefront



  29. EPO Reduces the World to Just Seven Nations to Bolster an Illusion of Growing 'Demand' for European Patents

    The unscientific -- if not antiscientific -- attitude of the European Patent Office (EPO) continues to show with the arrival of yet more misleading 'infographics' (disinfographics would be a more suitable term)



  30. Letter to Angela Merkel Expresses Concerns About Impact of EPO Scandals on Germany and Its Image

    Dr. Angela Merkel, arguably the most powerful woman in the world, is being warned about the consequences of Germany ignoring (and hence facilitating) the abuses of Benoît Battistelli


CoPilotCo

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 Channel: Come and chat with us in real time

CoPilotCo

Recent Posts