DOCSLIB.ORG

Proceedings of the 14Th Systems Administration Conference (LISA 2000)

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Proceedings of the 14Th Systems Administration Conference (LISA 2000) USENIX Association Proceedings of the 14th Systems Administration Conference (LISA 2000) New Orleans, Louisiana, USA December 3– 8, 2000 THE ADVANCED COMPUTING SYSTEMS ASSOCIATION © 2000 by The USENIX Association All Rights Reserved For more information about the USENIX Association: Phone: 1 510 528 8649 FAX: 1 510 548 5738 Email: [email protected] WWW: http://www.usenix.org Rights to individual papers remain with the author or the author's employer. Permission is granted for noncommercial reproduction of the work for educational or research purposes. This copyright notice must be included in the reproduced paper. USENIX acknowledges all trademarks herein. Automating Request-based Software Distribution Chris Hemmerich – Indiana University ABSTRACT Request-based distribution of software applications over a network is a difficult problem that many organizations face. While several programs address this issue, many lack features required for more sophisticated exports, and more complex solutions usually have a very limited scope. Managing these exports by hand is usually a time consuming and error-prone task. We were in such a situation when we developed the Automated Netdist program a year ago. Automated Netdist provides an automated mechanism for system administrators to request and receive software exports with an immediate turnaround. The system provides a simple user interface, secure authentication, and both user and machine based authentication. Each of these is configurable on a package-by-package basis for flexibility. Netdist is a modular service. The user interface, authentication and authorization are independent of the export protocol. We are currently distributing via NFS, but adding an additional protocol is as simple as writing a script to perform the export and plugging it into Netdist. Introduction • Open NFS exports At Indiana University, we have a large, extended, • Request based NFS exports and heterogeneous Unix workstation presence admin- • Media Checkout istered by many different departments and organiza- • Vendor Specific Distribution Tools tions. The Unix Workstation Support Group (UWSG) Anonymous FTP is charged with supporting and advising the adminis- The majority of the software we distribute is via trators of these machines. This includes offering a anonymous FTP. We maintain a large (150GB+) site at variety of systems administration classes, negotiating ftp.uwsg.iu.edu. This FTP site is our preferred method and maintaining site licenses with various vendors, of distributing files. This archive is available to the distributing a large variety of unix software, and main- world and contains mirrors of most of the large Linux taining a Unix Users Group. We also provide tradi- distributions, a CPAN mirror, a mirror of the Linux tional phone, e-mail, face-to-face, and extended con- kernel archives, various freeware programs and utili- tact support services. ties, and system patches. The benefits of this system At the time Netdist was developed the UWSG are many: consisted of six members, five full-time and one part- • It supports many concurrent users, and is lim- time, distributed across two campuses. This is a lot of ited only by our current hardware and the uni- ground for such a small group to cover, and we are versity’s bandwidth. always looking for ways to increase the efficiency of • It is available to anyone in the world with FTP our services without sacrificing quality or our cus- access. tomers’ satisfaction. In early 1999, I was given the • It is easy to use, and the ratio of support inci- task of re-working one of our least efficient and least dents to usage is orders of magnitude smaller reliable services, the request-triggered distribution of than any other service we maintain. software via NFS. • It is efficient to administer, requiring little Software Distribution maintenance. • It is a very well known system, and administra- The UWSG distributes a large and varied collec- tion can be shared or passed on easily. tion of Unix software, to a widely varied audience. Software export laws, license agreements, pre-existing Unfortunately, anonymous FTP is not a viable vendor-supplied distribution systems, varying security tool for all of our distribution needs. Following are requirements, and machines with slow or non-existent several of it’s limitations that have forced us to dis- network connection all work together to fragment our tribute packages using alternate methods. software distribution into the following components. • Access control is very limited. We maintain a These components are the environment out of which distinction between Indiana University (IU) Netdist grew, and their attributes greatly influenced clients and non-IU clients. Anything beyond the development on Netdist. this becomes much more difficult to administer • Anonymous FTP as the target audience shrinks and the complex- • Secure HTTP Access ity of administration increases. 2000 LISA XIV – December 3-8, 2000 – New Orleans, LA 197 Automating Request-based Software Distribution Hemmerich • Security is poor. FTP has a long history of This has been a very labor intensive service for us, as security deficiencies, vulnerabilities, and we must manage the physical storage of these CDs, exploits. We don’t make any sensitive data make copies of popular requests, keep track of who available via FTP, allow authenticated logins, has checked out what, and gently remind admins when or allow write access. they’ve kept a CD too long. A separate project to • We provide operating system media for system resolve the inefficiencies in this process is currently installations, and most operating systems aren’t wrapping up, with wonderful results. able to be installed over an FTP connection. This process is secure, and convenient for Several Linux distributions support this, but we administrators to install from. It also provides those must also provide Solaris, HP-UX, IRIX, and with only a modem or no network connection a means other Unix flavors that do not. of acquiring software. It is, however, horribly ineffi- • FTP sites cannot be mounted as local file sys- cient, generally requiring 15-30 minutes of work per tems. We offer several large software packages, request. We must respond to the request, obtain the and users might not have the free space to physical media, schedule a pickup time, meet the cus- download a large software package, uncom- tomer, check their identification, register the checkout press it, and then install it. into our tracking system, and then collect the software. Secure HTTP Access Vendor Specific Distribution Tools For software that needs to be firmly restricted to We use vendor-specific software distribution IU affiliates we use an Apache web server running tools from both HP and SGI. Both of these tools use SSL and an in-house mod_perl module that allows us remote procedure calls for transferring software to securely authenticate users against the University patches, updates, and new packages. These tools are wide kerberos database. This system is useful for dis- convenient for administrators on campus to use, and tributing smaller packages and we use it to distribute required little administration. Both of these tools are export-restricted security software, as well as IU-spe- proprietary software, and limited in the software they cific license codes for several software packages that can serve and the clients that can access them. we have licensed. We use the IRIX Network Distribution server to This service addresses the security failings of distribute OS and Software updates as well as new anonymous FTP, but doesn’t address the concerns of packages. In order for a machine to be able to access installing operating systems or dealing with large soft- the server, it must be listed in the servers .rhost file. ware packages. In addition, the server installation and This file tends to get rather large and outdated as time configuration is much more complex than anonymous progresses, and must be pruned periodically. FTP, and the overhead on the server is greater. The HP Software Agent Suite allows us to make Open NFS Exports HP depot files available over the network to HP We maintain open NFS exports of several Linux machines on campus. Depots are automatically avail- distributions for network installs and updates. This is a able to the whole campus, but implementing more convenient way for administrators to set up new granular permissions is a non-trivial task. The system machines over the campus network. As open NFS uses a graphical interface to make patching and install exports lack any real security, we do not export any software painless. other software this way. Indiana University does Request Based NFS exports: The problem block incoming NFS requests from outside the school network, so the exposure is relatively small. Under the old system, an administrator that Request Based NFS Exports wanted StarOffice or Sun WorkShop would send an e- mail message to our group account containing the At the time I began this project, we were export- software requested and the target machine’s hostname. ing Star Office (before it was purchased by Sun) and Upon receiving the message, we would verify that all Sun’s Workshop Compiler Suite through NFS on a of the relevant information was included, and if neces- per-request basis. This allowed us to control who had sary request any information that has been left out. access to the packages, while giving our customers the Then we would edit the NFS exports file by hand to convenience of installing these packages as if they include the client machine and a comment listing were mounted locally as a CD image. Our customers when the export expired. We then re-initialized the were happy with this service, but we were managing it exports and notified the user that the export would be by hand which was inefficient and error-prone. I was valid for three days. Once the export had expired, we assigned the task of replacing this service, when we removed the client hostname manually and then re-ini- learned that several new software packages would be tialized the exports to force the expiration.
Load more

Recommended publications
  • Secure Socket Layer (SSL) Transport Layer Security (TLS)
    Secure Socket Layer (SSL) Transport Layer Security (TLS) © André Zúquete Advanced Network Security TLS (Transport Layer Security, RFC 5246): Goals w Secure communication protocol over TCP/IP ® Standard inspired by SSL V3 (Secure Sockets Layer) ® Handles secure sessions per application over TCP/IP • Initially conceived for HTTP traffic • Currently being used by other kinds of traffic w Security mechanisms ® TCP payload protection • Confidentiality • Stream integrity ® Key distribution ® Peer authentication • Server authentication (the normal scenario) • Client authentication • Usually a person • Not usually explored © André Zúquete Advanced Network Security 1 Change Handshake Alert IMAP, Cipher Protocol Protocol HTTP Spec. etc. IMAP, TLS/SSL: HTTP etc. Protocols Record Protocol w Handshake Protocol TCP ® Key distribution • Master secrets (48 bytes) • Computed with DH; or • Chose by the client, upload to the server encrypted with the server’s public key • Session keys • Computed from a master secret and two nonces exchanged ® Peer authentication • Asymmetric encryption with long-term or ephemeral keys • Public key certificates for long-term public keys w Record Protocol ® Handling of secure data records ® Compression, confidentiality, integrity control © André Zúquete Advanced Network Security TLS/SSL versions w SSL ® 1.0 ® 2.0: 1995, prohibited by RFC 6176 (2011) ® 3.0: 1996, RFC 6101 (2011), deprecated by RFC 7568 (2015) w TLS ® 1.0: 1999: RFC 2246 SSL BEAST (2011) ® 1.1: 2006: RFC 4346 ® 1.2: 2008: RFC 5246 ® 1.3: 2018: RFC 8446 © André
    [Show full text]
  • ROADS and BRIDGES: the UNSEEN LABOR BEHIND OUR DIGITAL INFRASTRUCTURE Preface
    Roads and Bridges:The Unseen Labor Behind Our Digital Infrastructure WRITTEN BY Nadia Eghbal 2 Open up your phone. Your social media, your news, your medical records, your bank: they are all using free and public code. Contents 3 Table of Contents 4 Preface 58 Challenges Facing Digital Infrastructure 5 Foreword 59 Open source’s complicated relationship with money 8 Executive Summary 66 Why digital infrastructure support 11 Introduction problems are accelerating 77 The hidden costs of ignoring infrastructure 18 History and Background of Digital Infrastructure 89 Sustaining Digital Infrastructure 19 How software gets built 90 Business models for digital infrastructure 23 How not charging for software transformed society 97 Finding a sponsor or donor for an infrastructure project 29 A brief history of free and public software and the people who made it 106 Why is it so hard to fund these projects? 109 Institutional efforts to support digital infrastructure 37 How The Current System Works 38 What is digital infrastructure, and how 124 Opportunities Ahead does it get built? 125 Developing effective support strategies 46 How are digital infrastructure projects managed and supported? 127 Priming the landscape 136 The crossroads we face 53 Why do people keep contributing to these projects, when they’re not getting paid for it? 139 Appendix 140 Glossary 142 Acknowledgements ROADS AND BRIDGES: THE UNSEEN LABOR BEHIND OUR DIGITAL INFRASTRUCTURE Preface Our modern society—everything from hospitals to stock markets to newspapers to social media—runs on software. But take a closer look, and you’ll find that the tools we use to build software are buckling under demand.
    [Show full text]
  • Mac OS X Server Administrator's Guide
    034-9285.S4AdminPDF 6/27/02 2:07 PM Page 1 Mac OS X Server Administrator’s Guide K Apple Computer, Inc. © 2002 Apple Computer, Inc. All rights reserved. Under the copyright laws, this publication may not be copied, in whole or in part, without the written consent of Apple. The Apple logo is a trademark of Apple Computer, Inc., registered in the U.S. and other countries. Use of the “keyboard” Apple logo (Option-Shift-K) for commercial purposes without the prior written consent of Apple may constitute trademark infringement and unfair competition in violation of federal and state laws. Apple, the Apple logo, AppleScript, AppleShare, AppleTalk, ColorSync, FireWire, Keychain, Mac, Macintosh, Power Macintosh, QuickTime, Sherlock, and WebObjects are trademarks of Apple Computer, Inc., registered in the U.S. and other countries. AirPort, Extensions Manager, Finder, iMac, and Power Mac are trademarks of Apple Computer, Inc. Adobe and PostScript are trademarks of Adobe Systems Incorporated. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Netscape Navigator is a trademark of Netscape Communications Corporation. RealAudio is a trademark of Progressive Networks, Inc. © 1995–2001 The Apache Group. All rights reserved. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company, Ltd. 062-9285/7-26-02 LL9285.Book Page 3 Tuesday, June 25, 2002 3:59 PM Contents Preface How to Use This Guide 39 What’s Included
    [Show full text]
  • Open Source Documentation Used in WAP4410N, Version 2.0.5.X
    Open Source Used In WAP4410N 2.0.5.x This document contains the licenses and notices for open source software used in this product. With respect to the free/open source software listed in this document, if you have any questions or wish to receive a copy of the source code to which you are entitled under the applicable free/open source license(s) (such as the GNU Lesser/General Public License) , please contact us at http://www.cisco.com/go/smallbiz_opensource_request. In your requests please include the following reference number 78EE117C99-24342489 En ce qui a trait au logiciel gratuit ou à exploitation libre figurant dans ce document, si vous avez des questions ou souhaitez recevoir une copie du code source, auquel vous avez droit en vertu des licences gratuites ou d'exploitation libre applicables (telles que licences GNU Lesser/General Public), veuillez communiquer avec nous à l'adresse http://www.cisco.com/go/smallbiz_opensource_request. Dans vos demandes, veuillez inclure le numéro de référence 78EE117C99-24342489 Contents 1.1 ag7100 1.0 1.1.1 Available under license 1.2 binutils 2.16.1 1.2.1 Available under license 1.3 busybox 1.1.0 1.3.1 Available under license 1.4 ccache 2.4 78-20798-01 Open Source Used In WAP4410N 2.0.5.x 1 1.4.1 Available under license 1.5 dhcp 0.1 1.5.1 Available under license 1.6 gcc 3.4.4 1.6.1 Available under license 1.7 genext2fs 1.3 1.7.1 Available under license 1.8 hostapd 0.5.9 1.8.1 Available under license 1.9 libiconv 1.8 1.9.1 Available under license 1.10 libupnp 1.2.1 1.10.1 Available under license
    [Show full text]
  • Post-Quantum Authentication in Openssl with Hash-Based Signatures
    Recalling Hash-Based Signatures Motivations for Cryptographic Library Integration Cryptographic Libraries OpenSSL & open-quantum-safe XMSS Certificate Signing in OpenSSL / open-quantum-safe Conclusions Post-Quantum Authentication in OpenSSL with Hash-Based Signatures Denis Butin, Julian Wälde, and Johannes Buchmann TU Darmstadt, Germany 1 / 26 I Quantum computers are not available yet, but deployment of new crypto takes time, so transition must start now I Well established post-quantum signature schemes: hash-based cryptography (XMSS and variants) I Our goal: make post-quantum signatures available in a popular security software library: OpenSSL Recalling Hash-Based Signatures Motivations for Cryptographic Library Integration Cryptographic Libraries OpenSSL & open-quantum-safe XMSS Certificate Signing in OpenSSL / open-quantum-safe Conclusions Overall Motivation I Networking requires authentication; authentication is realized by cryptographic signature schemes I Shor’s algorithm (1994): most public-key cryptography (RSA, DSA, ECDSA) breaks once large quantum computers exist I Post-quantum cryptography: public-key algorithms thought to be secure against quantum computer attacks 2 / 26 Recalling Hash-Based Signatures Motivations for Cryptographic Library Integration Cryptographic Libraries OpenSSL & open-quantum-safe XMSS Certificate Signing in OpenSSL / open-quantum-safe Conclusions Overall Motivation I Networking requires authentication; authentication is realized by cryptographic signature schemes I Shor’s algorithm (1994): most public-key
    [Show full text]
  • Using Unsniff Network Analyzer to Analyze SSL / TLS
    Whitepaper – SSL / TLS Analysis using Unsniff Network Analyzer Whitepaper : Using Unsniff Network Analyzer to analyze SSL / TLS A number of applications today use SSL and TLS as a security layer. Unsniff allows authorized users to analyze these applications by decrypting the SSL/TLS streams in real time. This is done without interrupting the SSL streams in any way. Unsniff can also strip out the SSL/TLS layer completely and analyze the application protocols as if the security layer never existed. For example: If you are working with a secure web server, you can analyze the HTTPS protocol, including the ability to reconstruct complete web pages. References : RFC2246 (TLS 1.0), RFC2459 (X.509v3), PKCS Standards (RSA Website) Feature overview Working with PDUs and Streams Decrypting SSL/TLS Analyzing upper layer protocols Howto : Analyzing a secure Microsoft IIS web server Howto : Analyzing a secure Apache web server Howto : Analyzing protocols tunneled via stunnel FAQ 1/12 © Unleash Networks, All rights reserved Whitepaper – SSL / TLS Analysis using Unsniff Network Analyzer Feature Overview Unsniff shows SSL/TLS records as separate entities in the PDU sheet irrespective of SSL records how they were carried at the link layer. Stream Monitor entire SSL / TLS sessions in real time via the Streams sheet. analysis Provided you have the servers private key material you can decrypt SSL / TLS Decryption sessions in real time. Most of the popular ciphers are supported. Advanced Unsniff supports SSL / TLS features such as session reuse and cipher renegotiation. Decryption SSL/TLS only acts as a transport layer for higher layer protocols. Ultimately we are interested in the analysis of higher layer protocols such as HTTP, LDAP etc.
    [Show full text]
  • CS670: Network Security
    Cristina Nita-Rotaru CS670: Network security IPsec. TLS. Sources 1. Many slides courtesy of Christo Wilson and Wil Robertson 2. IPSec Key management based on slides from B. LaMacchia 3. Analysis of the HTTPS Certificate Ecosystem, IMC 2013: https://jhalderm.com/pub/papers/https-imc13.pdf 4. Analysis of SSL certificate reissues and revocations in the wake of Heartbleed, IMC 2014: http://www.ccs.neu.edu/home/cbw/pdf/imc254-zhang.pdf 2 IPSec; TLS 1: Protecting IP: IPsec OSI/ISO Model Application Application Presentation Presentation Session Session Transport Transport Network Network Data Link Data Link Physical Layer Physical Layer 4 IPSec; TLS IPsec design goals } Design philosophy: applications cannot be trusted to implement end-to-end security properly and security should be built into the network itself } Transparent to applications (below transport layer ) } Goal: Facilitate direct IP connectivity between sensitive hosts through untrusted networks } It is designed to be extremely flexible } Different crypto algorithms and key exchange supported } Different security services compositions } Different granularities of protection 5 IPSec; TLS Security goals } IPsec provides: } access control } integrity } data origin authentication } rejection of replayed packets } confidentiality } IETF IPSEC Working Group } Documented in RFCs and Internet drafts 6 IPSec; TLS Security and deployment mechanisms } Operates based on security associations } Deployment: } Transport-mode: encapsulates an upper-layer protocol (e.g. TCP or UDP) and preapends an
    [Show full text]
  • Master's Thesis
    Securing In-Boat CAN Communication over the Internet Using a Cell Phone as Wi-Fi Router with Limited Hardware Master's Thesis in Computer Science and Engineering RICKARD PERSSON ALESANDRO SANCHEZ Chalmers University of Technology Department of Computer Science and Engineering Gothenburg, Sweden 2015 The Author grants to Chalmers University of Technology and University of Gothen- burg the non-exclusive right to publish the Work electronically and in a non-commercial purpose make it accessible on the Internet. The Author warrants that he/she is the author to the Work, and warrants that the Work does not contain text, pictures or other material that violates copyright law. The Author shall, when transferring the rights of the Work to a third party (for example a publisher or a company), acknowledge the third party about this agreement. If the Author has signed a copyright agreement with a third party regarding the Work, the Author warrants hereby that he/she has obtained any necessary permission from this third party to let Chalmers University of Technology and University of Gothenburg store the Work electronically and make it accessible on the Internet. Securing In-Boat CAN Communication over the Internet Securing In-Boat CAN Communication over the Internet Using a Cell Phone as Wi-FI Router with Limited Hardware Rickard, Persson Alesandro, Sanchez ©Rickard Persson, June 2015 ©Alesandro Sanchez, June 2015 Examiner: Tomas Olovsson Chalmers University of Technology Department of Computer Science and Engineering SE-412 96 G¨oteborg Sweden Telephone + 46 (0)31-772 1000 Department of Computer Science and Engineering Gothenburg, Sweden June 2014 Abstract Opening a communication channel to the internal vehicle bus of pleasure boats through the Internet, offers benefits such as remote diagnostics and software update of boat components.
    [Show full text]
  • Scalar I3 and I6 Open Source Software Licenses
    Tape Automation Scalar i3 & Scalar i6, Firmware Release 1.1 (110G) Open Source Software Licenses Open Source Software (OSS) Licenses for: • Scalar i3 & Scalar i6 Firmware Release 1.1 (110G). The firmware/software contained in the Scalar i3 & Scalar i6 is an aggregate of vendor proprie- tary programs as well as third party programs, including Open Source Software (OSS). Use of OSS is subject to designated license terms and the following OSS license disclosure lists all open source components and applicable licenses that are part of the tape library firmware. All software that is designated as OSS may be copied, distributed, and/or modified in accordance with the terms and conditions of its respective license(s). Additionally, for some OSS you are entitled to obtain the corresponding OSS source files as required by the respective and applicable license terms. While GNU General Public License ("GPL") and GNU Lesser General Public Li- cense ("LGPL") licensed OSS requires that the sources be made available, Quantum makes all tape library firmware integrated OSS source files, whether licensed as GPL, LGPL or otherwise, available upon request. Please refer to the Scalar i3 & Scalar i6 Open Source License CD (part number 3-07787-01) when making such request. For contact information, see Getting More In- formation. LTO tape drives installed in the library may also include OSS components. For a complete list- ing of respective OSS packages and applicable OSS license information included in LTO tape drives, as well as instructions to obtain source files pursuant to applicable license requirements, please reference the Tape Automation disclosure listings under the Open Source Information link at www.quantum.com/support.
    [Show full text]
  • Third-Party License Acknowledgments
    Symantec Privileged Access Manager Third-Party License Acknowledgments Version 3.3.5 Symantec Privileged Access Manager Third-Party License Acknowledgments Broadcom, the pulse logo, Connecting everything, and Symantec are among the trademarks of Broadcom. Copyright © 2019 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries. For more information, please visit www.broadcom.com. Broadcom reserves the right to make changes without further notice to any products or data herein to improve reliability, function, or design. Information furnished by Broadcom is believed to be accurate and reliable. However, Broadcom does not assume any liability arising out of the application or use of this information, nor the application or use of any product or circuit described herein, neither does it convey any license under its patent rights nor the rights of others. 2 Symantec Privileged Access Manager Third-Party License Acknowledgments Contents Activation 1.1.1 ..................................................................................................................................... 7 Adal4j 1.1.2 ............................................................................................................................................ 7 AdoptOpenJDK 1.8.0_272-b10 ............................................................................................................ 7 Aespipe 2.4e aespipe ........................................................................................................................
    [Show full text]
  • Purecloud Edge Setup
    PureCloud Edge Setup Administrator's Guide Last Updated: July 21, 2016 This document provides introductory information and procedures for initial installation and configuration of a PureCloud Edge appliance. ©2016 Interactive Intelligence. All rights reserved. | inin.com Copyright and trademark information The following names are registered trademarks, trademarks, or service marks belonging to Interactive Intelligence, Inc. Registered Trademarks Service marks trademarks Interactive Intelligence® Spotability™ Interactive Intelligence PureCloud℠ Deliberately Innovative® Interactive Intelligence Bridge Server™ PureCloud℠ Interactive Intelligence logo Interactive Intelligence PureMatch℠ Deliberate Innovation™ PureCloud Logo℠ PureCloud Edge™ PureCloud Collaborate℠ Interactive Intelligence PureCloud Interactive Intelligence PureCloud Edge™ Collaborate℠ PureCloud Communicate℠ Interactive Intelligence PureCloud Communicate℠ All third-party trademarks or registered trademarks are the property of their respective owners. Interactive Intelligence PureCloud℠ Copyright ©2014-2016 Interactive Intelligence, Inc. All rights reserved. Spotability™ Copyright © 2011-2016 Interactive Intelligence, Inc. All rights reserved. DISCLAIMER INTERACTIVE INTELLIGENCE (INTERACTIVE) HAS NO RESPONSIBILITY UNDER WARRANTY, INDEMNIFICATION OR OTHERWISE, FOR MODIFICATION OR CUSTOMIZATION OF ANY INTERACTIVE SOFTWARE BY INTERACTIVE, CUSTOMER OR ANY THIRD PARTY EVEN IF SUCH CUSTOMIZATION AND/OR MODIFICATION IS DONE USING INTERACTIVE TOOLS, TRAINING OR METHODS DOCUMENTED BY
    [Show full text]
  • Emulex Lpe31000-Series and Lpe32000-Series HBA Firmware and Boot Code Release Notes Releases 12.8.340.8 and 12.8.340.19 Resolved Issues
    Release Notes Emulex® LPe31000-Series and LPe32000-Series HBA Firmware and Boot Code Releases 12.8.340.8 and 12.8.340.19 Purpose and Contact Information These release notes describe the new features, resolved issues, known issues, new firmware features or resolved issues that require a host reboot, technical tips, and license notices associated with this firmware and boot code release for Emulex® LPe31000-series and LPe32000-series HBAs. For the latest product documentation, go to www.broadcom.com. If you have questions or require additional information, contact an authorized Broadcom® Technical Support representative at [email protected]. New Features Release 12.8.340.19 Support was added for new flash devices. NOTE: If you downgrade the firmware to a version earlier than 12.8.340.19 on an HBA that has a new flash device, the firmware is not installed and an error message is displayed. Release 12.8.340.8 The EFIBoot driver now supports NVMe over FC direct-connect point-to-point topology. NOTE: In some cases, a firmware update requires either a firmware reset or a basic PCIe reset, depending on the features available in the new firmware. A firmware reset is performed automatically if it is needed, regardless of the operating system. In some cases, a full reboot is required to activate new firmware, to enable a new feature, or to take advantage of a resolved issue. In such a case, the application that updated the firmware produces a message indicating what is needed. See the New Firmware Features or Resolved Issues That Require a Host Reboot section for a list of new features or resolved issues that require a host reboot after a firmware update.
    [Show full text]