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 31/8/2015: Linux 4.2, LXLE 14.04.3

    Links for the day



  2. IRC Proceedings: August 9th, 2015 – August 29th, 2015

    Many IRC logs



  3. “Conservative” Site Responds (Yet Again) to Misguided “Conservative” Efforts to Derail Patent Reform in the US

    Patent trolls throw stones in glass houses, contributing to their own unpopularity, but some influential “Conservatives” continue to defend (conserve) them



  4. Increase in Lobbying for Software Patents in Europe and Its Trojan Horse, the Unitary Patent (UPC)

    The relentless campaigns to bring software patents into Europe have not stopped and so-called 'unification' -- much like so-called 'trade' deals -- serves to support them



  5. Microsoft Technology Crashes Financial Markets, Again

    SunGard, which is a Microsoft shop, is clearly failing to provide what it calls mission-ciriticaal [sic] solutions



  6. Alice v. CLS Bank (Alice/§101) Comes to Squash Software Patents Even in Eastern District of Texas

    The crackdown on software patents is coming along nicely and the Alice case is now being utilised even in the capital of patent trolls



  7. Apple's Patent Cases Against Android Are Falling Apart, as Acknowledged Even by the Anti-Android Lobby





  8. Links 29/8/2015: NetworkManager 1.0.6, Systemd Merges “su” Command Replacement

    Links for the day



  9. Microsoft Loves Linux to Death and Still Tries to Kill GNU/Linux

    Microsoft's relentless attacks on GNU/Linux and Free software in general (even if it runs on Windows) are so evident that claims of 'love' remain laughable at best (if not infuriating)



  10. Censorship, Self-Censorship and Intimidation Now the Modus Operandi at EPO

    The European Patent Office has ceased even trying to pretend that it respects human rights, including the right to free speech



  11. Patent Practitioners: "The Unitary Patent Might be Able to Open the Floodgates for Software Patents in Europe"

    The EPO-backed Unitary Patent scheme threatens to bring software patents to Europe and along with them a lot of patent trolls from all around the world (especially the United States)



  12. Microsoft Lies About Vista 10 and Increases Microsoft Surveillance (Even Beyond Vista 10 and Into Android, Vista 7/8)

    Windows surveillance expands retroactively, making its way into platforms other than Windows and also expanding to predecessors of Vista 10



  13. Another Suicide at the EPO, Fifth by Our Count

    Yet another EPO member of staff has just committed suicide, leading to the inevitable question: how many people need to die before Battistelli and his minions are out of the Office for good?



  14. Links 27/8/2015: ownCloud Desktop Client 2.0, Red Hat Downgraded

    Links for the day



  15. Microsoft-connected Mesosphere Threatens to Eliminate Free Software in the Datacentre

    Hiding behind a misleading 'open' label while actually backed by Microsoft (and based on new rumours may join Microsoft), Mesosphere wishes to eradicate Free and back doors-free software in large datacentres hosting a lot of physical and virtual servers



  16. Microsoft Aggression Against GNU/Linux Amid Vista 10's Failure

    A look at the recent assault on GNU/Linux in Munich and the likely cause for this assault (in such a timely fashion, too)



  17. Message to LinuxCon Regarding Microsoft: “It is Necessary to Get Behind Someone in Order to Stab Them in the Back.” -Sir Humphrey Appleby

    Jim Zemlin, executive director of the Linux Foundation, helps Microsoft gain influence in the Foundation after payments are received



  18. Market Share Estimates Confirm That Vista 10 Failed in a Major Way

    Confirmatory evidence that Vista 10 is failing in the market about a month after its much-hyped (paid coverage) release



  19. When Microsoft, the Master of Patent Trolls, Complains About Trolls

    Possibly the world's biggest patent abuser and monopolist, which also creates many patent trolls (including by far the biggest one), takes on a far smaller abuser in Court



  20. Letter Signed by Two German Officials Becomes a Microsoft Weapon of Propaganda

    Microsoft and its minions refuse to leave Munich alone, even though the vast majority in Munich are perfectly happy with Free/libre software



  21. Links 25/8/2015: Linux Kernel 4.2 Final RC, KDE Ships Plasma 5.4.0

    Links for the day



  22. Sabine Pfeiler and Otto Seidl Should Take Note as Russia -- Like China -- is in the Process of Banning Microsoft Windows for Security Reasons

    A look at a strange suggestion, signed by Sabine Pfeiler and Otto Seidl, who suggest going back to Microsoft which is basically a spyware company now



  23. Microsoft Windows Leads to Espionage and Blackmail: Latest Examples

    Another news overview, detailing high-profile examples of high-cost Windows deployments (including the cost of litigation and settlement)



  24. Links 23/8/2015: BcacheFS Benchmarks, Blackphone 2

    Links for the day



  25. Links 22/8/2015: Chromebook Gains, GNOME 3.18 Clues

    Links for the day



  26. Alice v. CLS Bank (the Alice Case/§101) Continues to Crush Software Patents in the United States

    Patent scope in the United States continues to be narrowed down as more software patents get their wings clipped



  27. Company of Hype and 'Fanbois' Continues Its Patent Attacks on Android/Linux

    Apple's attacks on Android (using bogus patents) may be soon be escalated to the US Supreme Court (SCOTUS)



  28. EPO Corruption of Patent Boundaries: Business Methods and Algorithms Patented

    How the European Patent Office (EPO) not only turns a blind eye to European law while patenting or granting patents on software but also openly advocates this now



  29. Who's Obsessing Over Patent Trolls in Latest 'Reform' Efforts? Larger Patent Trolls Such as Xerox

    Response to claims that the patent problem is being tackled by focusing on patent trolls and their favourite courts in the Eastern District of Texas



  30. Links 20/8/2015: Fedora 24 Plans, Ubuntu Phones in India

    Links for the day


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