Language Selection

English French German Italian Portuguese Spanish

IBM a reluctant user of Wine software

Filed under
Software

IBM's effort to promote Linux as a viable alternative on the company's 350,000 corporate desktops took a step forward last month, when the company's IT organization began supporting the open-source Firefox browser. However, while the move to support a browser that runs on Linux may provide a boost for both Firefox and IBM's internal Linux effort, Big Blue hasn't been nearly so eager to promote a lesser-known piece of software, called Wine, that it has used to advance Linux on the desktop.

Like Firefox, Wine is open-source software that provides an important piece of the Linux desktop puzzle. IBM's reluctance to promote Wine underscores some of the complex legal and technical issues surrounding Linux adoption.

The Wine software essentially masquerades as the Windows operating system, letting software that was written for Windows run on a Linux desktop. IBM employees have used it internally as a way of running the Lotus Notes desktop client, according to sources familiar with IBM's efforts, who say that Wine and the Notes client are part of the Linux version of IBM's standard desktop client, called the Client for eBusiness. IBM's goal is to have all their internal users running Linux, but they have not publicly said how many users currently run the operating system.

But trying to get IBM to talk about Wine is another thing entirely. IBM executives declined to comment on the company's use of Wine for this article, and while the software is mentioned occasionally on IBM's Web site, it is generally not endorsed as a tool for moving Windows desktops to Linux. Last year, IBM raised eyebrows in the Wine community by pulling an article describing the use of Wine from its DeveloperWorks Web site.

An IBM "Redbook" guide to Linux desktop migration, published in late 2004 contains one of the company's few public statements on the software. But even there, Wine is mentioned only in passing, in a section entitled "What to do if all else fails," and it is called a "temporary workaround" to get an application running on the Linux client. "This is not a solution for the long run," the guide states.

This unwillingness to publicly support Wine has frustrated Jeremy White, whose company CodeWeavers Inc. sells a commercial version of Wine.

"What they're doing is they're chilling the high-end migration opportunities for me," White said. "What I find galling is that they use it. I have tons of friends at IBM who use Wine every day to run Lotus Notes."

Part of the problem for White is that IBM has been reluctant to say what, if any, problems it has with the software. "I suspect it's legal issues or an OS/2 allergy," said White, referring to IBM's desktop operating system, which the company has stopped supporting. "Maybe they've got a deal with Bill Gates."

IBM's answer is more simple than that, according to Scott Handy, vice president of worldwide Linux strategy with IBM. IBM wants to promote open standards, like the Web-based protocols used in its Lotus Workplace suite of collaboration software, rather than the Microsoft APIs (application programming interfaces) used by Wine, he said.

"Our whole strategy revolves around Workplace, and we think one of the critical elements to Linux being successful is that we provide an open programming model," he said.

But Workplace uses new technologies like J2EE (Java 2 Enterprise Edition) that are unfamiliar to many long-time Notes developers, and it may be years before IBM's open-standards vision is embraced by the majority of Notes developers.

Until then, many Notes users will need either open-source software like Wine, or proprietary tools like the Citrix Systems Inc. MetaFrame server or VMware Inc.'s virtual machine software, in order to run Notes on their desktops.

The "legal issue" that White mentions may play a part as well. After all, IBM is already engaged in protracted litigation with The SCO Group Inc. over intellectual property claims relating to Linux.

Because Wine's purpose is to interoperate with Microsoft Corp.'s Windows platform, the project is in a special situation, said Eben Moglen, a law professor at Columbia University and the chairman of the Software Freedom Law Center, an organization dedicated to providing free legal services to open source developers.

Observers fear that Wine, by emulating the Windows operating system, could somehow find itself running afoul of Microsoft's thousands of software patents.

"People have reason to expect that there may be fear for uncertainty and doubt in connection with that interoperability layer," Moglen said.

Last month, the Wine project became a client of the Software Freedom Law Center, which is providing legal analysis and counsel to the open-source project. One of the most important effects of this relationship, Moglen believes, is that companies like IBM will view Wine as a less risky option.

"I believe that improved legal assurance will improve acceptance of and help acceleration of the use of Wine," Moglen said. "You are not likely to see a SCO-type lawsuit connected with any software connected with any client of mine... unless I have fallen down on the job completely."

By Robert McMillan
IDG News Service

More in Tux Machines

Security: OpenSSL, IoT, and LWN Coverage of 'Intelpocalypse'

  • Another Face to Face: Email Changes and Crypto Policy
    The OpenSSL OMC met last month for a two-day face-to-face meeting in London, and like previous F2F meetings, most of the team was present and we addressed a great many issues. This blog posts talks about some of them, and most of the others will get their own blog posts, or notices, later. Red Hat graciously hosted us for the two days, and both Red Hat and Cryptsoft covered the costs of their employees who attended. One of the overall threads of the meeting was about increasing the transparency of the project. By default, everything should be done in public. We decided to try some major changes to email and such.
  • Some Basic Rules for Securing Your IoT Stuff

    Throughout 2016 and 2017, attacks from massive botnets made up entirely of hacked [sic] IoT devices had many experts warning of a dire outlook for Internet security. But the future of IoT doesn’t have to be so bleak. Here’s a primer on minimizing the chances that your IoT things become a security liability for you or for the Internet at large.

  • A look at the handling of Meltdown and Spectre
    The Meltdown/Spectre debacle has, deservedly, reached the mainstream press and, likely, most of the public that has even a remote interest in computers and security. It only took a day or so from the accelerated disclosure date of January 3—it was originally scheduled for January 9—before the bugs were making big headlines. But Spectre has been known for at least six months and Meltdown for nearly as long—at least to some in the industry. Others that were affected were completely blindsided by the announcements and have joined the scramble to mitigate these hardware bugs before they bite users. Whatever else can be said about Meltdown and Spectre, the handling (or, in truth, mishandling) of this whole incident has been a horrific failure. For those just tuning in, Meltdown and Spectre are two types of hardware bugs that affect most modern CPUs. They allow attackers to cause the CPU to do speculative execution of code, while timing memory accesses to deduce what has or has not been cached, to disclose the contents of memory. These disclosures can span various security boundaries such as between user space and the kernel or between guest operating systems running in virtual machines. For more information, see the LWN article on the flaws and the blog post by Raspberry Pi founder Eben Upton that well describes modern CPU architectures and speculative execution to explain why the Raspberry Pi is not affected.
  • Addressing Meltdown and Spectre in the kernel
    When the Meltdown and Spectre vulnerabilities were disclosed on January 3, attention quickly turned to mitigations. There was already a clear defense against Meltdown in the form of kernel page-table isolation (KPTI), but the defenses against the two Spectre variants had not been developed in public and still do not exist in the mainline kernel. Initial versions of proposed defenses have now been disclosed. The resulting picture shows what has been done to fend off Spectre-based attacks in the near future, but the situation remains chaotic, to put it lightly. First, a couple of notes with regard to Meltdown. KPTI has been merged for the 4.15 release, followed by a steady trickle of fixes that is undoubtedly not yet finished. The X86_BUG_CPU_INSECURE processor bit is being renamed to X86_BUG_CPU_MELTDOWN now that the details are public; there will be bug flags for the other two variants added in the near future. 4.9.75 and 4.4.110 have been released with their own KPTI variants. The older kernels do not have mainline KPTI, though; instead, they have a backport of the older KAISER patches that more closely matches what distributors shipped. Those backports have not fully stabilized yet either. KPTI patches for ARM are circulating, but have not yet been merged.
  • Is it time for open processors?
    The disclosure of the Meltdown and Spectre vulnerabilities has brought a new level of attention to the security bugs that can lurk at the hardware level. Massive amounts of work have gone into improving the (still poor) security of our software, but all of that is in vain if the hardware gives away the game. The CPUs that we run in our systems are highly proprietary and have been shown to contain unpleasant surprises (the Intel management engine, for example). It is thus natural to wonder whether it is time to make a move to open-source hardware, much like we have done with our software. Such a move may well be possible, and it would certainly offer some benefits, but it would be no panacea. Given the complexity of modern CPUs and the fierceness of the market in which they are sold, it might be surprising to think that they could be developed in an open manner. But there are serious initiatives working in this area; the idea of an open CPU design is not pure fantasy. A quick look around turns up several efforts; the following list is necessarily incomplete.
  • Notes from the Intelpocalypse
    Rumors of an undisclosed CPU security issue have been circulating since before LWN first covered the kernel page-table isolation patch set in November 2017. Now, finally, the information is out — and the problem is even worse than had been expected. Read on for a summary of these issues and what has to be done to respond to them in the kernel. All three disclosed vulnerabilities take advantage of the CPU's speculative execution mechanism. In a simple view, a CPU is a deterministic machine executing a set of instructions in sequence in a predictable manner. Real-world CPUs are more complex, and that complexity has opened the door to some unpleasant attacks. A CPU is typically working on the execution of multiple instructions at once, for performance reasons. Executing instructions in parallel allows the processor to keep more of its subunits busy at once, which speeds things up. But parallel execution is also driven by the slowness of access to main memory. A cache miss requiring a fetch from RAM can stall the execution of an instruction for hundreds of processor cycles, with a clear impact on performance. To minimize the amount of time it spends waiting for data, the CPU will, to the extent it can, execute instructions after the stalled one, essentially reordering the code in the program. That reordering is often invisible, but it occasionally leads to the sort of fun that caused Documentation/memory-barriers.txt to be written.

US Sanctions Against Chinese Android Phones, LWN Report on Eelo

  • A new bill would ban the US government from using Huawei and ZTE phones
    US lawmakers have long worried about the security risks posed the alleged ties between Chinese companies Huawei and ZTE and the country’s government. To that end, Texas Representative Mike Conaway introduced a bill last week called Defending U.S. Government Communications Act, which aims to ban US government agencies from using phones and equipment from the companies. Conaway’s bill would prohibit the US government from purchasing and using “telecommunications equipment and/or services,” from Huawei and ZTE. In a statement on his site, he says that technology coming from the country poses a threat to national security, and that use of this equipment “would be inviting Chinese surveillance into all aspects of our lives,” and cites US Intelligence and counterintelligence officials who say that Huawei has shared information with state leaders, and that the its business in the US is growing, representing a further security risk.
  • U.S. lawmakers urge AT&T to cut commercial ties with Huawei - sources
    U.S. lawmakers are urging AT&T Inc, the No. 2 wireless carrier, to cut commercial ties to Chinese phone maker Huawei Technologies Co Ltd and oppose plans by telecom operator China Mobile Ltd to enter the U.S. market because of national security concerns, two congressional aides said. The warning comes after the administration of U.S. President Donald Trump took a harder line on policies initiated by his predecessor Barack Obama on issues ranging from Beijing’s role in restraining North Korea to Chinese efforts to acquire U.S. strategic industries. Earlier this month, AT&T was forced to scrap a plan to offer its customers Huawei [HWT.UL] handsets after some members of Congress lobbied against the idea with federal regulators, sources told Reuters.
  • Eelo seeks to make a privacy-focused phone
    A focus on privacy is a key feature being touted by a number of different projects these days—from KDE to Tails to Nextcloud. One of the biggest privacy leaks for most people is their phone, so it is no surprise that there are projects looking to address that as well. A new entrant in that category is eelo, which is a non-profit project aimed at producing not only a phone, but also a suite of web services. All of that could potentially replace the Google or Apple mothership, which tend to collect as much personal data as possible.

today's howtos

Mozilla: Resource Hogs, Privacy Month, Firefox Census, These Weeks in Firefox

  • Firefox Quantum Eats RAM Like Chrome
    For a long time, Mozilla’s Firefox has been my web browser of choice. I have always preferred it to using Google’s Chrome, because of its simplicity and reasonable system resource (especially RAM) usage. On many Linux distributions such as Ubuntu, Linux Mint and many others, Firefox even comes installed by default. Recently, Mozilla released a new, powerful and faster version of Firefox called Quantum. And according to the developers, it’s new with a “powerful engine that’s built for rapid-fire performance, better, faster page loading that uses less computer memory.”
  • Mozilla Communities Speaker Series #PrivacyMonth
    As a part of the Privacy Month initiative, Mozilla volunteers are hosting a couple of speaker series webinars on Privacy, Security and related topics. The webinars will see renowned speakers talking to us about their work around privacy, how to take control of your digital self, some privacy-security tips and much more.
  • “Ewoks or Porgs?” and Other Important Questions
    You ever go to a party where you decide to ask people REAL questions about themselves, rather than just boring chit chat? Us, too! That’s why we’ve included questions that really hone in on the important stuff in our 2nd Annual Firefox Census.
  • These Weeks in Firefox: Issue 30