DOCSLIB.ORG

Kboot—A Boot Loader Based on Kexec

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Kboot—A Boot Loader Based on Kexec kboot—A Boot Loader Based on Kexec Werner Almesberger [email protected] Abstract tools for hardware diagnosis and system soft- ware repair. On Linux, many boot loaders are much more limited than this. Compared to the “consoles” found on tradi- tional Unix workstations and mini-computers, Even boot loaders that provide several of these the Linux boot process is feature-poor, and the advanced features, like GRUB, suffer from the addition of new functionality to boot loaders of- problem that they need to replicate functional- ten results in massive code duplication. With ity or at least include code found elsewhere, the availability of kexec, this situation can be which creates an ever increasing maintenance improved. burden. Similarly, any drivers or protocols the boot loader incorporates, will have to be main- kboot is a proof-of-concept implementation of tained in the context of that boot loader, in par- a Linux boot loader based on kexec. kboot uses allel with the original source. a boot loader like LILO or GRUB to load a reg- ular Linux kernel as its first stage. Then, the full New boot loader functionality is not only re- capabilities of the kernel can be used to locate quired because administrators demand more and to access the kernel to be booted, perform powerful tools, but also because technologi- limited diagnostics and repair, etc. cal progress leads to more and more complex mechanisms for accessing storage and other de- vices, which a boot loader eventually should be able to support. 1 Oh no, not another boot loader ! It is easy to see that a regular Linux system hap- pens to support a superset of all the functional- There is already no shortage of boot loaders for ity described above. Linux, so why have another one ? The moti- vation for making kboot is simply that the boot With the addition of the kexec system call to process of Linux is still not as good as it could the 2.6.13 mainline Linux kernel, we now have be, and that recent technological advances have an instrument that allows us to build boot load- made it comparably easy to do better. ers with a fully featured Linux system, tailored according to the needs of the boot process and Looking at traditional Unix servers and work- the resources available for it. stations, one often finds very powerful boot en- vironments, offering a broad choice of possible Kboot is a proof-of-concept implementation of sources for the kernel and other system files to such a boot loader. It demonstrates that new load. It is also quite common to find various functionality can be merged from the vast code 28 • kboot—A Boot Loader Based on Kexec base available for Linux with great ease, and to the operating system it is booting, and trans- without incurring any significant maintenance fers control to the entry point of the code it has overhead. This way, it can also serve as a plat- loaded. form for the development of new boot concepts. The project’s home page is at http:// In the case of Linux, two items deserve special kboot.sourceforge.net/ mention: the boot parameter line and the initial RAM disk. The remainder of this section gives a high-level view of the role of a boot loader in general, The boot parameter line was at its inception in- and what kboot aims to accomplish. Additional tended primarily as a means for passing a “boot technical details about the boot process, includ- into single user mode” flag to the kernel, but ing tasks performed by the Linux kernel when this got a little out of hand, and it is nowadays bringing up user space, can be found in [1]. often used to pass dozens if not hundreds of bytes of essential configuration data to the ker- Section 2 briefly describes Eric Biederman’s nel, such as the location of the root file system, kexec [2], which plays a key role in the op- instructions for how certain drivers should ini- eration of kboot. Section 3 introduces kboot tialize themselves (e.g., whether it is safe for proper, explains its structure, and discusses its the IDE driver to try to use DMA or not), and application. Section 4 gives an outlook on fu- the selection and tuning of items included in a ture work, and we conclude with section 5. generic kernel (e.g., disabling ACPI support). 1.1 What a boot loader does Since a kernel would often not even boot with- out the correct set of boot parameters, a boot After being loaded by the system’s firmware, a loader must store them in its configuration, and boot loader spends a few moments making it- pass them to the kernel without requiring user self comfortable on the system. This includes action. At the same time, users should of course loading additional parts, moving itself to other be able to manually set and override such pa- memory regions, and establishing access to de- rameters. vices. The initial RAM disk (initrd), which at the time After that, it typically tries to interact with of writing is gradually being replaced by the the user. This interaction can range from initial RAM file system (initramfs), provides an checking whether the user is trying to get the early user space, which is put into memory by boot loader’s attention by pressing some key, the boot loader, and is thus available even be- through a command line or a simple full-screen fore the kernel is fully capable to interact with menu, to a lavish graphical user interface. its surroundings. This early user space is used Whatever the interface may be, in the end its for extended setup operations, such as the load- main purpose is to allow the user to select, per- ing of driver modules. haps along with some other options, which op- erating system or kernel will be booted. Once Given that the use of initrd is an integral part of this choice is made, the boot loader proceeds to many Linux distributions, any general-purpose load the corresponding data into memory, does Linux boot loader must support this functional- some additional setup, e.g., to pass parameters ity. 2006 Linux Symposium, Volume One • 29 Hard− and firmware New device drivers New protocols Boot process Administration User experience New file systems Convenience Combination of services Compatible "look and feel" Figure 1: The boot process exists in a world full of changes and faces requirements from many directions. All this leads to the need to continuously grow in functionality. 1.2 What a boot loader should be like formats, and gets particularly interesting when using networks. For example, there is noth- ing inherently wrong in wanting to boot kernels A boot loader has much in common with the that happen to be stored in RPM files on an NFS operating system it is loading: it shares the server, which is reached through an IPsec link. same hardware, exists in the same administra- tive context, and is seen by the same users. The hardware and protocol environment of the From all these directions originate require- boot process extends beyond storage. For ex- ments on the boot process, as illustrated in fig- ample, keyboard or display devices for users ure 1. with disabilities may require special drivers. With kboot, such devices can also be used to The boot loader has to be able to access at least interact with the boot loader. the hardware that leads to the locations from which data has to be loaded. This does not Last but not least, whenever users have to per- only include physical resources, but also any form non-trivial tasks with the boot loader, they protocols that are used to communicate with will prefer a context similar to what they are devices. Firmware sometimes provides a set used to from normal interaction with the sys- of functions to perform such accesses, but new tem. For instance, path names starting at the hardware or protocol extensions often require root of a file system hierarchy tend to be easier support that goes beyond this. For example, al- to remember than device-local names prefixed though many PCs have a Firewire port, BIOS with a disk and partition number. support for booting from storage attached via Firewire is not common. In addition to all this, it is often desirable if small repair work on an unbootable system can Above basic access mechanisms lies the do- be done from the boot loader, without having main of services the administrator can combine to find or prepare a system recovery medium, more or less freely. This begins with file system or similar. 30 • kboot—A Boot Loader Based on Kexec Kernel memory Kernel memory (before rebooting) (while and after rebooting) Copy file(s) through user space into kernel memory Order pages 1 2 3 Run kexec reboot Kernel Kernel code code 4 code kboot −f file Jump to kernel setup Figure 2: Simplified boot sequence of kexec. The bottom line is that a general-purpose boot it to absorb additional functionality more loader will always grow in functionality along quickly. For instance, GRUB can directly read the lines of what the full operating system can a large number of different file system formats, support. without having to rely on external help, such as the map file used by LILO. GRUB also offers limited networking support. 1.3 The story so far Unfortunately, GRUB still requires that any The two principal boot loaders for Linux on the new functionality, be it drivers, file systems, file i386 platform, LILO and GRUB, illustrate this formats, network protocols, or anything else, is trend nicely.
Load more

Recommended publications
  • Oracle® Linux Administrator's Solutions Guide for Release 6
    Oracle® Linux Administrator's Solutions Guide for Release 6 E37355-64 August 2017 Oracle Legal Notices Copyright © 2012, 2017, Oracle and/or its affiliates. All rights reserved. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S.
    [Show full text]
  • Kdump, a Kexec-Based Kernel Crash Dumping Mechanism
    Kdump, A Kexec-based Kernel Crash Dumping Mechanism Vivek Goyal Eric W. Biederman Hariprasad Nellitheertha IBM Linux NetworkX IBM [email protected] [email protected] [email protected] Abstract important consideration for the success of a so- lution has been the reliability and ease of use. Kdump is a crash dumping solution that pro- Kdump is a kexec based kernel crash dump- vides a very reliable dump generation and cap- ing mechanism, which is being perceived as turing mechanism [01]. It is simple, easy to a reliable crash dumping solution for Linux R . configure and provides a great deal of flexibility This paper begins with brief description of what in terms of dump device selection, dump saving kexec is and what it can do in general case, and mechanism, and plugging-in filtering mecha- then details how kexec has been modified to nism. boot a new kernel even in a system crash event. The idea of kdump has been around for Kexec enables booting into a new kernel while quite some time now, and initial patches for preserving the memory contents in a crash sce- kdump implementation were posted to the nario, and kdump uses this feature to capture Linux kernel mailing list last year [03]. Since the kernel crash dump. Physical memory lay- then, kdump has undergone significant design out and processor state are encoded in ELF core changes to ensure improved reliability, en- format, and these headers are stored in a re- hanced ease of use and cleaner interfaces. This served section of memory. Upon a crash, new paper starts with an overview of the kdump de- kernel boots up from reserved memory and pro- sign and development history.
    [Show full text]
  • Coreboot - the Free Firmware
    coreboot - the free firmware vimacs <https://vimacs.lcpu.club> Linux Club of Peking University May 19th, 2018 . vimacs (LCPU) coreboot - the free firmware May 19th, 2018 1 / 77 License This work is licensed under the Creative Commons Attribution 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by/4.0/. You can find the source code of this presentation at: https://git.wehack.space/coreboot-talk/ . vimacs (LCPU) coreboot - the free firmware May 19th, 2018 2 / 77 Index 1 What is coreboot? History Why use coreboot 2 How coreboot works 3 Building and using coreboot Building Flashing 4 Utilities and Debugging 5 Join the community . vimacs (LCPU) coreboot - the free firmware May 19th, 2018 3 / 77 Index 6 Porting coreboot with autoport ASRock B75 Pro3-M Sandy/Ivy Bridge HP Elitebooks Dell Latitude E6230 7 References . vimacs (LCPU) coreboot - the free firmware May 19th, 2018 4 / 77 1 What is coreboot? History Why use coreboot 2 How coreboot works 3 Building and using coreboot Building Flashing 4 Utilities and Debugging 5 Join the community . vimacs (LCPU) coreboot - the free firmware May 19th, 2018 5 / 77 What is coreboot? coreboot is an extended firmware platform that delivers a lightning fast and secure boot experience on modern computers and embedded systems. As an Open Source project it provides auditability and maximum control over technology. The word ’coreboot’ should always be written in lowercase, even at the start of a sentence. vimacs (LCPU) coreboot - the free firmware May 19th, 2018 6 / 77 History: from LinuxBIOS to coreboot coreboot has a very long history, stretching back more than 18 years to when it was known as LinuxBIOS.
    [Show full text]
  • Arxiv:1907.06110V1 [Cs.DC] 13 Jul 2019 (TCB) with Millions of Lines of Code and a Massive Attack Enclave” of Physical Machines
    Supporting Security Sensitive Tenants in a Bare-Metal Cloud∗† Amin Mosayyebzadeh1, Apoorve Mohan4, Sahil Tikale1, Mania Abdi4, Nabil Schear2, Charles Munson2, Trammell Hudson3 Larry Rudolph3, Gene Cooperman4, Peter Desnoyers4, Orran Krieger1 1Boston University 2MIT Lincoln Laboratory 3Two Sigma 4Northeastern University Abstract operations and implementations; the tenant needs to fully trust the non-maliciousness and competence of the provider. Bolted is a new architecture for bare-metal clouds that en- ables tenants to control tradeoffs between security, price, and While bare-metal clouds [27,46,48,64,66] eliminate the performance. Security-sensitive tenants can minimize their security concerns implicit in virtualization, they do not ad- trust in the public cloud provider and achieve similar levels of dress the rest of the challenges described above. For example, security and control that they can obtain in their own private OpenStack’s bare-metal service still has all of OpenStack in data centers. At the same time, Bolted neither imposes over- the TCB. As another example, existing bare-metal clouds en- head on tenants that are security insensitive nor compromises sure that previous tenants have not compromised firmware by the flexibility or operational efficiency of the provider. Our adopting a one-size-fits-all approach of validation/attestation prototype exploits a novel provisioning system and special- or re-flashing firmware. The tenant has no way to program- ized firmware to enable elasticity similar to virtualized clouds. matically verify the firmware installed and needs to fully trust Experimentally we quantify the cost of different levels of se- the provider. As yet another example, existing bare-metal curity for a variety of workloads and demonstrate the value clouds require the tenant to trust the provider to scrub any of giving control to the tenant.
    [Show full text]
  • SUSE Linux Enterprise Server 15 SP2 Autoyast Guide Autoyast Guide SUSE Linux Enterprise Server 15 SP2
    SUSE Linux Enterprise Server 15 SP2 AutoYaST Guide AutoYaST Guide SUSE Linux Enterprise Server 15 SP2 AutoYaST is a system for unattended mass deployment of SUSE Linux Enterprise Server systems. AutoYaST installations are performed using an AutoYaST control le (also called a “prole”) with your customized installation and conguration data. Publication Date: September 24, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE trademarks, see https://www.suse.com/company/legal/ . All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its aliates. Asterisks (*) denote third-party trademarks. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents 1 Introduction to AutoYaST 1 1.1 Motivation 1 1.2 Overview and Concept 1 I UNDERSTANDING AND CREATING THE AUTOYAST CONTROL FILE 4 2 The AutoYaST Control
    [Show full text]
  • Beyond Init: Systemd Linux Plumbers Conference 2010
    Beyond Init: systemd Linux Plumbers Conference 2010 Kay Sievers Lennart Poettering November 2010 Kay Sievers, Lennart Poettering Beyond Init: systemd Triggers: Boot, Socket, Bus, Device, Path, Timers, More Kay Sievers, Lennart Poettering Beyond Init: systemd Kay Sievers, Lennart Poettering Beyond Init: systemd Substantial coverage of basic OS boot-up tasks, including fsck, mount, quota, hwclock, readahead, tmpfiles, random-seed, console, static module loading, early syslog, plymouth, shutdown, kexec, SELinux, initrd+initrd-less boots. Status: almost made Fedora 14. Kay Sievers, Lennart Poettering Beyond Init: systemd including fsck, mount, quota, hwclock, readahead, tmpfiles, random-seed, console, static module loading, early syslog, plymouth, shutdown, kexec, SELinux, initrd+initrd-less boots. Status: almost made Fedora 14. Substantial coverage of basic OS boot-up tasks, Kay Sievers, Lennart Poettering Beyond Init: systemd mount, quota, hwclock, readahead, tmpfiles, random-seed, console, static module loading, early syslog, plymouth, shutdown, kexec, SELinux, initrd+initrd-less boots. Status: almost made Fedora 14. Substantial coverage of basic OS boot-up tasks, including fsck, Kay Sievers, Lennart Poettering Beyond Init: systemd quota, hwclock, readahead, tmpfiles, random-seed, console, static module loading, early syslog, plymouth, shutdown, kexec, SELinux, initrd+initrd-less boots. Status: almost made Fedora 14. Substantial coverage of basic OS boot-up tasks, including fsck, mount, Kay Sievers, Lennart Poettering Beyond Init: systemd hwclock, readahead, tmpfiles, random-seed, console, static module loading, early syslog, plymouth, shutdown, kexec, SELinux, initrd+initrd-less boots. Status: almost made Fedora 14. Substantial coverage of basic OS boot-up tasks, including fsck, mount, quota, Kay Sievers, Lennart Poettering Beyond Init: systemd readahead, tmpfiles, random-seed, console, static module loading, early syslog, plymouth, shutdown, kexec, SELinux, initrd+initrd-less boots.
    [Show full text]
  • Unbreakable Enterprise Kernel Release Notes for Unbreakable Enterprise Kernel Release 3
    Unbreakable Enterprise Kernel Release Notes for Unbreakable Enterprise Kernel Release 3 E48380-10 June 2020 Oracle Legal Notices Copyright © 2013, 2020, Oracle and/or its affiliates. This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or "commercial computer software documentation" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract.
    [Show full text]
  • Generating a White List for Hardware Which Works with Kexec/Kdump
    Generating a White List for Hardware which Works with Kexec/Kdump Fernando Luis Vázquez Cao NTT Open Source Software Center [email protected] Abstract nally, the capture of the crash dump. Kdump is very good at the first two but there are still some The mainstream Linux kernel lacked a crash issues when the dump capture kernel takes control dumping mechanism from its inception until the of the system. In particular the new kernel may fail recent adoption of kdump. This, despite the fact to initialise the underlying devices which, in turn, that there were several solutions available out-of- is likely to lead to a kernel panic or an oops. tree and some of them were even included in major distributions. However concerns about their intru- siveness and reliability prevented them from mak- The underlying problem is that the state of the ing it into the mainstream kernel (aka vanilla ker- devices during a kdump boot is not predictable nel), the main argument being that relying on the because no device shutdown is performed in the resources of a crashing kernel to capture a dump, crashed kernel (it cannot be trusted), and the as they did, is inherently dangerous. firmware stage of the standard boot process is skipped (the dump capture kernel is a soft-booted The appearance of Eric Biederman’s kexec kernel after all). In other words, the inherent as- patches and its subsequent inclusion in the kernel sumption that the firmware (known as the BIOS on as a new system call paved the way for the imple- some systems) is always there to do the dirty work mentation of an idea that had been floating around is not valid anymore.
    [Show full text]
  • SUSE Linux Enterprise Server 12 SP4 System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 12 SP4
    SUSE Linux Enterprise Server 12 SP4 System Analysis and Tuning Guide System Analysis and Tuning Guide SUSE Linux Enterprise Server 12 SP4 An administrator's guide for problem detection, resolution and optimization. Find how to inspect and optimize your system by means of monitoring tools and how to eciently manage resources. Also contains an overview of common problems and solutions and of additional help and documentation resources. Publication Date: September 24, 2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled “GNU Free Documentation License”. For SUSE trademarks, see https://www.suse.com/company/legal/ . All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its aliates. Asterisks (*) denote third-party trademarks. All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its aliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof. Contents About This Guide xii 1 Available Documentation xiii
    [Show full text]
  • Reinitialization of Devices After a Soft-Reboot
    RReeiinniittiiaalliizzaattiioonn ooff ddeevviicceess aafftteerr aa ssoofftt--rreebboooott 2007/2/12 NTT Open Source Software Center Fernando Luis Vázquez Cao Copyright(C)2007 NTT Open Source Software Center 1 Agenda 1. Kexec/kdump reboot 2. Device reinitialization 3. Tackling device reinitialization 4. Device configuration restore Copyright(C)2007 NTT Open Source Software Center 2 11 kkeexxeecc//kkdduummpp rreebboooott Copyright(C)2007 NTT Open Source Software Center 3 1.1. Standard boot process power on hardware stage firmware stage boot loader t o o kernel stage b e r working shutdown -r device shutdown machine shutdown HW reset Copyright(C)2007 NTT Open Source Software Center 4 1.2. Kexec boot process power on hardware stage firmware stage l e boot loader n r l e e k n t r s r kernel stage kernel stage e i f k d n o working working c e s kexec device shutdown machine shutdown HW reset Copyright(C)2007 NTT Open Source Software Center 5 1.3. Kdump boot process power on hardware stage firmware stage l e boot loader n r l e e k n t r s r e i kernel stage kernel stage f k d n o working working c e crash s minimal machine shutdown HW reset Copyright(C)2007 NTT Open Source Software Center 6 22 ddeevviiccee rreeiinniittiiaalliizzaattiioonn Copyright(C)2007 NTT Open Source Software Center 7 2.1. Device reinitialization issue State of devices after a kdump boot is unknown ➢ The first kernel and what it knows is unreliable ✗ No device shutdown in the crashing kernel ➢ Firmware stage of the boot process is skipped ✗ Devices are not reset Consequences ➢ Devices may be operational or in an unstable state Kexec is also vulnerable when the first kernel's shutdown functions do not do their job properly Copyright(C)2007 NTT Open Source Software Center 8 2.2.
    [Show full text]
  • Advanced Applications of DRTM with Trenchboot Securelaunch for Linux
    Advanced Applications of DRTM with TrenchBoot SecureLaunch for Linux Daniel P. Smith Apertus Solutions, LLC TrenchBoot Project CC-BY-4.0: https://creativecommons.org/licenses/by/4.0/ ● Introduction ● Early Launch Use Cases Agenda ● Late Launch Use Cases ● Futures ● Q&A TrenchBoot Contributors SecureLaunch Status Timeline: ● The kern_info structure was merged in 5.5 ● RFC version of SecureLaunch patch set submitted to LKML - March 2020 ● RFC version of GRUB patch set sent to GRUB mailing list - May 2020 ● SecureLaunch patch set submission to LKML - Sept 2020 See Project Info at the end for past presentations and ways to engage TrenchBoot community Introduction Common Understanding: ● Launch Integrity is the responsibility a user or enterprise entrusts the system with to ensure the expected run time is launched ● Launch Integrity is often implemented as a Load Integrity solution ● The Launch Integrity trust chain are the TCB components conducting the transitive trust operations ● A Launch Integrity trust chain is susceptible to manipulation by all TCB components it loads or inherits ● Dynamic Launch enables early launch and late launch operational models Early Launch SRTM Supplement Purpose: To reset the Root of Trust for the launch integrity trust chain used to start the run time. Reasons: ● Remove/replace the trust chain started by system firmware ● For UEFI, switch to a trust chain that is anchored with an RTM ● When system firmware RTV is not rooted in hardware, e.g. no BootGuard/Titan/DICE Challenges: ● Increases the boot time ● RTM requires a separate assessment action SecureLaunch Implementation In SecureLaunch this is referred to as the First Launch use case and is the primary focus for initial implementation and release.
    [Show full text]
  • What's New in Linux on IBM Z
    Linux on IBM Z News — Stefan Raspl Linux on IBM Z Development IBM Z / © 2019 IBM Corporation Trademarks The following are trademarks of the International Business Machines Corporation in the United States and/or other countries. AIX* DB2* HiperSockets* MQSeries* PowerHA* RMF System z* zEnterprise* z/VM* BladeCenter* DFSMS HyperSwap NetView* PR/SM Smarter Planet* System z10* z10 z/VSE* CICS* EASY Tier IMS OMEGAMON* PureSystems Storwize* Tivoli* z10 EC Cognos* FICON* InfiniBand* Parallel Sysplex* Rational* System Storage* WebSphere* z/OS* DataPower* GDPS* Lotus* POWER7* RACF* System x* XIV* * Registered trademarks of IBM Corporation The following are trademarks or registered trademarks of other companies. Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries. Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other countries, or both and is used under license therefrom. Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications Agency which is now part of the Office of Government Commerce. ITIL is a registered trademark, and a registered community trademark of the Office of Government Commerce, and is registered in the U.S. Patent and Trademark Office. Java and all Java based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates.
    [Show full text]