DOCSLIB.ORG

Extr-EXOS Warranty Regarding Use of Open Source Software Open

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Extr-EXOS Warranty Regarding Use of Open Source Software Open Open Source Declaration for: extr-EXOS Software Release: Versions: 30.6 Release Date: 2020-03-13 This document contains attributions, licenses, and notices for free and open source software (Collectively FOSS) used within this product. If you have any questions or wish to receive a copy of any FOSS source code to which you may be entitled, please contact us at [email protected]. Extreme Networks, Inc 6480 Via Del Oro San Jose, California 95119 Phone / +1 408.904.7002 Toll-free / + 1 888.257.3000 www.extremenetworks.com © 2019 Extreme Networks, Inc. All rights reserved. Extreme Networks, the Extreme Networks logo, and "Project Names" are trademarks or registered trademarks of Extreme Networks, Inc. in the United States and/or other countries. All other names, registered trademarks, trademarks, and service marks are property of their respective owners. For additional information on Extreme Networks trademarks, see www.extremenetworks.com/company/legal/trademarks Warranty Regarding Use of Open Source Software This FOSS is provided to you on an "as is" basis, and Extreme Networks makes no representations or warranties for the use of this code by you independent of any Extreme Networks provided software or services. Refer to the licenses and copyright notices listed below for each package for any specific license terms that apply to each software bundle. The licenses listed below define the warranty, if any, from the associated authors or licensors. Extreme Networks specifically disclaims any warranties for defects caused caused by altering or modifying any FOSS or the products' recommended configuration. You have no warranty or indemnification claims against Extreme Networks in the event that the FOSS infringes the intellectual property rights of a third party. Technical support, if any, will only be provided for the unmodified Extreme Networks product as used within such product's recommended configuration. Open Source Software Used in the Product Name Version URL License Apache @bloombox/js-client 1.1.0 https://github.com/Bloombox/JS#readme License 2.0 (GNU Lesser General Public License v2.1 ACL 2.2.52 http://savannah.nongnu.org/projects/acl or later AND GNU General Public License v2.0 or later) Android - platform - Apache platform-tools-29.0.3 http://github.com/android/platform_system_core/ frameworks - base License 2.0 Angular Dialog Service v1.0 https://github.com/m-e-conroy/angular-dialog-service MIT License angular-loading-bar 0.1.0 https://github.com/chieffancypants/angular-loading-bar MIT License angular-route v1.2.1 http://angularjs.org MIT License BSD 3-clause "New" or ASN.1 library for Python 0.1.9 http://sourceforge.net/projects/pyasn1 "Revised" License GNU Lesser General Public avahi 0.7 http://avahi.org License v2.1 or later GNU General avocado-test-framework 73.0 http://avocado-framework.readthedocs.org/en/latest/ Public License v2.0 or later GNU General axboe/fio fio-2.9 https://github.com/axboe/fio/archive/fio-3.12.tar.gz Public License v2.0 or later BIND (Berkeley Internet Name Mozilla Public 9.11.2 https://www.isc.org/wordpress/software/bind/ Domain) License 2.0 BIND (Berkeley Internet Name 9.11.2.P1 https://www.isc.org/wordpress/software/bind/ Mozilla Public Domain) License 2.0 Unknown Bitbake yocto-2.1 http://developer.berlios.de/projects/bitbake/ License bloggify-share-term 1.1.0 http://share-term.me/ MIT License GNU General bluez 5.48 http://www.bluez.org/ Public License v2.0 or later Boost Boost C++ Libraries 1.62.0.beta.2 http://tim.klingt.org/git?p=boost_lockfree.git; Software License 1.0 (GNU General Public License v2.0 or later boot-floppies 2.2.26 OR GNU General Public License v1.0 only) Bootstrap (Twitter) unknown http://getbootstrap.com/ MIT License Apache Bootstrap (Twitter) 3.0.2 http://getbootstrap.com/ License 2.0 bower-angular v1.2.1 https://github.com/angular/bower-angular MIT License bower-angular-animate v1.2.1 MIT License bower-angular-resource v1.2.1 https://github.com/angular/bower-angular-resource MIT License bower-angular-sanitize v1.2.1 https://github.com/angular/bower-angular-sanitize MIT License GNU General BusyBox 1_28_4 https://busybox.net/ Public License v2.0 only BSD 3-clause "New" or capstone-devel 3.0.5 http://www.capstone-engine.org/ "Revised" License GNU Lesser General Public Check 0.9.9 http://check.sourceforge.net/ License v2.1 or later BSD 3-clause "New" or CherryPy 3.6.0 http://www.cherrypy.org/ "Revised" License Apache cherrypy-cors 1.3 https://bitbucket.org/yougov/cherrypy-cors/ License 2.0 BSD 3-clause "New" or com.github.transcurity:capstone 3.0.5-rc2 "Revised" License com.tagtraum:libz 4.0.0 zlib License cURL 7.66.0 https://curl.haxx.se/ MIT License cURL 7.61.0 https://curl.haxx.se/ curl License Carnegie Mellon Cyrus SASL 2.1.23 http://asg.web.cmu.edu/sasl/ University License (GNU General Public License v2.0 or later D-Bus 1.12.2 http://www.freedesktop.org/wiki/Software/dbus OR Academic Free License v2.1) (GNU General Public License v2.0 or later dbus-glib 0.108 http://dbus.freedesktop.org OR Academic Free License v2.1) GNU General devtoolset-8-binutils 2.30 https://sourceware.org/binutils Public License v3.0 or later DHCP (ISC) 4.4.1 http://www.isc.org/downloads/dhcp/ ISC License GNU General Dnsmasq 2.78 http://www.thekelleys.org.uk/dnsmasq/doc.html Public License v2.0 only GNU General Dnsmasq 2.79 http://www.thekelleys.org.uk/dnsmasq/doc.html Public License v2.0 only GNU General dosfstools 2.11 http://www.daniel-baumann.ch/software/dosfstools/ Public License v2.0 or later GNU General Dulwich 0.10.0 https://www.dulwich.io/ Public License v2.0 or later GNU General e2fsprogs 1.43.8 http://ext4.wiki.kernel.org/ Public License v2.0 or later GNU General elfutils 0.170 http://elfutils.org/ Public License v2.0 or later (GNU Lesser General Public License v2.1 or later AND ffi 1.0.9 http://wiki.github.com/ffi/ffi BSD 3-clause "New" or "Revised" License) BSD 3-clause "New" or ffi 1.9.21 http://wiki.github.com/ffi/ffi "Revised" License GNU General fio 2.2.10 http://freshmeat.net/projects/fio Public License v2.0 only BSD 3-clause "New" or Flask 0.10.1 http://flask.pocoo.org/ "Revised" License Flask-Cors 2.1.0 https://flask-cors.corydolphin.com/ MIT License flask-httpauth 2.7.0 https://github.com/miguelgrinberg/flask-httpauth MIT License BSD 3-clause 20161128-snapshot- "New" or flask-jsonrpc https://github.com/cenobites/flask-jsonrpc c7f8e049 "Revised" License Flask-JsonSchema 0.1.1 https://github.com/mattupstate/flask-jsonschema MIT License Creative Font Awesome 4.0.3-1 Commons Attribution 3.0 future 0.16.0 http://python-future.org/ MIT License GNU General Gawk 4.2.1 http://www.gnu.org/software/gawk/ Public License v3.0 or later GNU General GDB 8.0.1 http://www.gnu.org/software/gdb/ Public License v3.0 or later GNU General GDB 8.0.90.20180111 http://www.gnu.org/software/gdb/ Public License v3.0 or later GNU General gkernel: rng-tools / ethtool v4.16 http://www.kernel.org/pub/software/network/ethtool/ Public License v2.0 or later GMP 6.1.2 http://gmplib.org/ (GNU Lesser General Public License v3.0 or later AND GNU General Public License v2.0 or later AND GNU General Public License v3.0 or later) GNU General GNU Binutils 2.29.90.20180122 http://www.gnu.org/software/binutils/ Public License v3.0 or later GNU General GNU Binutils 2.30 http://www.gnu.org/software/binutils/ Public License v3.0 or later (GNU Library General Public License v2 or later AND GNU General GNU C Library 2.27 http://www.gnu.org/software/libc/ Public License v2.0 or later AND Unknown License) BSD 4-clause GNU Compiler Collection 6.3.0 http://gcc.gnu.org/ "Original" or "Old" License GNU General GNU cpio 2.12 http://www.gnu.org/software/cpio/ Public License v3.0 or later (GNU Lesser General Public License v3.0 GNU libunistring 0.9.9 https://www.gnu.org/software/libunistring/ or later OR GNU General Public License v2.0 or later) Free Software Foundation - GNU Ncurses 6.0 http://www.gnu.org/software/ncurses/ MIT License (MIT +) GNU General GnuTLS 3.6.1 http://www.gnutls.org Public License v3.0 or later BSD 3-clause Google C++ Testing "New" or 1.7.0 https://github.com/google/googletest/ Framework "Revised" License Apache Google Code Prettify 3.3.4.2013 https://github.com/google/code-prettify License 2.0 (BSD 3-clause "New" or "Revised" Google Mock 1.7.0-18092013 http://code.google.com/p/googlemock/ License OR GNU General Public License v3.0 or later) gorakhargosh/pathtools 0.1.2 https://github.com/gorakhargosh/pathtools MIT License (gSoap Public License Version 1.3a License OR gSOAP 2.7.6d http://sourceforge.net/projects/gsoap2 Erlang Public License v1.1 OR Terracotta Public License) gSOAP gSOAP 2.7.9e stable http://sourceforge.net/projects/gsoap2 (gSoap Public License Version 1.3a License OR Genivia gSOAP Commercial License OR GNU General Public License v2.0 or later) Handlebars.js 1.1.2 http://handlebarsjs.com MIT License BSD 3-clause "New" or hiredis 0.13.3 http://github.com/antirez/hiredis "Revised" License BSD 3-clause "New" or holzschu/ios_system v1.2 http://github.com/holzschu/ios_system/ "Revised" License httpagentparser 1.7.8 http://pypi.python.org/pypi/httpagentparser/ MIT License GNU General ibus-rime 1.3.2 http://code.google.com/p/rimeime/ Public License v3.0 or later ICU for Java (ICU4J) 57.1 http://icu-project.org ICU License Apache impacket 0.9.11 http://code.google.com/p/impacket/ License 1.1 BSD 3-clause "New" or IPFIX library libipfix-1.0 http://sourceforge.net/projects/libipfix "Revised" License GNU General iproute2 4.15.0 http://www.linuxfoundation.org/collaborate/workgroups/networking/iproute2
Load more

Recommended publications
  • UNIX and Computer Science Spreading UNIX Around the World: by Ronda Hauben an Interview with John Lions
    Winter/Spring 1994 Celebrating 25 Years of UNIX Volume 6 No 1 "I believe all significant software movements start at the grassroots level. UNIX, after all, was not developed by the President of AT&T." Kouichi Kishida, UNIX Review, Feb., 1987 UNIX and Computer Science Spreading UNIX Around the World: by Ronda Hauben An Interview with John Lions [Editor's Note: This year, 1994, is the 25th anniversary of the [Editor's Note: Looking through some magazines in a local invention of UNIX in 1969 at Bell Labs. The following is university library, I came upon back issues of UNIX Review from a "Work In Progress" introduced at the USENIX from the mid 1980's. In these issues were articles by or inter- Summer 1993 Conference in Cincinnati, Ohio. This article is views with several of the pioneers who developed UNIX. As intended as a contribution to a discussion about the sig- part of my research for a paper about the history and devel- nificance of the UNIX breakthrough and the lessons to be opment of the early days of UNIX, I felt it would be helpful learned from it for making the next step forward.] to be able to ask some of these pioneers additional questions The Multics collaboration (1964-1968) had been created to based on the events and developments described in the UNIX "show that general-purpose, multiuser, timesharing systems Review Interviews. were viable." Based on the results of research gained at MIT Following is an interview conducted via E-mail with John using the MIT Compatible Time-Sharing System (CTSS), Lions, who wrote A Commentary on the UNIX Operating AT&T and GE agreed to work with MIT to build a "new System describing Version 6 UNIX to accompany the "UNIX hardware, a new operating system, a new file system, and a Operating System Source Code Level 6" for the students in new user interface." Though the project proceeded slowly his operating systems class at the University of New South and it took years to develop Multics, Doug Comer, a Profes- Wales in Australia.
    [Show full text]
  • CA Gen Integration Consuming REST Services – C Edition
    CA Gen Integration Consuming REST Services – C Edition Christian Kersters Broadcom Limited Web: www.broadcom.com Corporate Headquarters: San Jose, CA Broadcom Proprietary. © 2020 Broadcom. All rights reserved. Consuming REST Services – C Edition Revision History Revision Date Change Description V0.9 2020/11/12 Initial version V1.0 2020/11/17 Revised edition (integration of C. Jamar suggestions) Broadcom Proprietary. © 2020 Broadcom. All rights reserved. 1 Consuming REST Services – C Edition References CA Gen Integration Solutions, Christian Kersters, Broadcom, August 2017 https://community.broadcom.com/HigherLogic/System/DownloadDocumentFile.ashx?Docum entFileKey=4a401797-4dfe-4230-a031-273b908e57d3&forceDialog=0 Hello world: getting started with REST APIs https://www.genivia.com/dev.html#how-rest gSOAP User Guide https://www.genivia.com/doc/guide/html/index.html Richardson Maturity Model https://restfulapi.net/richardson-maturity-model/ Broadcom Proprietary. © 2020 Broadcom. All rights reserved. 2 Consuming REST Services – C Edition Contents Revision History ......................................................................................................................... 1 References ................................................................................................................................. 2 Contents ..................................................................................................................................... 3 1. Introduction ........................................................................................................................
    [Show full text]
  • Licensing 101 December 3, 2020 Meet the Speakers
    Licensing 101 December 3, 2020 Meet The Speakers Sushil Iyer Adam Kessel Principal Principal fr.com | 2 Roadmap • High level, introductory discussion on IP licensing • Topics – Types of IP – Monetization strategies – Key parts of a license agreement – Certain considerations • Licensing software, especially open source software • Licensing pharmaceutical patents • Trademarks • Trade secrets • Know-how fr.com | 3 Types of IP Patents Trademarks Copyrights Know-how (including trade secrets) fr.com | 4 Monetization Strategies • IP licensing – focus of this presentation – IP owner (licensor) retains ownership and grants certain rights to licensee – IP licensee obtains the legal rights to practice the IP – Bundle of rights can range from all the rights that the IP owner possesses to a subset of the same • Sale – IP owner (assignor) transfers ownership to the purchaser (assignee) • Litigation – Enforcement, by IP owner, of IP rights against an infringer who impermissibly practices the IP owner’s rights – Damages determined by a Court fr.com | 5 What is an IP License? • Contract between IP owner (Licensor) and Licensee – Licensor’s offer – grant of Licensor’s rights in IP • Patents – right to sell products that embody claimed inventions of Licensor’s US patents • Trademarks – right to use Licensor’s US marks on products or when selling products • Copyright – right to use and/or make derivative works of Licensor’s copyrighted work • Trade Secret – right to use and obligation to maintain Licensor’s trade secret – Licensee’s consideration – compensation
    [Show full text]
  • Python 2.6.2 License 04.11.09 14:37
    Python 2.6.2 license 04.11.09 14:37 Download > Releases > License Python 2.6.2 license This is the official license for the Python 2.6.2 release: A. HISTORY OF THE SOFTWARE ========================== Python was created in the early 1990s by Guido van Rossum at Stichting Mathematisch Centrum (CWI, see http://www.cwi.nl) in the Netherlands as a successor of a language called ABC. Guido remains Python's principal author, although it includes many contributions from others. In 1995, Guido continued his work on Python at the Corporation for National Research Initiatives (CNRI, see http://www.cnri.reston.va.us) in Reston, Virginia where he released several versions of the software. In May 2000, Guido and the Python core development team moved to BeOpen.com to form the BeOpen PythonLabs team. In October of the same year, the PythonLabs team moved to Digital Creations (now Zope Corporation, see http://www.zope.com). In 2001, the Python Software Foundation (PSF, see http://www.python.org/psf/) was formed, a non-profit organization created specifically to own Python-related Intellectual Property. Zope Corporation is a sponsoring member of the PSF. All Python releases are Open Source (see http://www.opensource.org for the Open Source Definition). Historically, most, but not all, Python releases have also been GPL-compatible; the table below summarizes the various releases. Release Derived Year Owner GPL- from compatible? (1) 0.9.0 thru 1.2 1991-1995 CWI yes 1.3 thru 1.5.2 1.2 1995-1999 CNRI yes 1.6 1.5.2 2000 CNRI no 2.0 1.6 2000 BeOpen.com no 1.6.1
    [Show full text]
  • Practice Tips for Open Source Licensing Adam Kubelka
    Santa Clara High Technology Law Journal Volume 22 | Issue 4 Article 4 2006 No Free Beer - Practice Tips for Open Source Licensing Adam Kubelka Matthew aF wcett Follow this and additional works at: http://digitalcommons.law.scu.edu/chtlj Part of the Law Commons Recommended Citation Adam Kubelka and Matthew Fawcett, No Free Beer - Practice Tips for Open Source Licensing, 22 Santa Clara High Tech. L.J. 797 (2005). Available at: http://digitalcommons.law.scu.edu/chtlj/vol22/iss4/4 This Article is brought to you for free and open access by the Journals at Santa Clara Law Digital Commons. It has been accepted for inclusion in Santa Clara High Technology Law Journal by an authorized administrator of Santa Clara Law Digital Commons. For more information, please contact [email protected]. ARTICLE NO FREE BEER - PRACTICE TIPS FOR OPEN SOURCE LICENSING Adam Kubelkat Matthew Fawcetttt I. INTRODUCTION Open source software is big business. According to research conducted by Optaros, Inc., and InformationWeek magazine, 87 percent of the 512 companies surveyed use open source software, with companies earning over $1 billion in annual revenue saving an average of $3.3 million by using open source software in 2004.1 Open source is not just staying in computer rooms either-it is increasingly grabbing intellectual property headlines and entering mainstream news on issues like the following: i. A $5 billion dollar legal dispute between SCO Group Inc. (SCO) and International Business Machines Corp. t Adam Kubelka is Corporate Counsel at JDS Uniphase Corporation, where he advises the company on matters related to the commercialization of its products.
    [Show full text]
  • Ironpython in Action
    IronPytho IN ACTION Michael J. Foord Christian Muirhead FOREWORD BY JIM HUGUNIN MANNING IronPython in Action Download at Boykma.Com Licensed to Deborah Christiansen <[email protected]> Download at Boykma.Com Licensed to Deborah Christiansen <[email protected]> IronPython in Action MICHAEL J. FOORD CHRISTIAN MUIRHEAD MANNING Greenwich (74° w. long.) Download at Boykma.Com Licensed to Deborah Christiansen <[email protected]> For online information and ordering of this and other Manning books, please visit www.manning.com. The publisher offers discounts on this book when ordered in quantity. For more information, please contact Special Sales Department Manning Publications Co. Sound View Court 3B fax: (609) 877-8256 Greenwich, CT 06830 email: [email protected] ©2009 by Manning Publications Co. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by means electronic, mechanical, photocopying, or otherwise, without prior written permission of the publisher. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in the book, and Manning Publications was aware of a trademark claim, the designations have been printed in initial caps or all caps. Recognizing the importance of preserving what has been written, it is Manning’s policy to have the books we publish printed on acid-free paper, and we exert our best efforts to that end. Recognizing also our responsibility to conserve the resources of our planet, Manning books are printed on paper that is at least 15% recycled and processed without the use of elemental chlorine.
    [Show full text]
  • An Introduction to Software Licensing
    An Introduction to Software Licensing James Willenbring Software Engineering and Research Department Center for Computing Research Sandia National Laboratories David Bernholdt Oak Ridge National Laboratory Please open the Q&A Google Doc so that I can ask you Michael Heroux some questions! Sandia National Laboratories http://bit.ly/IDEAS-licensing ATPESC 2019 Q Center, St. Charles, IL (USA) (And you’re welcome to ask See slide 2 for 8 August 2019 license details me questions too) exascaleproject.org Disclaimers, license, citation, and acknowledgements Disclaimers • This is not legal advice (TINLA). Consult with true experts before making any consequential decisions • Copyright laws differ by country. Some info may be US-centric License and Citation • This work is licensed under a Creative Commons Attribution 4.0 International License (CC BY 4.0). • Requested citation: James Willenbring, David Bernholdt and Michael Heroux, An Introduction to Software Licensing, tutorial, in Argonne Training Program on Extreme-Scale Computing (ATPESC) 2019. • An earlier presentation is archived at https://ideas-productivity.org/events/hpc-best-practices-webinars/#webinar024 Acknowledgements • This work was supported by the U.S. Department of Energy Office of Science, Office of Advanced Scientific Computing Research (ASCR), and by the Exascale Computing Project (17-SC-20-SC), a collaborative effort of the U.S. Department of Energy Office of Science and the National Nuclear Security Administration. • This work was performed in part at the Oak Ridge National Laboratory, which is managed by UT-Battelle, LLC for the U.S. Department of Energy under Contract No. DE-AC05-00OR22725. • This work was performed in part at Sandia National Laboratories.
    [Show full text]
  • Vxworks Third Party Software Notices
    Wind River® VxWorks® 7 Third Party License Notices This document contains third party intellectual property (IP) notices for the BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY Wind River® VxWorks® 7 distribution. Certain licenses and license notices THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, may appear in other parts of the product distribution in accordance with the OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN license requirements. ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. Trademarks All company, product and service names used in this software are for ACPICA identification purposes only. Version: 20170303 Component(s): Runtime Wind River and VxWorks are registered trademarks of Wind River Systems. Description: Provides code to implement ACPI specification in VxWorks. UNIX is a registered trademark of The Open Group. IBM and Bluemix are registered trademarks of the IBM Corporation. NOTICES: All other third-party trademarks are the property of their respective owners. 1. Copyright Notice Some or all of this work - Copyright (c) 1999 - 2016, Intel Corp. All rights reserved. Third Party Notices 2. License 2.1. This is your license from Intel Corp. under its intellectual property rights. You may have additional license terms from the party that provided you this software, covering your right to use that party's intellectual property rights. 64-Bit Dynamic Linker Version: 2.2. Intel grants, free of charge, to any person ("Licensee") obtaining a copy Component(s): Runtime of the source code appearing in this file ("Covered Code") an irrevocable, Description: The dynamic linker is used to load shared libraries.
    [Show full text]
  • Single-Node CUCM Single-Node IMP 10.201.203.76 10.201.203.75 10.201.203.67 10.201.203.72
    #CLUS CCIE Collaboration Techtorial Ben Ng, Exam PM, L@C, Cisco CX Ishan Sambhi, CSE, Cisco CX TECCCIE-3503 #CLUS Agenda • Session 1: CCIE® Program Overview • Session 2: CCIE Collaboration Overview • Session 3: CCIE Collaboration Modular Lab Exams • Session 4: Lab Exam Diagnostic Module with Case Studies • Session 5: Lab Exam Troubleshooting Module with Case Studies • Session 6: Lab Exam Configuration Module with Case Studies • Session 7: Exam Preparation Tips, In-Lab Strategies, and Q&A #CLUS TECCCIE-3503 © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 3 Cisco Webex Teams Questions? Use Cisco Webex Teams to chat with the speaker after the session How 1 Find this session in the Cisco Live Mobile App 2 Click “Join the Discussion” 3 Install Webex Teams or go directly to the team space 4 Enter messages/questions in the team space Webex Teams will be moderated cs.co/ciscolivebot#TECCCIE-3503 by the speaker until June 16, 2019. #CLUS © 2019 Cisco and/or its affiliates. All rights reserved. Cisco Public 4 Session 1: CCIE Program Overview Cisco CCIE Certifications CCIE Track Major Skills R&S Configure and troubleshoot complex converged networks Security Configure complex, end-to-end secure networks, troubleshoot environments, and anticipate and respond to network attacks Service Provider Configure and troubleshoot advanced technologies to support service provider networks Collaboration Design, implement, integrate, and troubleshoot complex collaboration networks Wireless Plan, design, implement, operate, and troubleshoot wireless network and mobility infrastructure Data Center Configure and troubleshoot Cisco Data Center technologies including DC infrastructure, compute and virtualization. #CLUS TECCCIE-3503 © 2019 Cisco and/or its affiliates.
    [Show full text]
  • ** OPEN SOURCE LIBRARIES USED in Tv.Verizon.Com/Watch
    ** OPEN SOURCE LIBRARIES USED IN tv.verizon.com/watch ------------------------------------------------------------ 02/27/2019 tv.verizon.com/watch uses Node.js 6.4 on the server side and React.js on the client- side. Both are Javascript frameworks. Below are the licenses and a list of the JS libraries being used. ** NODE.JS 6.4 ------------------------------------------------------------ https://github.com/nodejs/node/blob/master/LICENSE Node.js is licensed for use as follows: """ Copyright Node.js contributors. All rights reserved. Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. """ This license applies to parts of Node.js originating from the https://github.com/joyent/node repository: """ Copyright Joyent, Inc. and other Node contributors.
    [Show full text]
  • Mcafee Potentially Unwanted Programs (PUP) Policy March, 2018
    POLICY McAfee Potentially Unwanted Programs (PUP) Policy March, 2018 McAfee recognizes that legitimate technologies such as commercial, shareware, freeware, or open source products may provide a value or benefit to a user. However, if these technologies also pose a risk to the user or their system, then users should consent to the behaviors exhibited by the software, understand the risks, and have adequate control over the technology. McAfee refers to technologies with these characteristics as “potentially unwanted program(s),” or “PUP(s).” The McAfee® PUP detection policy is based on the process includes assessing the risks to privacy, security, premise that users should understand what is being performance, and stability associated with the following: installed on their systems and be notified when a ■ Distribution: how users obtain the software including technology poses a risk to their system or privacy. advertisements, interstitials, landing-pages, linking, PUP detection and removal is intended to provide and bundling notification to our users when a software program or technology lacks sufficient notification or control over ■ Installation: whether the user can make an informed the software or fails to adequately gain user consent to decision about the software installation or add- the risks posed by the technology. McAfee Labs is the ons and can adequately back out of any undesired McAfee team responsible for researching and analyzing installations technologies for PUP characteristics. ■ Run-Time Behaviors: the behaviors exhibited by the technology including advertisements, deception, and McAfee Labs evaluates technologies to assess any impacts to privacy and security risks exhibited by the technology against the degree of user notification and control over the technology.
    [Show full text]
  • Toolchains Instructor: Prabal Dutta Date: October 2, 2012
    EECS 373: Design of Microprocessor-Based Systems Fall 2012 Lecture 3: Toolchains Instructor: Prabal Dutta Date: October 2, 2012 Note: Unless otherwise specified, these notes assume: (i) an ARM Cortex-M3 processor operating in little endian mode; (ii) the ARM EABI application binary interface; and (iii) the GNU GCC toolchain. Toolchains A complete software toolchain includes programs to convert source code into binary machine code, link together separately assembled/compiled code modules, disassemble the binaries, and convert their formats. Binary program file (.bin) Assembly Object Executable files (.s) files (.o) image file objcopy ld (linker) as objdump (assembler) Memory layout Disassembled Linker code (.lst) script (.ld) Figure 0.1: Assembler Toolchain. A typical GNU (GNU's Not Unix) assembler toolchain includes several programs that interact as shown in Figure 0.1 and perform the following functions: • as is the assembler and it converts human-readable assembly language programs into binary machine language code. It typically takes as input .s assembly files and outputs .o object files. • ld is the linker and it is used to combine multiple object files by resolving their external symbol references and relocating their data sections, and outputting a single executable file. It typically takes as input .o object files and .ld linker scripts and outputs .out executable files. • objcopy is a translation utility that copies and converts the contents of an object file from one format (e.g. .out) another (e.g. .bin). • objdump is a disassembler but it can also display various other information about object files. It is often used to disassemble binary files (e.g.
    [Show full text]