DOCSLIB.ORG

Information Regarding Free and Open Source Software

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Information regarding Free and Open Source Software This product includes software components that are licensed by the copyright holders as free software or open source software. The applicable license texts are printed below. Warranty Disclaimer The open source software in this product is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY, without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the applicable licenses for more details. The source code will be made available to you on request. To file a request, please email to [email protected] or send a written request to BSH Hausgeräte GmbH Carl-Wery-Str.34 D-81739 München Reference „OSSREQUEST“ The cost of performing your request will be charged to you. This offer is valid three years from the date of purchase or at least as long as we offer support and spare parts for the product. Information regarding Free and Open Source Software The license texts are displayed below the copyright statement at the end of this document. PACKAGE NAME: acl LICENSE: LGPLv2.1 Copyright statements: Copyright (c) 2000-2006 Silicon Graphics, Inc. All Rights Reserved. Copyright (C) 2007 Free Software Foundation, Inc. Antonio Trueba [email protected], 2007. Copyright (C) 2006 Free Software Foundation, Inc. Daniel Nylander [email protected], 2006. Copyright (C) 2005 Free Software Foundation, Inc. Sylvain Archenault [email protected], 2005. Copyright (C) 2004 Free Software Foundation, Inc. Jakub Bogusz [email protected], 2004. Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011 Free Software Foundation, Inc. Written by Gordon Matzigkeit, 1996 Copyright (C) 1989, 1991-2012 Free Software Foundation, Inc. (C) 1999-2011 Andreas Gruenbacher PACKAGE NAME: attr LICENSE: LGPLv2.1 Copyright statements: Copyright (c) 1999-2008 Silicon Graphics, Inc. All Rights Reserved. Copyright (C) 2008 Petr Pisar [email protected] Copyright (C) 2007 Antonio Trueba [email protected] Copyright (C) 2006 Daniel Nylander [email protected] Copyright (C) 2005 Guilhelm Panaget [email protected] Copyright (C) 2004, 2005 Jakub Bogusz [email protected] Copyright (C) 2004 Luk Claes [email protected] Copyright (C) 2000-2009 Andreas Gruenbacher [email protected] Copyright (C) 1996-2012 Free Software Foundation, Inc. PACKAGE NAME: avahi LICENSE: GPLv2.0 , LGPLv2.1 Copyright statements: Copyright © 2004 Scott James Remnant [email protected]. Copyright 2010 Lennart Poettering Copyright 2009 Johan Dahlin dnl Copyright 2004-2015 by the Avahi developers. Copyright 2003, 2004, 2004 Porchdog Software. All rights reserved. Copyright 2003, 2004 Porchdog Software. All rights reserved. Copyright 2003, 2004 Porchdog Software, Inc. All rights reserved. Copyright 1999-2007 Gentoo Foundation Distributed under the terms of the GNU General Public License v2 Copyright 1991-2015 Free Software Foundation, Inc. Copyright (c) 2003-2004, Apple Computer, Inc. All rights reserved. Copyright (C) 2009 Avahi's COPYRIGHT HOLDER Bruce Cowan [email protected] Copyright (C) 2006-2007 Collabora Ltd. Copyright (C) 2004-2008 Rodney Dawes [email protected] Copyright (C) 2004 Oren Ben-Kiki This file is distributed under the same terms as the Automake macro files. Copyright (C) 2004 Oren Ben-Kiki This file is distributed under the same terms as the Autoconf macro files. Copyright (C) 2001 Eazel, Inc. Author: Maciej Stachowiak [email protected] Kenneth Christiansen [email protected] Copyright (C) 2000-2003,2004 Red Hat, Inc. Copyright (C) 1999 Tom Tromey Copyright (C) 1995, 1996, 1997 by Ulrich Drepper [email protected] Copyright (C) 1994 X Consortium PACKAGE NAME: backport-brcmfmac BSH Hausgeräte GmbH 1 / 266 LICENSE: GPLv2.0 Copyright statements: Copyright: (c) 2014 Czech Technical University in Prague Copyright 2015-2017 Intel Deutschland GmbH Copyright 2013-2014 Intel Mobile Communications GmbH Copyright 2011 Alexey Dobriyan [email protected] Copyright 2008-2015 Luis R. Rodriguez [email protected] Copyright 2008 Michael Wu [email protected] Copyright 2008 Michael Buesch [email protected] Copyright 2008 Luis Carlos Cobo [email protected] Copyright 2008 Colin McCabe [email protected] Copyright 2007 Andy Green [email protected] Copyright 2006-2010 Johannes Berg [email protected] Copyright 2005-2007 Jiri Benc [email protected] Copyright 2002-2006, Devicescape Software, Inc. Copyright 2002-2005, Instant802 Networks, Inc. Copyright 1997--1999 Martin Mares [email protected] Copyright 1994, Drew Eckhardt Copyright (c) 2016 Qualcomm Atheros, Inc Copyright (c) 2015-2016 Herbert Xu [email protected] Copyright (c) 2015 Stefan Assmann [email protected] Copyright (c) 2014-2015 Thomas Graf [email protected] Copyright (c) 2013 Hannes Frederic Sowa [email protected] Copyright (c) 2011-2017 Hauke Mehrtens [email protected] Copyright (c) 2010-2016 Broadcom Corporation Copyright (c) 2008-2014 Patrick McHardy [email protected] Copyright (c) 2008, 2009 John W. Linville [email protected] Copyright (c) 2006-2012 Jiri Kosina Copyright (c) 2006, Michael Wu [email protected] Copyright (c) 2005 Michael Haboustak [email protected] for Concept2, Inc Copyright (c) 2002 Johann Deneux Copyright (c) 2001-2004, 2008, 2009 Jouni Malinen [email protected] Copyright (c) 2000-2005 Vojtech Pavlik [email protected] Copyright (c) 1999 Andreas Gal Copyright (c) 1997-2007 Jean Tourrilhes, All Rights Reserved. Copyright (C) 2017 Rafał Miłecki [email protected] Copyright (C) 2014 Felix Fietkau [email protected] Copyright (C) 2012,2015 Eric Dumazet [email protected] Copyright (C) 2012 Red Hat, Inc. All Rights Reserved. Written by David Howells ([email protected]) Copyright (C) 2012 Michael D. Taht [email protected] Copyright (C) 2011-2012 Van Jacobson [email protected] Copyright (C) 2011-2012 Kathleen Nichols [email protected] Copyright (C) 2007, 2008 Wolfson Microelectronics PLC. Copyright (C) 2006-2015, ARM Limited, Copyright (C) 2004, 2009, 2018 Intel Corporation. All rights reserved. Copyright (C) 2004 - 2009 Ivo van Doorn [email protected] Copyright (C) 2002-2005 Sam Ravnborg [email protected] Copyright (C) 2002-2005 Roman Zippel [email protected] Copyright (C) 1984, 1989-1991, 2001-2015 Free Software Foundation, Inc. (c) 2014 Volkswagen Group Research Author: Rostislav Lisovy [email protected] Funded by: Volkswagen Group Research (C) 2012 Sasha Levin [email protected] PACKAGE NAME: base-passwd LICENSE: GPLv2.0 Copyright statements: Copyright: Copyright 2001, 2002 Joey Hess Copyright: Copyright 1999-2002 Wichert Akkerman [email protected] Copyright 2007 David Mandelberg Copyright 2002, 2003, 2004, 2005, 2007 Colin Watson Copyright 1999-2002 Wichert Akkerman [email protected] Copyright 1991 by the Massachusetts Institute of Technology Copyright (C) Helge Kreutzmann [email protected], 2011. Copyright (C) 2004 Nicolas FRANCOIS Copyright (C) 1989, 1991-1996, 1998-2012 Free Software Foundation, Inc. PACKAGE NAME: bluez5 LICENSE: GPLv2.0 , LGPLv2.1 Copyright statements: © Nespresso S.A. BSH Hausgeräte GmbH 2 / 266 © Antonio Santos Cadenas [email protected] Francisco Alecrim [email protected] Daniel Orstadius [email protected] Anderson Briglia [email protected] Anderson Lizardo [email protected] Bruna Moreira [email protected] Brian Gix [email protected] Andre Guedes [email protected] Sheldon Demario [email protected] Lucas De Marchi [email protected] Szymon Janc [email protected] Syam Sidhardhan [email protected] Paulo Alcantara [email protected] Jefferson Delfes [email protected] Andrzej Kaczmarek [email protected] Eder Ruiz Maria [email protected] Mikel Astiz mikel.astiz@bmw- carit.de Chan-yeol Park [email protected] João Paulo Rechi Vita [email protected] Larry Junior [email protected] Raymond Liu [email protected] Radoslaw Jablonski [email protected] Rafal Michalski michalski.raf Copyright © 2004 Scott James Remnant [email protected]. Copyright (c) 2013, Kenneth MacKay All rights reserved. Copyright (c) 2010-2012 Code Aurora Forum. All rights reserved. Copyright (c) 2009-2010 Atheros Communications Inc. Copyright (C) 2017 Red Hat Inc. Copyright (C) 2016 ROLI Ltd. Copyright (C) 2015,2016 Felipe F. Tonello [email protected] Copyright (C) 2015 Andrzej Kaczmarek [email protected] Copyright (C) 2013 Szymon Janc [email protected] Copyright (C) 2012-2015 Google Inc. Copyright (C) 2012 Nordic Semiconductor Inc. Copyright (C) 2011-2017 Intel Corporation. All rights reserved. Copyright (C) 2011-2014 Tieto Poland Copyright (C) 2011-2013 BMW Car IT GmbH. All rights reserved. Copyright (C) 2011-2012 David Herrmann [email protected] Copyright (C) 2011 Bartosz Szatkowski [email protected] for Comarch Copyright (C) 2011 Antonio Ospite [email protected] Copyright (C) 2011 André Dieb Martins [email protected] Copyright (C) 2010-2014 Instituto Nokia de Tecnologia - INdT Copyright (C) 2010-2011 ST-Ericsson SA """ Copyright (C) 2010 Signove Copyright (C) 2010 Marcel Mol [email protected] Copyright (C) 2010 GSyC/LibreSoft, Universidad Rey Juan Carlos. Copyright (C) 2009-2011 Kay Sievers [email protected] Copyright (C) 2009-2010 Nokia Corporation Copyright (C) 2009,2017 Bastien Nocera [email protected] Copyright (C) 2009 Joao Paulo Rechi Vita Copyright (C) 2009 Bastien Nocera [email protected]
Recommended publications
  • Free and Open Source Software Is Not a “Free for All”: German Court Enforces GPL License Terms

    Free and Open Source Software Is Not a “Free for All”: German Court Enforces GPL License Terms

    Free and Open Source Software Is Not A “Free For All”: German Court Enforces GPL License Terms The GNU General Public License, computer programs, and to guarantee version 2 (GPLv2) scores another the same rights to the recipients of court victory for the free and/or open works licensed under the GPLv2. source software (FOSS) community. Although the open-source movement The GPLv2 carries important has been active for nearly two conditions, however, most notably— decades, globally there are only and critical for its viability—that any a handful of cases in which a FOSS distribution of software licensed under license has been reviewed by — let the GPLv2 must be accompanied with alone receive the imprimatur of the “complete corresponding machine- enforceability from — a court. The readable source code” or “a written latest case hails from Germany and offer … to give any third party … a serves to underscore the importance complete machine-readable copy of of proper FOSS-license compliance the corresponding source code”. throughout the software development GPLv2, Sections 3(a) and 3(b). process and supply chain, including During a “Hacking for Compliance the obligation of distributors to Workshop” organized in Berlin in 2012 independently verify FOSS-license by the Free Software Foundation compliance representations from their Europe, the source code package for a suppliers. media player with GNU/Linux-based Welte v. Fantec firmware inside was found not to contain the source code for the Harald Welte, founder of gpl- iptables components. It was also violations.org (a non-profit discovered that the source code for organization aiming at the other device components was not the enforcement of GPL license terms), is same version used to compile the the owner of “netfilter/iptables” firmware’s binary code.
  • GIMP Toolkit: GTK+ V1.2

    GIMP Toolkit: GTK+ V1.2

    'Construction d’IHM $ GIMP Toolkit: GTK+ v1.2 Alexis N´ed´elec Ecole Nationale d’Ing´enieursde Brest TechnopˆoleBrest-Iroise, Site de la Pointe du Diable CP 15 29608 BREST Cedex (FRANCE) e-mail : [email protected] & enib=li2 °c A.N. 1 % 'GTK+ v1.2 : GIMP Toolkit $ Table des Mati`eres Introduction 3 Premier Programme: Hello World 10 Signaux et R´eflexes 14 Description de Widget 22 Container de Widgets 32 Entr´eesde Texte 43 Les Listes multi-colonnes 76 Repr´esentation d’arborescence 89 Bibliographie 107 & enib=li2 °c A.N. 2 % 'GTK : GIMP Toolkit $ Introduction On peut d´efinirGTK comme: . une API “Orient´eObjet” . pour le d´eveloppement d’IHM graphiques (GUI) . sous Licence GNU (LGPL) Glossaire de Sigles: . GNU : GNU’s Not Unix ou “Vive le Logiciel Libre !”. GNOME : GNU Network Object Model Environment . GIMP : General Image Manipulation Program . GDK : GIMP Drawing Kit . GTK : GIMP ToolKit & enib=li2 °c A.N. 3 % 'GTK : GIMP Toolkit $ Introduction Le Projet GNOME: . 1997: Miguel de Icaza du “Mexican Autonomous National University” . objectifs : d´eveloppement de logiciels libres (open source) . inspir´edes d´eveloppements de KDE (Qt) GNOME est bas´esur un ensemble de librairies existantes . glib: utilitaire pour la cr´eationet manipulation de structures . GTK+: Boˆıte`aoutils pour le d´eveloppement d’IHM graphiques . ORBit: Le Broker GNOME (CORBA 2.2) pour la distribution d’objets . Imlib: pour la manipulation d’images sous X Window et GDK & enib=li2 °c A.N. 4 % 'GTK : GIMP Toolkit $ Introduction Librairies sp´ecifiquesdu projet GNOME . libgnome: utilitaires (non-GUI) de bases pour toute application GNOME .
  • Open Source Software Notice

    Open Source Software Notice

    OPEN SOURCE SOFTWARE NOTICE DCS Touch Display Software V2.00.XXX Schüco International KG Karolinenstraße 1-15 33609 Bielefeld OPEN SOURCE SOFTWARE NOTICE Seite 1 von 32 10000507685_02_EN OPEN SOURCE SOFTWARE NOTICE This document contains information about open source software for this product. The rights granted under open source software licenses are granted by the respective right holders. In the event of conflicts between SCHÜCO’S license conditions and the applicable open source licenses, the open source license conditions take precedence over SCHÜCO’S license conditions with regard to the respective open source software. You are allowed to modify SCHÜCO’S proprietary programs and to conduct reverse engineering for the purpose of debugging such modifications, to the extent such programs are linked to libraries licensed under the GNU Lesser General Public License. You are not allowed to distribute information resulting from such reverse engineering or to distribute the modified proprietary programs. The rightholders of the open source software require to refer to the following disclaimer, which shall apply with regard to those rightholders: Warranty Disclaimer THE OPEN SOURCE SOFTWARE IN THIS PRODUCT IS DISTRIBUTED ON AN "AS IS" BASIS AND IN THE HOPE THAT IT WILL BE USEFUL, BUT WITHOUT ANY WARRANTY OF ANY KIND, WITHOUT EVEN THE IMPLIED WARRANTY OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SEE THE APPLICABLE LICENSES FOR MORE DETAILS. OPEN SOURCE SOFTWARE NOTICE Seite 2 von 32 10000507685_02_EN Copyright Notices and License Texts (please see the source code for all details) Software: iptables Copyright notice: Copyright (C) 1989, 1991 Free Software Foundation, Inc. Copyright Google, Inc.
  • Netfilter's Connection Tracking System

    Netfilter's Connection Tracking System

    FILTERING POLICIES BASED UNIQUELY on packet header information are obsolete. PABLO NEIRA AYUSO These days, stateful firewalls provide advanced mechanisms to let sysadmins Netfilter’s and security experts define more intelli- gent policies. This article describes the connection implementation details of the connection tracking system tracking system provided by the Netfilter project and also presents the required Pablo Neira Ayuso has an M.S. in computer science background to understand it, such as an and has worked for several companies in the IT secu- rity industry, with a focus on open source solutions. understanding of the Netfilter framework. Nowadays he is a full-time teacher and researcher at the University of Seville. This article will be the perfect complement to understanding the subsystem that [email protected] enables the stateful firewall available in any recent Linux kernel. The Netfilter Framework The Netfilter project was founded by Paul “Rusty” Russell during the 2.3.x development series. At that time the existing firewalling tool for Linux had serious drawbacks that required a full rewrite. Rusty decided to start from scratch and create the Netfilter framework, which comprises a set of hooks over the Linux network protocol stack. With the hooks, you can register kernel modules that do some kind of network packet handling at different stages. Iptables, the popular firewalling tool for Linux, is commonly confused with the Netfilter framework itself. This is because iptables chains and hooks have the same names. But iptables is just a brick on top of the Netfilter framework. Fortunately, Rusty spent considerable time writ- ing documentation [1] that comes in handy for anyone willing to understand the framework, al- though at some point you will surely feel the need to get your hands dirty and look at the code to go further.
  • The Glib/GTK+ Development Platform

    The Glib/GTK+ Development Platform

    The GLib/GTK+ Development Platform A Getting Started Guide Version 0.8 Sébastien Wilmet March 29, 2019 Contents 1 Introduction 3 1.1 License . 3 1.2 Financial Support . 3 1.3 Todo List for this Book and a Quick 2019 Update . 4 1.4 What is GLib and GTK+? . 4 1.5 The GNOME Desktop . 5 1.6 Prerequisites . 6 1.7 Why and When Using the C Language? . 7 1.7.1 Separate the Backend from the Frontend . 7 1.7.2 Other Aspects to Keep in Mind . 8 1.8 Learning Path . 9 1.9 The Development Environment . 10 1.10 Acknowledgments . 10 I GLib, the Core Library 11 2 GLib, the Core Library 12 2.1 Basics . 13 2.1.1 Type Definitions . 13 2.1.2 Frequently Used Macros . 13 2.1.3 Debugging Macros . 14 2.1.4 Memory . 16 2.1.5 String Handling . 18 2.2 Data Structures . 20 2.2.1 Lists . 20 2.2.2 Trees . 24 2.2.3 Hash Tables . 29 2.3 The Main Event Loop . 31 2.4 Other Features . 33 II Object-Oriented Programming in C 35 3 Semi-Object-Oriented Programming in C 37 3.1 Header Example . 37 3.1.1 Project Namespace . 37 3.1.2 Class Namespace . 39 3.1.3 Lowercase, Uppercase or CamelCase? . 39 3.1.4 Include Guard . 39 3.1.5 C++ Support . 39 1 3.1.6 #include . 39 3.1.7 Type Definition . 40 3.1.8 Object Constructor . 40 3.1.9 Object Destructor .
  • Third Party Terms for Modular Messaging 3.0 (July 2005)

    Third Party Terms for Modular Messaging 3.0 (July 2005)

    Third Party Terms for Modular Messaging 3.0 (July 2005) Certain portions of the product ("Open Source Components") are licensed under open source license agreements that require Avaya to make the source code for such Open Source Components available in source code format to its licensees, or that require Avaya to disclose the license terms for such Open Source Components. If you are a licensee of this Product, and wish to receive information on how to access the source code for such Open Source Components, or the details of such licenses, you may contact Avaya at (408) 577-7666 for further information. The Open Source Components are provided “AS IS”. ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR THE CONTRIBUTORS OF THE OPEN SOURCE COMPONENTS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THE PRODUCT, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Avaya provides a limited warranty on the Product that incorporates the Open Source Components. Refer to your customer sales agreement to establish the terms of the limited warranty. In addition, Avaya’s standard warranty language as well as information regarding support for the Product, while under warranty, is available through the following web site: http://www.avaya.com/support.
  • A Brief History of GNOME

    A Brief History of GNOME

    A Brief History of GNOME Jonathan Blandford <[email protected]> July 29, 2017 MANCHESTER, UK 2 A Brief History of GNOME 2 Setting the Stage 1984 - 1997 A Brief History of GNOME 3 Setting the stage ● 1984 — X Windows created at MIT ● ● 1985 — GNU Manifesto Early graphics system for ● 1991 — GNU General Public License v2.0 Unix systems ● 1991 — Initial Linux release ● Created by MIT ● 1991 — Era of big projects ● Focused on mechanism, ● 1993 — Distributions appear not policy ● 1995 — Windows 95 released ● Holy Moly! X11 is almost ● 1995 — The GIMP released 35 years old ● 1996 — KDE Announced A Brief History of GNOME 4 twm circa 1995 ● Network Transparency ● Window Managers ● Netscape Navigator ● Toolkits (aw, motif) ● Simple apps ● Virtual Desktops / Workspaces A Brief History of GNOME 5 Setting the stage ● 1984 — X Windows created at MIT ● 1985 — GNU Manifesto ● Founded by Richard Stallman ● ● 1991 — GNU General Public License v2.0 Our fundamental Freedoms: ○ Freedom to run ● 1991 — Initial Linux release ○ Freedom to study ● 1991 — Era of big projects ○ Freedom to redistribute ○ Freedom to modify and ● 1993 — Distributions appear improve ● 1995 — Windows 95 released ● Also, a set of compilers, ● 1995 — The GIMP released userspace tools, editors, etc. ● 1996 — KDE Announced This was an overtly political movement and act A Brief History of GNOME 6 Setting the stage ● 1984 — X Windows created at MIT “The licenses for most software are ● 1985 — GNU Manifesto designed to take away your freedom to ● 1991 — GNU General Public License share and change it. By contrast, the v2.0 GNU General Public License is intended to guarantee your freedom to share and ● 1991 — Initial Linux release change free software--to make sure the ● 1991 — Era of big projects software is free for all its users.
  • Secure Boot UEFI Secure Boot, Trusted Firmware Grub 2, Tboot

    Secure Boot UEFI Secure Boot, Trusted Firmware Grub 2, Tboot

    Design and Implementation of a Security Architecture for Critical Infrastructure Industrial Control Systems in the Era of Nation State Cyber Warfare David Safford, Bill Smith, Monty Wiseman LSS, 2016 GE Global Research Center Imagination at work. GE: • Half of the world’s installed Power Generation (PG) base is from GE • 10,000 gas and steam turbine generating units • Over 1,000,000 megawatts of installed capacity in 120 countries. • https://powergen.gepower.com/products/heavy-duty-gas-turbines.html • 40% share of the worldwide market for new PG equipment. • http://www.statista.com/statistics/381088/global-market-share-of-power- generation-equipment-manufacturers/ • Largest supplier of Transmission & Distribution (T&D) equipment in the United States, top three worldwide. • http://microgridmedia.com/ge-becomes-globa-utility-td-powerhouse/ • https://medium.com/@GE_Grid/a-vision-to-power-the-world- 74349a3c98a6#.ehjw5t7v8 3 Controls in The Era of Nation State Cyber Attacks At RSA 2016, Admiral Michael Rogers, head of the NSA and the US Cyber Command, told delegates during his keynote address at RSA 2016 that the number one thing that keeps him awake at night is a cyber attack against US critical infrastructure, which is only a matter of when, not if, it will happen. http://www.theregister.co.uk/2016/03/01/nsa_boss_three_security_ nightmares/ Stuxnet compromised the control systems for Iran’s nuclear centrifuges, rendering them useless. It attacked them successfully despite a state of the art air-gap defense. http://threatjournal.com/archive/tj12072013.html Ukraine’s electric grid was shut down for 8 hours by a cyber attack, which wiped all control system computers, and bricked critical control interfaces.
  • Step-By-Step Strategies and Case Studies for Embedded Software Companies to Adapt to the FOSS Ecosystem Suhyun Kim, Jaehyun Yoo, Myunghwa Lee

    Step-By-Step Strategies and Case Studies for Embedded Software Companies to Adapt to the FOSS Ecosystem Suhyun Kim, Jaehyun Yoo, Myunghwa Lee

    Step-by-Step Strategies and Case Studies for Embedded Software Companies to Adapt to the FOSS Ecosystem Suhyun Kim, Jaehyun Yoo, Myunghwa Lee To cite this version: Suhyun Kim, Jaehyun Yoo, Myunghwa Lee. Step-by-Step Strategies and Case Studies for Embed- ded Software Companies to Adapt to the FOSS Ecosystem. 8th International Conference on Open Source Systems (OSS), Sep 2012, Hammamet, Tunisia. pp.48-60, 10.1007/978-3-642-33442-9_4. hal-01519083 HAL Id: hal-01519083 https://hal.inria.fr/hal-01519083 Submitted on 5 May 2017 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Distributed under a Creative Commons Attribution| 4.0 International License Step-by-Step Strategies and Case Studies for Embedded Software Companies to Adapt to the FOSS Ecosystem Suhyun Kim, Jaehyun Yoo, and Myunghwa Lee Software Engineering Lab, Software R&D Center, Samsung Electronics 416 Maetan-Dong, Yeongtong-Gu, Suwon, Gyeonggi-Do 443-742, Korea {suhyun47.kim, sjh.yoo, mhlee}@samsung.com WWW home page: https://opensource.samsung.com Abstract Due to the continuous expansion of the FOSS ecosystem and the introduction of high-quality FOSS, FOSS is increasingly used in consumer electronics (CE) such as smartphones, televisions, and cameras.
  • Debian's Support for Secure Boot on X86 And

    Debian's Support for Secure Boot on X86 And

    Debian’s support for Secure Boot on x86 and ARM Ben Hutchings Kernel Recipes, Paris, 2016 Ben Hutchings ● Regular Linux contributor since 2008 ● Working on various drivers and kernel code in my day job ● Debian kernel and LTS team member, now doing most of the kernel maintenance aside from ports ● Maintaining Linux 3.2.y and 3.16.y stable update series on kernel.org ● Kernel maintainer for LF Civil Infrastructure Platform, aiming for super-long-term support Secure Boot ● Optional feature in UEFI - uses certificate store to validate boot loader, UEFI drivers, system firmware updates ● Protects against persistent malware (bootkit / kernel rootkit) if implemented correctly ● Required in 'Designed for Windows' systems since Windows 8 (2012) ● Only common trusted certificates on PCs are for Microsoft signing keys ● MS will sign PC boot loaders for a small fee, and the certificate store is normally editable on PCs ● ARM-based Windows systems are completely locked down ● HPe shipping ARM64 server systems in SB setup mode, allowing installer to set trusted certificates GNU/Linux under Secure Boot ● First stage needs MS signature – manual submission process ● Most distributions introduced 'shim' as first stage boot loader that won't need updating often ● MS expects boot loader and kernel to validate code they load – and it's a good idea anyway ● For later stages, we control certificates and keys – certificates can be embedded in 'shim' ● GRUB needs to validate its modules and kernels ● Linux kernel needs to validate its modules and any other code
  • Open Source Software

    Open Source Software

    OPEN SOURCE SOFTWARE Product AVD9x0x0-0010 Firmware and version 3.4.57 Notes on Open Source software The TCS device uses Open Source software that has been released under specific licensing requirements such as the ”General Public License“ (GPL) Version 2 or 3, the ”Lesser General Public License“ (LGPL), the ”Apache License“ or similar licenses. Any accompanying material such as instruction manuals, handbooks etc. contain copyright notes, conditions of use or licensing requirements that contradict any applicable Open Source license, these conditions are inapplicable. The use and distribution of any Open Source software used in the product is exclusively governed by the respective Open Source license. The programmers provided their software without ANY WARRANTY, whether implied or expressed, of any fitness for a particular purpose. Further, the programmers DECLINE ALL LIABILITY for damages, direct or indirect, that result from the using this software. This disclaimer does not affect the responsibility of TCS. AVAILABILITY OF SOURCE CODE: Where the applicable license entitles you to the source code of such software and/or other additional data, you may obtain it for a period of three years after purchasing this product, and, if required by the license conditions, for as long as we offer customer support for the device. If this document is available at the website of TCS and TCS offers a download of the firmware, the offer to receive the source code is valid for a period of three years and, if required by the license conditions, for as long as TCS offers customer support for the device. TCS provides an option for obtaining the source code: You may obtain any version of the source code that has been distributed by TCS for the cost of reproduction of the physical copy.
  • Op E N So U R C E Yea R B O O K 2 0

    Op E N So U R C E Yea R B O O K 2 0

    OPEN SOURCE YEARBOOK 2016 ..... ........ .... ... .. .... .. .. ... .. OPENSOURCE.COM Opensource.com publishes stories about creating, adopting, and sharing open source solutions. Visit Opensource.com to learn more about how the open source way is improving technologies, education, business, government, health, law, entertainment, humanitarian efforts, and more. Submit a story idea: https://opensource.com/story Email us: [email protected] Chat with us in Freenode IRC: #opensource.com . OPEN SOURCE YEARBOOK 2016 . OPENSOURCE.COM 3 ...... ........ .. .. .. ... .... AUTOGRAPHS . ... .. .... .. .. ... .. ........ ...... ........ .. .. .. ... .... AUTOGRAPHS . ... .. .... .. .. ... .. ........ OPENSOURCE.COM...... ........ .. .. .. ... .... ........ WRITE FOR US ..... .. .. .. ... .... 7 big reasons to contribute to Opensource.com: Career benefits: “I probably would not have gotten my most recent job if it had not been for my articles on 1 Opensource.com.” Raise awareness: “The platform and publicity that is available through Opensource.com is extremely 2 valuable.” Grow your network: “I met a lot of interesting people after that, boosted my blog stats immediately, and 3 even got some business offers!” Contribute back to open source communities: “Writing for Opensource.com has allowed me to give 4 back to a community of users and developers from whom I have truly benefited for many years.” Receive free, professional editing services: “The team helps me, through feedback, on improving my 5 writing skills.” We’re loveable: “I love the Opensource.com team. I have known some of them for years and they are 6 good people.” 7 Writing for us is easy: “I couldn't have been more pleased with my writing experience.” Email us to learn more or to share your feedback about writing for us: https://opensource.com/story Visit our Participate page to more about joining in the Opensource.com community: https://opensource.com/participate Find our editorial team, moderators, authors, and readers on Freenode IRC at #opensource.com: https://opensource.com/irc .