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 23/5/2015: Fedora 22 to May 26th, Netflix in SteamOS

    Links for the day



  2. The Patents Production 'Industry' (Patent Lawyers) Still Fights Hard to Salvage Software Patents

    A review of recent writings about software patents and patents on business methods in the United States, demonstrating that patent lawyers have gotten very vocal and sneaky (trying to evade the rules)



  3. Patents as a Marketing Strategy: USPTO Now Part of the Advertising Industry

    The existence of publicity patents, or patents whose sole purpose is to advertise some products, serves to discredit the US patent office, which was originally set up to promote science and technology



  4. Microsoft Blackmails and Extorts British Politicians Over Open Standards and Free Software-Leaning Policies

    Microsoft's digital imperialism in the UK getting defended using blackmail, reminding a lot of Brits that Microsoft is just as evil as ever before



  5. Microsoft Gives Another Bug a Name, This Time Logjam™

    The Microsoft crowd is good only at marketing, even when it comes to small bugs in software



  6. Links 22/5/2015: Fedora 22 Final Release is Near, Canonical IPO Considered

    Links for the day



  7. More Utter Shame Unveiled at Battistelli's EPO: Intimidation Tactics With Help From 'Control Risks'

    The unaccountable thugs who run the EPO have hired London-based spooks to help silence their opposition and their critics



  8. GNU/Linux Still Under Attack From Apple and Microsoft, Patents Remain the Weapon of Choice

    A timely reminder of the importance of patent matters, for they are being used to eliminate the zero-cost advantage of Free/libre software and make it more proprietary, privacy-infringing, and user-hostile (as a result of blackmail)



  9. Gartner Group and NASSCOM: Will Lie for FUD, on Behalf of Microsoft and Proprietary Software

    Some of the latest arguments against Free/libre software turn out to be arriving from couriers of Microsoft and its agenda



  10. Windows is a Franchise in Demise, Don't Believe the Hype

    Ongoing propaganda about Vista 10, 'cloud', and other buzzwords or brands are put in perspective



  11. Links 21/5/2015: Fedora 22 RC2, CERN Chooses OpenStack

    Links for the day



  12. Microsoft is Again Showing Its Hatred of Free/Open Source Software by Lobbying the Indian Government to Drop a Rational National Policy

    Microsoft decides to attack Free/Open Source software (FOSS) in India, where the corporate media is very much complicit in misleading the public



  13. Links 20/5/2015: Containers, OpenStack, and EXT4 Corruption

    Links for the day



  14. The PATENT Act, Distraction of Trolls, and Lobbying for Software Patents by Protectionists

    Only large corporations and their lawyers are able to formally change the US patent system through public officials and politicians, despite recent rulings from very high courts



  15. Corporate Media and Friends of Microsoft Are Still Lying About the Cost of Vista 10

    In a desperate effort to beat operating systems that are Free (libre) and free (gratis), such as GNU/Linux or Android, Microsoft shores up the illusion of 'free' (gratis) Windows



  16. Links 19/5/2015: Linux 4.1 RC4, Thunderbird 31.7.0, OpenStack Event

    Links for the day



  17. Links 18/5/2015: Russia Chooses Jolla, Many New Distro Releases, Meizu Devices

    Links for the day



  18. Even Converting an Image to Greyscale is Now a Patent

    Simple mathematics becoming patented as Fujifilm claims 'ownership' of photographic conversion to greyscale



  19. Grooming of the World's Biggest Patent Troll, Nathan Myhrvold of Microsoft and Intellectual Ventures

    UCLA and Microsoft-linked media are framing big thugs as heroes, doing a great disservice to both academia and journalism



  20. The EPO's Fight to Bring Software Patents Into Europe is One Step Closer to a 'Victory' (for Multinationals)

    Opposition to the Unified Patent Court (UPC) is being crushed and Italy is one of the latest actors to have fallen in the battle



  21. Microsoft's 'Former' Staff Continues With His Anti-Google Rhetoric at CBS

    A Microsoft intern, who has moved on to journalism, is still showing his affinity for Microsoft with apologetics and spin



  22. More of Microsoft's False Claims About Cost of Vista 10 and More Layoffs

    Vista 10 is still being marketed using lies and Microsoft may be going down the same route as Nokia



  23. Microsoft Remotely Bricks -- Intentionally -- Xbox One

    Microsoft is showing off its kill switches, kills consoles of people whom it doesn't like



  24. IRC Proceedings: May 3rd - May 16th, 2015

    Many IRC logs



  25. Links 17/5/2015: NuTyX Saravane 15.05, Panasonic and Firefox OS

    Links for the day



  26. Links 16/5/2015: MAME Free Software. Rust 1.0, New Wine

    Links for the day



  27. Links 15/5/2015: GNOME 3.16.2, GNU Guix 0.8.2

    Links for the day



  28. Links 15/5/2015: Skrooge Releases, Linux 3.14.42, Linux 3.10.78

    Links for the day



  29. "VENOM" FUD Attack -- Like "Heartbleed" FUD Attack -- Linked to Microsoft

    Why CrowdStrike™ is motivated to smear Free software and establish a stigma of insecurity in Free software-based virtual machines/'clouds'



  30. Spinning Microsoft's Inability to Sell Windows (or Office) as a Strength

    The 'cloud' mindset, which is promoted by surveillance fanatics, increasingly used to pretend that Microsoft has a bright future, despite declining sales


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