Language Selection

English French German Italian Portuguese Spanish

License compliance issues could affect all BSD-derived distributions

Filed under
Legal

The Gentoo/FreeBSD project, which combines the FreeBSD kernel with Gentoo Linux design principles, is in a fix. Its lead developer, Diego "Flameeyes" Pettenò, discovered licensing issues while working on the libkvm library and the start-stop-daemon -- and Pettenò says that the problem might not be limited to his project, but could trap other BSD-derived projects as well.

"The licensing trouble began," says Pettenò, "when I looked up the license under which libkvm was released, as I was going to link into a GPLv2 software (portage-utils, a Gentoo-specific utilities package), and I found it using the four-clause BSD license (the original one, basically). When I looked up what else was using it, I found we were already redistributing a binary handled under GPLv2 license that could cause us issues." He immediately stopped public distribution of the project's files.

The license in question is the original BSD license, which was in use till 1999. One of its clauses, notoriously known as the advertising clause, requires all advertisements mentioning the software to include an acknowledgment sentence that credits the University of California, Berkeley, and its contributors for their efforts. This wasn't much of an issue until other developers started modifying the statement to credit themselves for their modifications. This becomes a headache when software with the same clause makes its way into an operating system like Gentoo/FreeBSD. In effect, it requires Gentoo/FreeBSD to reproduce every credit statement in all their advertisements.

Full Story.

re: Credit arguments did appear on Tuxmachines

Yeah, there was a big one one time over a distro develper that was accused of little more than copying (rebranding) another. It was ugly. In the end I unpublished most of the controversial content and comments, which kinda goes against my grain. But all parties agreed to that resolution, so what else can ya do.

----
You talk the talk, but do you waddle the waddle?

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Leftovers: OSS

Security Leftovers

  • Security updates for Thursday
  • OpenSSL patches two high-severity flaws
    OpenSSL has released versions 1.0.2h and 1.0.1t of its open source cryptographic library, fixing multiple security vulnerabilities that can lead to traffic being decrypted, denial-of-service attacks, and arbitrary code execution. One of the high-severity vulnerabilities is actually a hybrid of two low-risk bugs and can cause OpenSSL to crash.
  • Linux Foundation Advances Security Efforts via Badging Program
    The Linux Foundation Core Infrastructure Initiative's badging program matures, as the first projects to achieve security badges are announced.
  • Linux Foundation tackles open source security with new badge program
  • WordPress Plugin ‘Ninja Forms’ Security Vulnerability
    FOSS Force has just learned from Wordfence, a security company that focuses on the open source WordPress content management platform, that a popular plugin used by over 500,000 sites, Ninja Forms, contains serious security vulnerabilities.
  • Preparing Your Network for the IoT Revolution
    While there is no denying that IP-based connectivity continues to become more and more pervasive, this is not a fundamentally new thing. What is new is the target audience is changing and connectivity is becoming much more personal. It’s no longer limited to high end technology consumers (watches and drones) but rather, it is showing up in nearly everything from children’s toys to kitchen appliances (yes again) and media devices. The purchasers of these new technology-enabled products are far from security experts, or even security aware. Their primary purchasing requirements are ease of use.
  • regarding embargoes
    Yesterday I jumped the gun committing some patches to LibreSSL. We receive advance copies of the advisory and patches so that when the new OpenSSL ships, we’re ready to ship as well. Between the time we receive advance notice and the public release, we’re supposed to keep this information confidential. This is the embargo. During the embargo time we get patches lined up and a source tree for each cvs branch in a precommit state. Then we wait with our fingers on the trigger. What happened yesterday was I woke up to a couple OpenBSD developers talking about the EBCDIC CVE. Oh, it’s public already? Check the OpenSSL git repo and sure enough, there are a bunch of commits for embargoed issues. Pull the trigger! Pull the trigger! Launch the missiles! Alas, we didn’t look closely enough at the exact issues fixed and had missed the fact that only low severity issues had been made public. The high severity issues were still secret. We were too hasty.
  • Medical Equipment Crashes During Heart Procedure Because of Antivirus Scan [Ed: Windows]
    A critical medical equipment crashed during a heart procedure due to a timely scan triggered by the antivirus software installed on the PC to which the said device was sending data for logging and monitoring.
  • Hotel sector faces cybercrime surge as data breaches start to bite
    Since 2014, things have become a lot more serious with a cross section of mostly US hotels suffering major breaches during Point-of-Sale (POS) terminals. Panda Security lists a string of attacks on big brands including on Trump Hotels, Hilton Worldwide, Hyatt, Starwood, Rosen Hotels & Resorts as well two separate attacks on hotel management outfit White Lodging and another on non-US hotel Mandarin Oriental.

Android Leftovers

today's howtos