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 22/11/2014: Linux Mint 17.1, Ubuntu MATE

    Links for the day



  2. Links 21/11/2014: Problems at Debian, Jolla Tablet

    Links for the day



  3. Links 18/11/2014: Linux 3.18 RC 5, New DigiKam

    Links for the day



  4. Special Report: Many Criminal Charges Against EPO Vice-President Željko Topić

    The abuses of Željko Topić, who has gained notoriety in his home country, are rapidly becoming public knowledge across all of Europe



  5. Links 16/11/2014: Xfdesktop 4.10.3, GNU Hello 2.10

    Links for the day



  6. Microsoft is Going Into the Anti-Whistleblowing Business, Dodges Criticism Over 19-Year Bug Door in Windows

    With Aorato acquisition Microsoft helps protect the criminals (from whistleblowers) and with lies about .NET Microsoft distracts from a bug that has facilitated remote access into Windows (by those in the know) for nearly two decades



  7. Reaffirming Microsoft's Long-Known Hostility Towards Net Neutrality, Microsoft Crashed Juniper

    Steve Ballmer is ranting against net neutrality and Juniper's business is in trouble after a lot of executives from Microsoft took over most top positions there



  8. Another Massive Step Towards Elimination of Software Patents as Even CAFC Rules Against Them

    After SCOTUS gets involved in the Ultramercial case, the CAFC finally decides to actually serve justice rather than dogma



  9. The GOP's Patent Reform Plan Not Effective Enough to Stop Massive Patent Trolls Like Microsoft/Nokia

    The corporations-serving GOP says that it wants a patent reform, but another reminder is needed of the futility of the suggested changes



  10. How the EPO's Executive Branch (Battistelli and Topić) Banned Scrutiny and Created Authoritarian Model of Control: Part X

    A look at highly dubious moves by EPO President Battistelli and his right-hand man Topić, whose abuses are becoming hard to oversee or even report



  11. Links 15/11/2014: Linux Mint 17.1 Release Candidate, Popcorn Time 0.3.5

    Links for the day



  12. IRC Proceedings: October 26th, 2014 – November 8th, 2014

    Many IRC logs



  13. The Terrible Joke Which is Microsoft 'Loving' Linux: Nightmares With UEFI 'Secure' Boot (i.e. Windows Monopoly Imposed) Continue to Affect GNU/Linux Users

    A reminder of Microsoft's sheer hostility towards GNU/Linux and long-reaching sabotage of GNU/Linux installations



  14. Patent Lawyers Worry About Section 101 in 'Alice' (and Other Patent News)

    A quick roundup of news of interest regarding software patents



  15. Will Write for FUD (Against FOSS)

    Black Duck rears its ugly head again, serving to show that it is in the business of changing perceptions and not in the information or analysis business



  16. Debunking Several Days of Never-Ending Lies About Microsoft and .NET

    .NET is not "Open Source", it cannot be forked (there remains patent threat), Visual Studio is still completely proprietary and it is expected to come to other platforms only because Windows has lost its dominance and Microsoft wants to perpetually control APIs (with software patents) and hence reign over developers



  17. Links 14/11/2014: LibreOffice 4.3.4, Ads Now in Firefox

    Links for the day



  18. Links 14/11/2014: GNOME 3.14.2, PulseAudio 6.0

    Links for the day



  19. Microsoft Windows is Still Designed as a Paradise of Back Doors, Intrusion, Wiretaps, and Interception

    At many levels -- from communication to storage and encryption -- Windows is designed for the very opposite of security



  20. Forget the FUD About Bash and OpenSSL, Microsoft Windows Blamed for Massive Credit Cards Heist

    Home Depot learns its lesson from a Microsoft Windows disaster, but it stays with proprietary software rather than move to software that is actively audited by many people and is inherently better maintained (Free/libre software)



  21. Windows 'Update' and NSA Back Doors, Including a 19-Year Bug Door in Microsoft Windows

    The back doors-enabled Microsoft Windows is being revealed and portrayed as the Swiss cheese that it really is after massive holes are discovered (mostly to be buried by a .NET propaganda blitz)



  22. Revealed: Microsoft is Trying to Corrupt the UK in Order to Eliminate Its OpenDocument Format-Oriented Standards Policy

    Microsoft interference with Britain's preference for ODF is now confirmed, thanks to a valuable news report from Computer Weekly; OOXML lock-in is being unleashed by Microsoft on Android users



  23. Links 13/11/2014: Ubuntu MATE 14.04.1 LTS, New KDE Plasma

    Links for the day



  24. .NET is NOT "Open Source", But Microsoft's Minions Shamelessly Openwash It Right Now

    The openwashing of .NET continues with yet another publicity stunt that is intended to lock in developers



  25. Links 11/11/2014: GNOME Trademark Dispute Settled, Mozilla Embraces Tor

    Links for the day



  26. Patent Reform Subversion After Republican (GOP) 'Win' in US Senate

    The Grand Corporations Party, or the political party which serves large businesses that are funding it, continues to just focus on a mirage of a 'reform' rather than tackle the real issues where culprits include very large businesses such as Microsoft and Apple



  27. Microsoft-Armed Patent Troll MOSAID (Now Conversant) Wants to Sweep up More Patents for Litigation

    Reports about patent trolls and scope of patents serve to show what the foes of Free software are up to right now



  28. When Courts in the US Attack the Right to Reuse APIs

    Challenging the clueless ruling from the Court of Appeals for the Federal Circuit in the United States (very pro-software patents and anti-computer science), notable programmers write to the highest court



  29. Links 10/11/2014: 2015 GNU/Linux Forecasts, Debian Shakeup

    Links for the day



  30. Links 7/11/2014: War Thunder on GNU/Linux, KaOS ISO 2014.11

    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