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 18/4/2015: ExTiX 15.2, RaspArch

    Links for the day



  2. Microsoft Tired of Pretending to be Nice to Free/Open Source Software (FOSS), Microsoft 'Open' Technologies Dumped

    Microsoft dumps its proxy (misleadingly named 'Open Tech') and other attacks on Free software persist from the inside, often through so-called 'experts' whose agenda is to sell proprietary software



  3. More Translations of French Article About the EPO

    German and Dutch translations of the Le Monde article are now available



  4. Links 17/4/2015: Wipro and the Netherlands Want FOSS

    Links for the day



  5. Microsoft's Multi-Dimensional Assault on Android/Linux: Extortion, Lobbying of Regulators, and Bribes

    Microsoft's vicious war on Linux (and Android in its current incarnation) takes more sophisticated -- albeit illegal (as per the RICO Act) -- forms



  6. Microsoft's Plot to Associate Windows with 'Open Source' is Proving Effective, Despite Being Just a Big Lie

    A look at the latest headlines which can lead to a false perception that Microsoft is now in bed with 'Open Source'



  7. Microsoft Windows Remotely Crashed, Remotely Hijacked, But Still No Logo and No Branding for the Bugs

    Windows maintains its reputation as a back doors haven, but the media is still not highlighting the severity of this issue, instead focusing on accidental bugs in Free software, even very old (and already fixed) bugs



  8. Black Duck's Latest Self-Promotional Propaganda (for Proprietary Software) Still Fools Journalists

    Under the traditionally misleading title "Future of Open Source" Black Duck expresses its desire for proprietary software sales, salivating over fearful managers who may get bamboozled into buying the patents-'protected' Black Duck 'product'



  9. Links 16/4/2015: Opera for 32-bit GNU/Linux, New Chromebook Site

    Links for the day



  10. Links 15/4/2015: Plasma 5.3 Beta, Docker's New Funding

    Links for the day



  11. Microsoft is Still Googlebombing the Term Open Source and Fooling Politicians Who Now Think Microsoft is Open Source

    Microsoft's attempt to assimilate (to confuse) bears some fruit and the Microsoft-linked media plays a considerable role in it



  12. Back Doors/Bug Doors in All Versions of Microsoft Windows Need a Name, a Logo, and Branding Too

    All versions of Microsoft Windows are found to have been insecure since 1997, but the bug responsible for this is not named as candidate for back door access, let alone named (with logo and marketing) like far less severe bugs in Free/libre software such as OpenSSL



  13. OnePlus (or OnePlus Customers) Should Wipe CyanogenMod From Existing Devices and Install Something Else

    A call for OnePlus to reconsider any future updates from Microsoft's Trojan horse, Cyanogen



  14. Links 14/4/2015: 3DR Dronecode, Z1/Z2 Tizen

    Links for the day



  15. Links 13/4/2015: Linux 4.0 Released; A Look at Antergos 2015.04.12

    Links for the day



  16. EFF Uses Alice v. CLS Bank Case to Pressure USPTO to Halt Software Patenting

    A look at recent patent policies and actions from the EFF, as well as increasing secrecy at the USPTO



  17. No, Panasonic Did Not Open-Source Anything (Another Example of Openwashing for PR)

    A dissection of media deception (or media being bamboozled) regarding the act of promising not to sue using patents, which in no way relates to Free/Open Source software



  18. Yes, Software Patents Are Dying, But Media Continues to Be Dominated by Those Denying it For a Salary

    The debate about software patents in this post-Alice era parallels the Net neutrality debate, where voices of people with vested interests contribute to confusion and meddle with largely-accepted views/consensus



  19. Links 12/4/2015: Linux 4.0 Imminent, Semplice 7 Reviewed

    Links for the day



  20. GNU/Linux is Crushing Windows, So Microsoft Leaps Ahead to X+2 Vapourware (Two Versions Ahead Into the Future)

    Microsoft continues to pile up bogus claims and empty promises in an effort to stall migrations to GNU/Linux



  21. The ITC's and US Media's Surprisingly Soft Treatment of Patent Bully Apple

    Despite Apple's history of initiating patent aggression against its competition (mostly Android-backing companies), the US corporate media treats Apple like a victim



  22. Microsoft Continues to Attack (and Tax) Linux Using Software Patents

    Microsoft stabs Linux in the back while it continues to insist that it 'loves' Linux



  23. European Unitary Patent Decision Due 5th of May

    The meta-industry of patent protectionism is debating and pushing forth the Unitary Patent Court, with or without endorsement from the European public



  24. Microsoft is Still Googlebombing 'Open Source'

    Microsoft's massive campaign of deception, obfuscation and misuse of the "Open Source" brand is still on, even a week after it was cleverly started by Condé Nast



  25. Links 11/4/2015: elementary OS Freya, Mageia 5 on the Way

    Links for the day



  26. Links 10/4/2015: Linux 4.0 Imminent, ZFS On Linux Improved

    Links for the day



  27. New Article Chronicles Suicides and Nervous Breakdowns at the EPO Due to the Management's Abuses

    Article from Le Monde translated into English



  28. Links 9/4/2015: SalentOS, Semplice Releases

    Links for the day



  29. The EPO is Becoming More Like the USPTO Under Benoît Battistelli's Greed-Driven Reign

    Recent articles about the EPO and the Unitary Patent are bundled together to highlight truly disturbing developments whereby those in power beget power through instruments of state-sanctioned power, such as the EPO (stateless entity within a continent-wide 'island')



  30. More Suicides Reported at the Staff-Hostile European Patent Office

    The EPO has become so rogue that it might as well be renamed the Euthanasia-Prodding Organisation


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