Defender of the Linux faith

Ingrid Marson, ZDNet UK
18 March 2005 12:36 PM
Tags: harald welte, linux, gpl, violate
update Earlier this week, open source developer Harald Welte personally handed over warning letters to 13 technology companies at the CeBIT technology show in Hannover, Germany, including telecoms giant Motorola and PC manufacturer Acer.

Welte is one of the core developers of the Linux kernel firewall engine Netfilter/iptables and the maintainer of the packet filter subsystem in the Linux kernel. In 2004, he set up gpl-violations.org, which aims to prevent companies from contravening the rules set down in the GNU General Public License.

Since setting up the project, Welte has made 25 agreements with companies that were violating the GPL, as well as setting up two preliminary injunctions and one court order. Each of these companies used GPL code in products they distributed without making the source code available, as is required by the licence.

ZDNet UK  spoke to Welte about tracking down those companies that violate the GPL and how he persuades them to comply.

Q: Why is it important to stop people from violating the GPL?
Welte: You can use all the code out there for free, but if you do modifications you have to give them back to the community -- it's a fairness thing. If we allowed violations to become common, the system would be out of equilibrium. This would result in fewer contributions and it would have a large negative impact on the motivation of developers.

How do you find out whether companies have used GPL licensed code?
It's quite hard without having the source code. All you can do is look at the firmware with a hex editor. You can often spot error messages or function names from GPL-licensed code. For example, there is an error message in the Netfilter code that says, "Rusty needs more caffeine." If someone writes a firewall they are very unlikely to come up with the same error message.

If somebody wants to obfuscate the fact that they have used the [GPL-licensed] source code, they can write a program to automatically change the error messages or strings. But if they try to hide it, it's a wilful copyright violation, which is a more serious legal offence.

What happens when you tell companies that they are violating the GPL?
Lots of companies that we are going after are resellers, so even if the device is sold as Fujitsu Siemens, it's not made by them, but is an OEM device. With resellers it's easier as we simply tell them, and they then put pressure on their upstream vendors.

In some cases we got an out-of-court agreement and the company agreed to stop distributing software that doesn't comply with the GPL licence, but then did it again. This happened with Belkin and Netgear -- half a year after signing the agreement, they introduced new products that came without any indication of source code availability. This has now been sorted out and they are fully compliant.

In general, we haven't had trouble persuading companies to comply, apart from [PC connectivity company] Sitecom.

What happened with Sitecom?
When we found out about Sitecom's GPL violation, my lawyer asked them to sign a declaration to stop distributing software that didn't comply with the GPL licence. We didn't receive their signed declaration within the deadline, so we applied for a preliminary injunction. After they received the injunction they filed an appeal. The court ruled that it will uphold the preliminary injunction.

Even though you have won every case so far, surely there's potential cost involved in pursuing these cases?
There is a cost of 10,000 euros (AU$16,892) per case, although the party who loses the case pays all the legal fees. It's not that I have that amount of money spare, but it's worth the risk.

Continued ...

Advertisement

Talkback 3 comments

    "Each of these companies used GPL code without making the source code available" is no violation of the license. Modifying and not publishing the changes is.Anonymous -- 18/03/05

    "Each of these companies used GPL code without making the source code available" is no violation of the license.

    Modifying and not publishing the changes is.

    This fellow is so right. I think the OSS community needs viable mechanism, including those legal to stop those violating GPL. This guy is one of the first among those who will establish such a mechanism and I will help them. keep up the good worAnonymous -- 18/03/05

    This fellow is so right. I think the OSS community needs viable mechanism, including those legal to stop those violating GPL.
    This guy is one of the first among those who will establish such a mechanism and I will help them.
    keep up the good work!

    " you have to give them back to the community" This is not correct. The GPL states that the source code must, essentially, accompany the object code. It does not say that "the community", or the world, for that matter must beAnonymous -- 19/03/05

    " you have to give them back to the community"

    This is not correct. The GPL states that the source code must, essentially, accompany the object code. It does not say that "the community", or the world, for that matter must be able to get a copy.

    This is a frequently frustrating feature for developers who have no right to receive the modified sources, unless, they have a right, say, through purchasing a product, to the the object files.

    The relevant part of the GPL is quoted below.

    "3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

    a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

    b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

    c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.) "

Add your opinion


Latest Videos

Blogs

  • Chris Duckett PayPal launches Aussie developer program
    PayPal announced the opening of its certification program for Australian developers today, making Australia the first country outside of the US to offer certification.
  • Array Cash cow in a BigTinCan?
    Around one third of Australia's telcos have shut their doors over time, but that isn't stopping new ventures hoping to chip away at carriers' mobile call bonanza. By fighting carriers at the smartphone rather than the home phone, could the latest two contenders be onto something big?
  • Array A third of the way to a zettabyte
    This week on Twisted Wire we look at how internet usage is changing in Australia and around the world. How are we meeting this demand and how is the cost structure changing for the service provider?
  • More blogs »

Tags

Back to top

Featured