Code Siblings: Technical and Legal Implications of Copying Code Between Applications

Total Page:16

File Type:pdf, Size:1020Kb

Code Siblings: Technical and Legal Implications of Copying Code Between Applications Code siblings: technical and legal implications of copying code Between applications Daniel German, Massimiliano Di Penta, Yann -Ga ël Gu éhéneuc , and Giuliano (Giulio) Antoniol MSR 2009, Vancouver 1/17 TheThe ChallengeChallenge Code,Code, asas anyany otherother artisticartistic production,production, isis regulatedregulated byby copyrightcopyright lawlaw CompaniesCompanies ownown thethe propertyproperty ofof sourcesource codecode FreeFree andand openopen sourcesource softwaresoftware (FOSS)(FOSS) modelmodel isis differentdifferent CopyingCopying 2727 LOCLOC outout ofof 525525 KLOCKLOC resultedresulted inin aa copyrightcopyright infringementinfringement UsersUsers andand companiescompanies mustmust bebe awareaware ofof copyrightcopyright lawlaw andand ownershipownership MSR 2009, Vancouver 2/17 CodeCode HasHas PreferentialPreferential MigrationMigration FlowsFlows MSR 2009, Vancouver 3/17 LicenseLicense TypesTypes Permissive – the MIT/X11 and BSD licenses Minor constraints on the licensee Inclusion of fragments in a system under a different license BSD licensed fragments can be included in proprietary systems. CAVEAT! Multiple BSD licenses: original BSD (4-clauses BSD), the new BSD (3-clauses BSD), and the 2-clauses BSD Code licensed under the original 4-clauses BSD cannot be included inside systems licensed under the GPL Reciprocal – GNU variants Any system that includes the fragments must be licensed under the same license GPL-licensed fragments can only be included in systems licensed under the same version of the GPL MSR 2009, Vancouver 4/17 TheThe ScaleScale ofof thethe ProblemProblem WidelyWidely adoptedadopted systemssystems areare inin thethe rangerange ofof MLOCMLOC andand thousandsthousands ofof filesfiles IfIf 27LOC27LOC inin 525KLOC525KLOC leadlead toto copyrightcopyright infringementinfringement Companies implication in reusing code End user implications WeWe areare likelike detectivesdetectives Help monitoring and detecting license inconsistencies Help monitoring and identifying inconsistent licenses in code fragments MSR 2009, Vancouver 5/17 EmpiricalEmpirical StudyStudy CodeCode siblings:siblings: codecode fragmentsfragments thatthat migratedmigrated fromfrom oneone systemsystem toto anotheranother andand thenthen evolvedevolved followingfollowing theirtheir ownown pathspaths ThreeThree *nix*nix kernelskernels Linux ~7MLOC and 20,000 files FreeBSB ~8MLOC and 21,000 files OpenBSD ~2MLOC and 5,500 files OverallOverall SizeSize asas ofof Jan.Jan. 2009,2009, 17MLOC17MLOC MSR 2009, Vancouver 6/17 ResearchResearch QuestionsQuestions RQ1:RQ1: WhatWhat kindskinds ofof openopen sourcesource licenseslicenses areare usedused inin thethe threethree kernels?kernels? RQ2:RQ2: HowHow manymany potentialpotential siblingssiblings existexist betweenbetween thethe BSDBSD kernelskernels andand thethe LinuxLinux kernel?kernel? RQ3:RQ3: WhatWhat licenseslicenses areare usedused byby siblingssiblings and,and, ifif different,different, why?why? MSR 2009, Vancouver 7/17 TechnologiesTechnologies andand SetupSetup CloneClone detectiondetection tooltool CCFinderX tool Min 100 tokens Parse only .c files Concentrate on pair of files sharing a high percentage of common code fragment, least ~30%, i.e., ~20LOC Prune files mapped into more than five siblings LicenseLicense detectiondetection andand identificationidentification First comment(s) FoSSology version 1.0.0 78 different license variants Added 5 more licenses MSR 2009, Vancouver 8/17 Sibling(s)Sibling(s) OriginOrigin IdentifyIdentify currentcurrent siblingssiblings TraceTrace backback intointo pastpast siblingssiblings –– theirtheir codecode fragmentsfragments inin thethe samesame filesfiles WhenWhen theythey disappear,disappear, thenthen wewe havehave theirtheir originsorigins TakeTake thethe oldestoldest ofof thethe twotwo asas thethe truetrue originorigin Sys 1 – File i Cloned fragments Migration siblings direction Sys 2 – File j MSR 2009, Vancouver Cloned fragments 9/17 RQ1:RQ1: KindsKinds ofof openopen sourcesource licenseslicenses LinuxLinux …… isis LinuxLinux …… 65%65% ofof GPLGPL filesfiles plusplus 25%25% ofof filesfiles ““promotedpromoted ”” toto GPLGPL byby L.L. TorvaldTorvald A few files (35) have two licenses FreeBSDFreeBSD 75%75% ofof thethe filesfiles withwith BSDBSD licenselicense 189 files (5%) with no license 179 files with a corporate license (Intel licenses) 167 files with MIT license A few multiple licenses – 19 BSD and GPL, 15 BSD and Educational, 14 MIT and GPL OpenBSDOpenBSD 7676 %% BSDBSD licenseslicenses 295 files (9%) with a MIT license, 179 with an educational license 138 (84%) without license 59 files with BSD and Educational, 25 with MIT and MSR 2009, BSD, and 14 with BSD and GPL Vancouver 10/17 RQ2:RQ2: SiblingsSiblings betweenbetween kernelskernels 2500 2000 1500 FreeBSD vs.Linux OpenBSD vs. Linux 1000 Siblings 500 0 Filtered siblings Clone pairs Files Linux Files BSD File Pairs File Pairs (same name) 250 200 150 FreeBSD vs. Linux OpenBSD vs. Linux 100 50 MSR 2009, Vancouver 0 11/17 Files Linux Files BSD File Pairs File Pairs (same name) RQ3:RQ3: CodeCode MigrationMigration andand LicensesLicenses FreeBSD Linux Files Before Jan 1, 2002 BSD GPL 8 Almost nothing after BSD MIT 2 OpenBSD Linux Files BSD None 2 BSD BSD+GPL 1 Corporate BSD+GPL 89 BSD MIT 2 GPL None 1 Phrase BSD+GPL 1 BSD Unknown 1 X.Net+BSD MIT 1 BSD+GPL GPL 1 BSD+Phrase Phrase+GPL 1 MIT GPL 23 Linux FreeBSD Files BSD+GPL Corporate 8 GPL BSD 17 GPL BSD+GPL 1 GPL CPL+BSD+GPL 1 After Jan 1, 2002 MIT BSD 1 Nothing before MIT+GPL None 2 MSR 2009, None BSD 1 Vancouver None BSD 1 12/17 Phrase+GPL MIT 2 AIC7xxxAIC7xxx MaintainingMaintaining SiblingsSiblings 1994:1994: LinuxLinux AIC7xxxAIC7xxx seriesseries SCSISCSI adaptersadapters 1995:1995: LinuxLinux codecode isis incorporatedincorporated intointo anan OpenBSDOpenBSD driverdriver 1996:1996: NetBSDNetBSD driverdriver isis portedported toto FreeBSDFreeBSD #ifdef to maintain the variants 1997:1997: AA mailingmailing listlist isis createdcreated inin FreeBSDFreeBSD toto unifyunify thethe effortsefforts ofof peoplepeople inin thethe differentdifferent kernelskernels The major development of the driver seems to happen in FreeBSD 2000:2000: DevelopmentDevelopment propagatespropagates toto Linux,Linux, NetBSDNetBSD ,, andand OpenBSDOpenBSD Today:Today: DevelopmentDevelopment mostlymostly LinuxLinux andand FreeBSDFreeBSD MSR 2009, Vancouver 13/17 GPCGPC codecode inin FreeBSDFreeBSD 2002:2002: SiliconSilicon GraphicsGraphics xfsxfs filefile systemsystem integratedintegrated intointo LinuxLinux DecDec 12,12, 20052005 xfsxfs appearsappears inin FreeBSDFreeBSD The license of xfs is GPL FreeBSD is licensed under the 2-clause BSD Including xfs in a BSD kernel requires the kernel to be under the GPL too a CompilingCompiling GPLGPL --licensedlicensed codecode intointo thethe kernelkernel makesmakes itit ““RESTRICTEDRESTRICTED ”” It can no longer be distributed in binary form, its source code be made available for mirroring MSR 2009, Vancouver 14/17 LicenseLicense DefectsDefects FreeBSD rdma _cma .c / Linux cdma .c are siblings In Linux, it appeared on Jun 17, 2006, with 64 changes plus including 8 changes after it appeared in FreeBSD The Linux sibling is licensed under GPL v2 and the 2 - clause BSD licenses The FreeBSD sibling is licensed under the terms of the new BSD license, the GPL v2, and Commons Public License Original license still present in FreeBSD Linux license was changed: commit a9474917099e007c0f51d5474394b5890111614f Author: Sean Hefty <[email protected]> Date: Mon Jul 14 23:48:43 2008 -0700 RDMA: Fix license text The license text for several files references a third software license MSR 2009, that was inadvertently copied in. Update the license to what was Vancouver intended. This update was based on a request from HP. [..] 15/17 ConclusionConclusion CodeCode movemove andand codecode siblingssiblings dodo existexist SiblingsSiblings havehave aa preferentialpreferential flowflow Initially from BSD(s) to Linux – frequent Today from Linux to FreeBSD – less frequent CompaniesCompanies directlydirectly contributecontribute toto codecode inin differentdifferent kernelskernels –– seesee IntelIntel driversdrivers withwith dualdual licenseslicenses ManagingManaging siblingssiblings isis aa difficultdifficult problemproblem MSR 2009, Vancouver 16/17 IfIf youyou dondon ’’tt monitormonitor codecode maymay sneaksneak inin …… QuestionsQuestions ?? MSR 2009, Vancouver 17/17.
Recommended publications
  • Download the Specification
    Internationalizing and Localizing Applications in Oracle Solaris Part No: E61053 November 2020 Internationalizing and Localizing Applications in Oracle Solaris Part No: E61053 Copyright © 2014, 2020, Oracle and/or its affiliates. License Restrictions Warranty/Consequential Damages Disclaimer This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. Warranty Disclaimer The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. Restricted Rights Notice If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial
    [Show full text]
  • Dell Wyse Management Suite Version 2.1 Third Party Licenses
    Dell Wyse Management Suite Version 2.1 Third Party Licenses October 2020 Rev. A01 Notes, cautions, and warnings NOTE: A NOTE indicates important information that helps you make better use of your product. CAUTION: A CAUTION indicates either potential damage to hardware or loss of data and tells you how to avoid the problem. WARNING: A WARNING indicates a potential for property damage, personal injury, or death. © 2020 Dell Inc. or its subsidiaries. All rights reserved. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be trademarks of their respective owners. Contents Chapter 1: Third party licenses...................................................................................................... 4 Contents 3 1 Third party licenses The table provides the details about third party licenses for Wyse Management Suite 2.1. Table 1. Third party licenses Component name License type jdk1.8.0_112 Oracle Binary Code License jre11.0.5 Oracle Binary Code License bootstrap-2.3.2 Apache License, Version 2.0 backbone-1.3.3 MIT MIT aopalliance-1.0.jar Public Domain aspectjweaver-1.7.2.jar Eclipse Public licenses- v 1.0 bcprov-jdk16-1.46.jar MIT commons-codec-1.9.jar Apache License, Version 2.0 commons-logging-1.1.1.jar Apache License, Version 2.0 hamcrest-core-1.3.jar BSD-3 Clause jackson-annotations.2.10.2.jar Apache License, Version 2.0 The Apache Software License, Version 2.0 jackson-core.2.10.2.jar Apache License, Version 2.0 The Apache Software License, Version 2.0 jackson-databind.2.10.2.jar Apache License, Version 2.0 The Apache Software License, Version 2.0 log4j-1.2.17.jar Apache License, Version 2.0 mosquitto-3.1 Eclipse Public licenses- v 1.0 Gradle Wrapper 2.14 Apache 2.0 License Gradle Wrapper 3.3 Apache 2.0 License HockeySDK-Ios3.7.0 MIT Relayrides / pushy - v0.9.3 MIT zlib-1.2.8 zlib license yaml-cpp-0.5.1 MIT libssl.dll (1.1.1c) Open SSL License 4 Third party licenses Table 1.
    [Show full text]
  • GNU Guix Cookbook Tutorials and Examples for Using the GNU Guix Functional Package Manager
    GNU Guix Cookbook Tutorials and examples for using the GNU Guix Functional Package Manager The GNU Guix Developers Copyright c 2019 Ricardo Wurmus Copyright c 2019 Efraim Flashner Copyright c 2019 Pierre Neidhardt Copyright c 2020 Oleg Pykhalov Copyright c 2020 Matthew Brooks Copyright c 2020 Marcin Karpezo Copyright c 2020 Brice Waegeneire Copyright c 2020 Andr´eBatista Copyright c 2020 Christine Lemmer-Webber Copyright c 2021 Joshua Branson Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.3 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled \GNU Free Documentation License". i Table of Contents GNU Guix Cookbook ::::::::::::::::::::::::::::::: 1 1 Scheme tutorials ::::::::::::::::::::::::::::::::: 2 1.1 A Scheme Crash Course :::::::::::::::::::::::::::::::::::::::: 2 2 Packaging :::::::::::::::::::::::::::::::::::::::: 5 2.1 Packaging Tutorial:::::::::::::::::::::::::::::::::::::::::::::: 5 2.1.1 A \Hello World" package :::::::::::::::::::::::::::::::::: 5 2.1.2 Setup:::::::::::::::::::::::::::::::::::::::::::::::::::::: 8 2.1.2.1 Local file ::::::::::::::::::::::::::::::::::::::::::::: 8 2.1.2.2 `GUIX_PACKAGE_PATH' ::::::::::::::::::::::::::::::::: 9 2.1.2.3 Guix channels ::::::::::::::::::::::::::::::::::::::: 10 2.1.2.4 Direct checkout hacking:::::::::::::::::::::::::::::: 10 2.1.3 Extended example ::::::::::::::::::::::::::::::::::::::::
    [Show full text]
  • Marjn Norling November 2012
    Mar$n Norling November 2012 UNIX Lecture Goals • Goal 1: Know basic UNIX commands and their use from memory. • Goal 2: Know how to find informaon on more advanced UNIX commands and their use. • Goal 3: Understand the basics of regular expression paerns. • Goal 4: Know the basic loops and condi$onals for shell scrip$ng and understand how to use them. UNIX Schedule Thursday Friday 09.00-09.45 UNIX introduc$on 09.00-09.45 Bash Scrip$ng 10.00-10.45 UNIX basics 10.00-10.45 Tutorial: Bash scrip$ng 11.00-12.00 Redirects to regexp 11.00-12.00 Tips & Quesons 12.00-13.00 Lunch 12.00-13.00 Lunch 13.00-16.00 Tutorial: Basics 13.00-16.00 Tutorial: finishing up UNIX HISTORY UNIX History • 1969 – First Version of UNIX developed at Bell Labs by AT&T • 1975 – UNIX 6, the first to be widely available outside Bell Labs. The first “Berkeley So]ware Distribu$on” (BSD) is released. • 1989 – UNIX System V, the last tradi$onal UNIX version. • 1991 – Linus Torvalds begin developing Linux. “UNIX-like” • Today – UNIX itself, what’s now called “tradi$onal UNIX” is not used, except by enthusiasts. • There are many “UNIX-like” systems (also known as *nix or UN*X) that are similar to UNIX while not conforming to the Single UNIX Specificaon. • In fact, most operang systems today except windows are “UNIX like”. Single UNIX Specificaon (SUS) • Developed and maintained by the Aus$n Group, based on earlier work by the IEee and The Open Group.
    [Show full text]
  • Using Ptxdist on Mac OS Based on Ptxdist 2012.04
    Using PTXdist on Mac OS based on PTXdist 2012.04 Bernhard Walle∗ 2012-04-20 ∗[email protected] Contents 1. Motivation 3 2. Basics 4 2.1. Getting OpenSource Software on Mac OS.........................4 2.2. Preparing the Hard Disk..................................5 2.2.1. Creating and Using a Sparse Bundle ........................6 3. Installing PTXdist7 3.1. Requirements........................................7 3.1.1. Mac OS.......................................7 3.1.2. Host compiler....................................7 3.2. GNU Tools..........................................7 3.3. Installation..........................................8 3.4. First setup..........................................9 4. Building an OSELAS.Toolchain 11 5. Building an Embedded Linux project 12 5.1. Using OSELAS.BSP-Pengutronix-Generic......................... 12 5.1.1. Getting the BSP................................... 12 5.1.2. Building FSF GCC.................................. 13 5.1.3. Building Qemu................................... 13 5.1.4. Running the System................................ 13 5.2. Using real Hardware.................................... 14 6. Limitations 15 6.1. Building UBI or JFFS2 images................................ 15 6.2. Linux kernel......................................... 15 6.3. Bootloader.......................................... 15 7. Using a Mac for Embedded Linux Development 16 7.1. Using a serial console.................................... 16 7.2. Exporting directories via NFS............................... 16 7.3. Mounting ext2 partitions.................................. 18 A. About this Document 19 B. Change History 20 Bibliography 21 2 1. Motivation PTXdist (http://www.ptxdist.org) is a great way to build Embedded Linux systems. It downloads all required components, conVgures them for cross-compilation and Vnally builds a target image and/or target packages. In addition, it provides an easy way to build a cross-toolchain for most common processors. Read [2] for a description how to use PTXdist.
    [Show full text]
  • Free Berkeley Software Distribution
    Free berkeley software distribution Berkeley Software Distribution (BSD) was a Unix operating system derivative developed and . The lawsuit slowed development of the free- software descendants of BSD for nearly two years while their legal status was in question, and as a OS family​: ​Unix. Software Central is a consolidation of several IST sites that offer software to UC Berkeley faculty, staff and students. The products available through this site are ​Productivity Software · ​Mathematics & Sciences · ​VMware · ​Stata. Software Central. The API department runs the Campus Software Distribution Service, which: Runs a distribution service through (link is. Free Speech Online Blue Ribbon Campaign. Welcome to ! UNIX! Live free or die! Google. Custom Search. What is this page all about? This page is. BSD stands for “Berkeley Software Distribution”. which is available on CD-ROM and for free download from FTP sites, for example OpenBSD. All of the documentation and software included in the BSD and As you know, certain of the Berkeley Software Distribution ("BSD") source. Template:Redirect Berkeley Software Distribution (BSD, sometimes called many other operating systems, both free and proprietary, to incorporate BSD code. BSD (originally: Berkeley Software Distribution) refers to the particular version of the UNIX operating system that was developed at and distributed fro. Short for Berkeley Software Distribution, BSD is a Unix-like NetBSD is another free version of BSD compatible with a very large variety of. Berkeley Software Distribution (BSD) is a prominent version of the Unix operating system that was developed and distributed by the Computer Systems. Early in , Joy put together the "Berkeley Software Distribution.
    [Show full text]
  • Functional Package and Configuration Management with GNU Guix
    Functional Package and Configuration Management with GNU Guix David Thompson Wednesday, January 20th, 2016 About me GNU project volunteer GNU Guile user and contributor since 2012 GNU Guix contributor since 2013 Day job: Ruby + JavaScript web development / “DevOps” 2 Overview • Problems with application packaging and deployment • Intro to functional package and configuration management • Towards the future • How you can help 3 User autonomy and control It is becoming increasingly difficult to have control over your own computing: • GNU/Linux package managers not meeting user needs • Self-hosting web applications requires too much time and effort • Growing number of projects recommend installation via curl | sudo bash 1 or otherwise avoid using system package managers • Users unable to verify that a given binary corresponds to the source code 1http://curlpipesh.tumblr.com/ 4 User autonomy and control “Debian and other distributions are going to be that thing you run Docker on, little more.” 2 2“ownCloud and distribution packaging” http://lwn.net/Articles/670566/ 5 User autonomy and control This is very bad for desktop users and system administrators alike. We must regain control! 6 What’s wrong with Apt/Yum/Pacman/etc.? Global state (/usr) that prevents multiple versions of a package from coexisting. Non-atomic installation, removal, upgrade of software. No way to roll back. Nondeterminstic package builds and maintainer-uploaded binaries. (though this is changing!) Reliance on pre-built binaries provided by a single point of trust. Requires superuser privileges. 7 The problem is bigger Proliferation of language-specific package managers and binary bundles that complicate secure system maintenance.
    [Show full text]
  • Engineering Law and Ethics
    ENSC 406 Software, Computer and Internet Ethics Bob Gill, P.Eng., FEC, smIEEE May 15th 2017 1 Topics Covered What is Open Source Software? A One-Slide History of Open Source Software The Open Source Development Model Why Companies Use (and Don’t Use) Open Source Software Open Source Licensing Strategies Open Source Licenses and “Copyleft” Open Source Issues in Corporate Transactions Relevant Cases and Disputes Open source vs. Freeware vs. Shareware Site Licensing Software Maintenance Computer and Internet Ethics 2 What is Open Source Software? Open Source software is software licensed under an agreement that conforms to the Open Source Definition Access to Source Code Freedom to Redistribute Freedom to Modify Non-Discriminatory Licensing (licensee/product) Integrity of Authorship Redistribution in accordance with the Open Source License Agreement 3 What is Open Source Software? Any developer/licensor can draft an agreement that conforms to the OSD, though most licensors use existing agreements GNU Public License (“GPL”) Lesser/Library GNU Public License (“LGPL”) Mozilla Public License Berkeley Software Distribution license (“BSD”) Apache Software License MIT – X11 License See complete list at www.opensource.org/licenses 4 Examples of Open Source Software Linux (operating system kernel – substitutes for proprietary UNIX) Apache Web Server (web server for UNIX systems) MySQL(Structured Query Language – competes with Oracle) Cloudscape, Eclipse (IBM contributions) OpenOffice(Microsoft Office Alternate) SciLab,
    [Show full text]
  • UNIX and High-Level Language Education Using Windows Operating Systems
    UNIX and High-level Language Education Using Windows Operating Systems R. W. Skeith M. A. Thornton Department of Computer Engineering Department of Electrical and Computer Engineering University of Arkansas Mississippi State University 313 Engineering Hall ECE Dept., P. O. Box 9571 Fayetteville, AR 72701-1201 Miss. State, MS. 39762-9571 [email protected] [email protected] Abstract Entering and continuing engineering students need to learn skills in the use of high-level languages and the use of the UNIX operating system [1] including the development of shell scripts. In the past, this requirement has been very challenging to educators since it requires access to a laboratory containing (sometimes expensive) computers that are UNIX-based workstations. The widespread availability of the LINUX operating system [2] helps to alleviate this problem somewhat since the operating system is free and associated high-level language compilers are also freely available through the GNU project [3]. Unfortunately, the skills required to successfully install and use LINUX often precludes its use as a classroom tool that students can easily maintain. An alternative and free solution based on the use of a UNIX emulator that runs under Microsoft Windows operating systems is described here. INTRODUCTION Recently, several UNIX emulators that are easily installed and used under the Microsoft Operating Systems (OS) commonly referred to as “Windows” have become available [4,5,6,7]. This paper describes the authors’ experiences in using these tools in an undergraduate setting for the purpose of teaching the use of UNIX and various high-level languages such as PERL, FORTRAN, C and C++.
    [Show full text]
  • GNU / Linux and Free Software
    GNU / Linux and Free Software GNU / Linux and Free Software An introduction Michael Opdenacker Free Electrons http://free-electrons.com Created with OpenOffice.org 2.x GNU / Linux and Free Software © Copyright 2004-2007, Free Electrons Creative Commons Attribution-ShareAlike 2.5 license http://free-electrons.com Sep 15, 2009 1 Rights to copy Attribution ± ShareAlike 2.5 © Copyright 2004-2007 You are free Free Electrons to copy, distribute, display, and perform the work [email protected] to make derivative works to make commercial use of the work Document sources, updates and translations: Under the following conditions http://free-electrons.com/articles/freesw Attribution. You must give the original author credit. Corrections, suggestions, contributions and Share Alike. If you alter, transform, or build upon this work, you may distribute the resulting work only under a license translations are welcome! identical to this one. For any reuse or distribution, you must make clear to others the license terms of this work. Any of these conditions can be waived if you get permission from the copyright holder. Your fair use and other rights are in no way affected by the above. License text: http://creativecommons.org/licenses/by-sa/2.5/legalcode GNU / Linux and Free Software © Copyright 2004-2007, Free Electrons Creative Commons Attribution-ShareAlike 2.5 license http://free-electrons.com Sep 15, 2009 2 Contents Unix and its history Free Software licenses and legal issues Free operating systems Successful project highlights Free Software
    [Show full text]
  • The Intel Management Engine: an Attack on Computer Users' Freedom by Denis Gnutoo Carikli
    A statement by FSF President Richard Stallman on the Intel Management Engine (ME): "Meltdown and Spectre are errors. Grave errors, to be sure, but not evidently malicious. Everyone makes mistakes. Intel has done far worse with its CPUs than make a mistake. It has built in an intentional back door called the Management Engine. Important as these bugs are, don©t let Intel©s mistakes distract you from Intel©s deliberate attack!" The Intel Management Engine: an attack on computer users© freedom By Denis GNUtoo Carikli With security issues like the Spectre and Meltdown vulnerabilities (https://www.cnet.com/news/meltdown-spectre-intel-ceo-no-recall-chip-processor/) discovered in Intel chips in early 2018, it became more important than ever to talk about the necessity of software freedom in these deeply embedded technologies. Serious as though these bugs may be, we cannot let them distract us from the broader issues: Intel considers the Intel Management Engine a feature, while it©s nothing more than a threat to user freedom. Thanks to Denis GNUtoo Carikli, we have a new basis for that conversation in this article. The Intel Management Engine is a tool that ships with Intel chipsets, purportedly to ease the job of system administrators. But in reality, it is another restriction on user freedoms, imposed by a company, and used to control your computing. Carikli offers a moderately technical explanation of what©s happening with Management Engine, the ways in which it restricts rather than empowers users, and how it violates the four freedoms of free software. Carikli may be best known for his work on the Replicant project (https://www.replicant.us/), which he co-founded with Aaron Williamson, Bradley Kuhn, and Grazlano Sorbaioli.
    [Show full text]
  • Third Party Licenses Visual Investigator
    Third Party Licenses and Information This page contains information regarding any third party code included with your SAS software, including applicable third party software notices and/or additional terms and conditions. SAS Visual Investigator 10.7 Component Applicable License(s) @uirouter/angularjs 1.0.20 MIT License @uirouter/core 5.0.21 MIT License @uirouter/dsr 1.0.3 MIT License @uirouter/sticky-states 1.5.0 MIT License ACE 1.2.3 BSD 3-clause "New" or "Revised" License akka-actor 2.4.17 Apache License 2.0 Angular 1.7.9 MIT License Animal Sniffer Annotations 1.18 MIT License ANTLR 2.7.7 ANTLR Software Rights Notice ANTLR 3.5.2 BSD 3-clause "New" or "Revised" License ANTLR 4.5.3 BSD 3-clause "New" or "Revised" License ANTLR 4 Tool 4.5 BSD 3-clause "New" or "Revised" License ANTLR 4 Tool 4.5.3 BSD 3-clause "New" or "Revised" License Apache Commons BeanUtils 1.9.4 Apache License 2.0 Apache Commons Codec 1.11 Apache License 2.0 Apache Commons Codec 1.9 Apache License 2.0 Apache Commons Collections 3.2.2 Apache License 2.0 Apache Commons Collections 4.1 Apache License 2.0 Apache Commons Collections 4.3 Apache License 2.0 Apache Commons Collections commons-commons-collections-4.4 Apache License 2.0 Apache Commons Compress 1.19 Apache License 2.0 Apache Commons Configuration 1.8 Apache License 2.0 Apache Commons CSV 1.4 Apache License 2.0 Apache Commons DBCP 1.4 Apache License 2.0 Apache Commons Digester 2.1 Apache License 1.1 Apache Commons Email 1.5 Apache License 2.0 Apache Commons FileUpload 1.3.3 Apache License 2.0 Apache Commons Lang
    [Show full text]