Practical Linux Forensics by Bruce Nikkel! As a Prepublication Title, This Book May Be Incom- Plete and Some Chapters May Not Have Been Proofread

Total Page:16

File Type:pdf, Size:1020Kb

Practical Linux Forensics by Bruce Nikkel! As a Prepublication Title, This Book May Be Incom- Plete and Some Chapters May Not Have Been Proofread P R A C T I C A L LINUX FORENSICS A GUIDE FOR DIGITAL INVESTIGATORS BRUCE NIKKEL EARLY ACCESS NO STARCH PRESS EARLY ACCESS PROGRAM: FEEDBACK WELCOME! Welcome to the Early Access edition of the as yet unpublished Practical Linux Forensics by Bruce Nikkel! As a prepublication title, this book may be incom- plete and some chapters may not have been proofread. Our goal is always to make the best books possible, and we look forward to hearing your thoughts. If you have any comments or questions, email us at [email protected]. If you have specific feedback for us, please include the page number, book title, and edition date in your note, and we’ll be sure to review it. We appreciate your help and support! We’ll email you as new chapters become available. In the meantime, enjoy! PR CA T IC A L L INU X FOR E N SI C S BRUCE N IK KE L Early Access edition, 6/18/21 Copyright © 2021 by Bruce Nikkel. ISBN-13: 978-1-7185-0196-6 (print) ISBN-13: 978-1-7185-0197-3 (ebook) Publisher: William Pollock Production Manager: Rachel Monaghan Production Editor: Miles Bond Developmental Editor: Jill Franklin Cover Illustrator: James L. Barry Technical Reviewer: Don Frick Copyeditor: George Hale No Starch Press and the No Starch Press logo are registered trademarks of No Starch Press, Inc. Other product and company names mentioned herein may be the trademarks of their respective owners. Rather than use a trademark symbol with every occurrence of a trade- marked name, we are using the names only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. All rights reserved. No part of this work may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or by any informa- tion storage or retrieval system, without the prior written permission of the copyright owner and the publisher. The information in this book is distributed on an “As Is” basis, without warranty. While every precaution has been taken in the preparation of this work, neither the author nor No Starch Press, Inc. shall have any liability to any person or entity with respect to any loss or damage caused or alleged to be caused directly or indirectly by the information contained in it. CONTENTS Introduction Chapter 1: Digital Forensics Overview Chapter 2: Linux Overview Chapter 3: Extracting Evidence from Storage Devices and Filesystems Chapter 4: Directory Layout and Forensic Analysis of Linux Files Chapter 5: Investigating Evidence from Linux Logs Chapter 6: Reconstructing System Boot and Initialization Chapter 7: Examination of Installed Software Packages Chapter 8: Identifying Network Configuration Artifacts Chapter 9: Forensic Analysis of Time and Location Chapter 10: Reconstructing User Desktops and Login Activity Chapter 11: Forensic Traces of Attached Peripheral Devices Afterword Appendix A: File and Directory List for Digital Investigators The chapters in red are included in this Early Access PDF. Practical Linux Forensics (Early Access) © 2021 by Bruce Nikkel IN TRODUCTION Welcome to Practical Linux Forensics: A Guide for Digital Investigators. This book covers a variety of methods and techniques for find­ ing and analyzing digital evidence found on modern Linux systems. Among digital forensic inves­ tigators, the phrase Linux forensics may have one of two meanings. In one case, it refers to using Linux as a dig­ ital forensics platform to perform acquisition or anal­ ysis of any target system under investigation (which could be Windows, Mac, Linux, or any other operat­ ing system). In this book, however, Linux forensics refers to analyzing or examining a suspect Linux sys­ tem as the target of an investigation (independent of the platform or tools used). I will focus on identify­ ing common artifacts found on various Linux distri­ butions (distros) and how to analyze them in the con­ text of a forensic investigation. The forensic analysis Practical Linux Forensics (Early Access) © 2021 by Bruce Nikkel methods described in this book are independent of the tools used and will benefit users of FTK, X­Ways, EnCase, or any other forensic analysis tool suite. The tools I use in the examples and illustrations tend to be Linux­based, but the concepts remain fully tool inde­ pendent. Why I Wrote This Book In some ways, this book is a logical continuation of my first book, Practical Forensic Imaging. After performing a forensic acquisition of a system and securing a drive image, analysis is the next step performed in a typical digital forensic investigation. This book dives into the technical details of analyzing forensic images of Linux systems. There are many books on Windows and even Mac forensic analysis, but few books focus on the analysis of a Linux system as the target of an inves­ tigation. Even fewer focus specifically on postmortem (dead disk) analysis of modern Linux installations. I’ve been hearing digital forensic investiga­ tors in the community increasingly comment: “We are starting to get more Linux images in our lab, but we don’t know exactly what to look for...”. Such comments are coming both from forensic labs in the private sector (corpo­ rations) and the public sector (law enforcement). This book is intended to provide a resource that addresses this growing area of interest. It will help forensic investigators find and extract digital evidence found on Linux sys­ tems, reconstruct past activity, draw logical conclusions, and write compre­ hensive forensic evidence reports of their analysis. Another reason for writing this book is out of personal interest and motivation to better understand the internals of modern Linux systems. Over the past decade, significant advancements in Linux distributions have changed how Linux forensic analysis is performed. I teach classes in both digital forensics and Linux at the Bern University of Applied Sciences in Switzerland, and writing this book has helped me stay current on those top­ ics. Finally, I wrote this book because doing technical research and writing is fun and interesting. Writing is a learning process for me as an author, and I find myself constantly filling gaps in my knowledge that I didn’t realize ex­ isted. How This Book Is Unique This book was written as a guide for digital forensic investigators using any forensic analysis platform or tool. There is no requirement to use Linux as a platform or to use Linux­based tools. The book is intended to be a useful resource even for people using commercial digital forensic analysis tools on 2 Introduction Practical Linux Forensics (Early Access) © 2021 by Bruce Nikkel Windows or Mac, as long as those tools support the analysis of Linux arti­ facts. This book is Linux distribution agnostic. There is no favoritism toward any particular distro and the most popular Linux distributions are used across all the examples. The research, testing, and examples used in this book have been conducted primarily with four Linux distribution families and derivatives: Debian (including Ubuntu), Fedora (including Red Hat), SUSE, and Arch Linux. These four distributions are the basis for the vast majority of Linux systems in use today and are the core focus of this book. Whenever possible I try to describe concepts that are distro independent and consistent across most Linux distributions. However, many forensic artifacts are distribution specific and still need to be explained. Those are covered as well, but not as comprehensively. This book is also architecture independent. The concepts here should apply to Linux systems installed on any CPU architecture or hardware sys­ tem. The examples provided tend to focus on the 64­bit x86 PC (Intel and AMD) platform, with additional references to ARM­based Raspberry Pi sys­ tems. I might mention certain hardware peculiarities if they affect the digital forensics process in some way. Another aspect of this book is the discussion of Linux systems with a variety of uses and purposes. I cover methods for investigating both Linux server systems as well as Linux desktop systems. A wide range of scalability is assumed, and analysis techniques are applicable from tiny embedded Linux systems and Raspberry Pis, all the way up to large server clusters and Linux­ based mainframes. The assumption throughout this book is that we are performing a post­ mortem forensic analysis on a drive image, also known as dead disk forensics. Many books cover incident response and analysis of live Linux systems using commands while logged in to a running system. This book doesn’t cover live systems and assumes that a drive image has been acquired in a forensically sound manner or that a drive is safely attached to an examination machine with a forensic write blocker. That said, everything in this book will also be useful in the context of live system incident response. This book avoids going into too much depth on fringe or rare topics. In some cases, obscure topics might be mentioned and references provided, but the focus remains on covering the most popular Linux distributions, hardware architectures, and system applications. This book tries to remain non­political and non­religious about technol­ ogy. In the community there are often strong opinions about which technol­ ogy is better or worse, which licences are good or bad, which tech companies are altruistic or evil, and so on. I make a deliberate effort to avoid praising or criticizing any particular technology or company and avoid providing my personal opinions unless they are relevant to digital forensics. This combination of factors provides a book that is unique in the mar­ ketplace of digital forensics books, especially among those covering topics related to forensically analyzing Linux systems.
Recommended publications
  • Desktop Migration and Administration Guide
    Red Hat Enterprise Linux 7 Desktop Migration and Administration Guide GNOME 3 desktop migration planning, deployment, configuration, and administration in RHEL 7 Last Updated: 2021-05-05 Red Hat Enterprise Linux 7 Desktop Migration and Administration Guide GNOME 3 desktop migration planning, deployment, configuration, and administration in RHEL 7 Marie Doleželová Red Hat Customer Content Services [email protected] Petr Kovář Red Hat Customer Content Services [email protected] Jana Heves Red Hat Customer Content Services Legal Notice Copyright © 2018 Red Hat, Inc. This document is licensed by Red Hat under the Creative Commons Attribution-ShareAlike 3.0 Unported License. If you distribute this document, or a modified version of it, you must provide attribution to Red Hat, Inc. and provide a link to the original. If the document is modified, all Red Hat trademarks must be removed. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
    [Show full text]
  • Cryptomator Documentation Release 1.5.0
    Cryptomator Documentation Release 1.5.0 Cryptobot Sep 15, 2021 Desktop 1 Setup 3 1.1 Windows...............................................3 1.2 macOS................................................3 1.3 Linux.................................................3 2 Getting Started 5 3 Adding Vaults 7 3.1 Create a New Vault..........................................8 3.2 Open an Existing Vault........................................ 13 4 Accessing Vaults 15 4.1 Unlocking a Vault.......................................... 16 4.2 Working with the Unlocked Vault.................................. 17 4.3 Locking a vault............................................ 18 5 Password And Recovery Key 21 5.1 Change Password........................................... 21 5.2 Show Recovery Key......................................... 22 5.3 Reset Password............................................ 23 6 Vault Mounting 27 6.1 General Adapter Selection...................................... 27 6.2 Options applicable to all Systems and Adapters........................... 27 6.3 WebDAV-specific options...................................... 28 6.4 Dokany-specific options....................................... 28 6.5 FUSE-specific options........................................ 28 7 Vault Management 29 7.1 Remove Vaults............................................ 29 7.2 Reorder Vaults............................................ 29 7.3 Vault Options............................................. 29 8 Setup 33 8.1 Google PlayStore..........................................
    [Show full text]
  • Red Hat Enterprise Linux 8 Installing, Managing, and Removing User-Space Components
    Red Hat Enterprise Linux 8 Installing, managing, and removing user-space components An introduction to AppStream and BaseOS in Red Hat Enterprise Linux 8 Last Updated: 2021-06-25 Red Hat Enterprise Linux 8 Installing, managing, and removing user-space components An introduction to AppStream and BaseOS in Red Hat Enterprise Linux 8 Legal Notice Copyright © 2021 Red Hat, Inc. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/ . In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, the Red Hat logo, JBoss, OpenShift, Fedora, the Infinity logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. Linux ® is the registered trademark of Linus Torvalds in the United States and other countries. Java ® is a registered trademark of Oracle and/or its affiliates. XFS ® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL ® is a registered trademark of MySQL AB in the United States, the European Union and other countries.
    [Show full text]
  • Debian GNU/Linux 4.0 (“Etch”) (Mips )
    Debian GNU/Linux 4.0 (“etch”) JJー スノー( (Mips 用) Josip Rodin, Bob Hilliard, Adam Di Carlo, Anne Bezemer, Rob Bradford, Frans Pop (現在.AS&*), Andreas Barth (現在.AS&*), Javier Fernández-Sanguino Peña (現在.AS&*), Steve Langasek (現在.AS&*) <[email protected]> $Id: release-notes.en.sgml,v 1.312 2007-08-16 22:24:38 jseidel Exp $ i 目目目 hhh 1 //はじじじめAA+++ 1 1.1 この£書+¯するバグR報告する ...........................1 1.2 アップグレー)についての報告をする .........................2 1.3 この£書.ソース .....................................2 2 Debian GNU/Linux 4.0 ...最最最新新新情ss報報報 3 2.1 Mips +¯する最新情報 .................................4 2.2 ディストリビューション.最新情報 ..........................4 2.2.1 パッケージ管理 ..................................5 2.2.2 debian-volatile がGwサービス+ .......................6 2.3 システム.改, ......................................6 2.4 カー-K¯c.®要*¼f点 ..............................7 2.4.1 カーネルパッケージングにおける¼f ....................8 2.4.2 新しい initrd 生成Fーティリティ .......................8 2.4.3 #¿* /dev 管理(/ードウェア検õ .....................8 3 イイインSンスススト((ーーーKKルシシシススステ&&@@@ 11 3.1 インストールシステム.最新情報 ........................... 11 3.1.1 ®要*¼f点 ................................... 11 3.1.2 r#インストーK ................................ 13 3.2 ®気コンテスト ...................................... 14 4 )))MMM...JJJJJJーーースススかかからIIアアアッ##77プグググレLLーーー)))すすするKK 15 4.1 アップグレー).準& .................................. 15 4.1.1 あらゆる'ータD設¡s報Rバックアップする ............... 15 目 h ii 4.1.2 _M+Fーザ+通知する ............................ 16 4.1.3 復!.準& .................................... 16 4.1.4 アップグレー)用.!Q*環@.準& .................... 17 4.1.5 2.2 系カー-K/サポー(されなくなりました ................ 17 4.2 システム.x態Rチェックする ............................. 17 4.2.1 パッケージマネージャU.? ?.アクションRGx ........... 17 4.2.2 APT . pin 機能R\Iにする .......................... 18 4.2.3 パッケージ.x態Rチェックする ....................... 18 4.2.4 "Gw*ソース(バックポー( ........................ 19 4.3 パッケージ.>ークR±ù[')す .........................
    [Show full text]
  • Ubuntu Kung Fu
    Prepared exclusively for Alison Tyler Download at Boykma.Com What readers are saying about Ubuntu Kung Fu Ubuntu Kung Fu is excellent. The tips are fun and the hope of discov- ering hidden gems makes it a worthwhile task. John Southern Former editor of Linux Magazine I enjoyed Ubuntu Kung Fu and learned some new things. I would rec- ommend this book—nice tips and a lot of fun to be had. Carthik Sharma Creator of the Ubuntu Blog (http://ubuntu.wordpress.com) Wow! There are some great tips here! I have used Ubuntu since April 2005, starting with version 5.04. I found much in this book to inspire me and to teach me, and it answered lingering questions I didn’t know I had. The book is a good resource that I will gladly recommend to both newcomers and veteran users. Matthew Helmke Administrator, Ubuntu Forums Ubuntu Kung Fu is a fantastic compendium of useful, uncommon Ubuntu knowledge. Eric Hewitt Consultant, LiveLogic, LLC Prepared exclusively for Alison Tyler Download at Boykma.Com Ubuntu Kung Fu Tips, Tricks, Hints, and Hacks Keir Thomas The Pragmatic Bookshelf Raleigh, North Carolina Dallas, Texas Prepared exclusively for Alison Tyler Download at Boykma.Com Many of the designations used by manufacturers and sellers to distinguish their prod- ucts are claimed as trademarks. Where those designations appear in this book, and The Pragmatic Programmers, LLC was aware of a trademark claim, the designations have been printed in initial capital letters or in all capitals. The Pragmatic Starter Kit, The Pragmatic Programmer, Pragmatic Programming, Pragmatic Bookshelf and the linking g device are trademarks of The Pragmatic Programmers, LLC.
    [Show full text]
  • PDF-Dokumenten Zusammenzusetzen Im Test Raspi 3A+
    Haiku: BeOS-Klon bekommt RasPi 3 Modell A+: Neuer easyLINUX COMMUNITY-EDITIONJetzt mit zusätzlichen Seiten ! rund umneues den Paketmanagement Linux-Einstieg S. 82 Mini-PC im Überblick S. 86 Frei kopieren und beliebig weiter verteilen ! 02.2019 02.2019 Digitale Notizen, Gliederungseditoren, Zusammenarbeit im LAN und unterwegs WISSEN TEILEN WISSEN TEILEN WISSEN Mini-Server: Vorträge um ein Diskussionsforum ergänzen S. 28 Joplin: Evernote-Ersatz ohne Zwang zur Cloud S. 32 Pydio Cells: Dateien teilen und gemeinsam bearbeiten S. 24 Cherrytree und Piggydb: Daten ordnen und miteinander vernetzen S. 16 Steam Play: Der neue Valve-Client im Test Dank Vulkan-API und Proton verspricht das Unternehmen mehr Spiele für Linux – unser Report deckt das Potenzial und die Probleme des neuen Ansatzes auf S. 74 Hilfe aus der Ferne Netzwerk-Konfiguration Einsteigertaugliche Remote-Software Mit nur einem Tool Geräte einrichten, öffnet SSH-Zugang zum eigenen PC S.38 Routen setzen und Traffic steuern S. 80 Top-Distris auf zwei Heft-DVDs MANJARO 18 • APT-CLONE • PLASMA 5.14 • GIMP 2.10 • RASPI 3A+ • • 3A+ RASPI • 2.10 GIMP • 5.14 PLASMA • APT-CLONE • 18 MANJARO EUR 8,50 EUR 9,35 sfr 17,00 EUR 10,85 EUR 11,05 EUR 11,05 02 www.linux-user.de Deutschland Österreich Schweiz Benelux Spanien Italien 4 196067 008502 02 Editorial Lindows? Sehr geehrte Leserinnen und Leser, wer sich gelegentlich auch in englisch- sprachigen Medien über Linux und quell- offene Software informiert, der kennt unvermeidlich das Kürzel sjvn: Steven J. Vaughan-Nichols liefert seit Jahrzehnten technische Hintergrund informationen und spitzzüngige Meinungsstücke über Jörg Luther das Open-Source- Umfeld.
    [Show full text]
  • Linux Apps That Run Anywhere
    7/22/2018 AppImage | Linux apps that run anywhere Linux apps that run anywhere (h "As a user, I want to download an application from the original author, and run it on my Linux desktop system just like I would do with a Windows or Mac application." (m "As an application author, I want to provide packages for Linux desktop systems, without the (h need to get it 'into' a distribution and without having to build for gazillions of different distributions." (h (h (h LEADING LINUX DISTRIBUTIONS Download an application, make it executable, and run! No need to install. No system libraries or system preferences are altered. Can also run in a sandbox like Firejail (https://github.com/netblue30/firejail) https://appimage.org/ 1/10 7/22/2018 AppImage | Linux apps that run anywhere (h (m (h (h Distribute your desktop Linux application in the AppImage format and win users running all common Linux distributions. Package once and run everywhere. Reach users on all major desktop distributions. (h (h WHAT PEOPLE THINK https://appimage.org/ 2/10 7/22/2018 AppImage | Linux apps that run anywhere (h Dirk Hohndel (m "The AppImage approach is really really useful." Picture: Copyright Faces of Open Source / Peter Adams. Licensed under CC-BY-NC-SA 4.0. Original picture (h (http://facesofopensource.com/dirk-hohndel/) (h (h (h https://appimage.org/ 3/10 7/22/2018 AppImage | Linux apps that run anywhere (h (m (h Drawing: [email protected] Larry Ewing and The GIMP. (h SEE IT IN ACTION (h Here is an application packaged as an AppImage for you to try.
    [Show full text]
  • The GNOME Census: Who Writes GNOME?
    The GNOME Census: Who writes GNOME? Dave Neary & Vanessa David, Neary Consulting © Neary Consulting 2010: Some rights reserved Table of Contents Introduction.........................................................................................3 What is GNOME?.............................................................................3 Project governance...........................................................................3 Why survey GNOME?.......................................................................4 Scope and methodology...................................................................5 Tools and Observations on Data Quality..........................................7 Results and analysis...........................................................................10 GNOME Project size.......................................................................10 The Long Tail..................................................................................11 Effects of commercialisation..........................................................14 Who does the work?.......................................................................15 Who maintains GNOME?................................................................17 Conclusions........................................................................................22 References.........................................................................................24 Appendix 1: Modules included in survey...........................................25 2 Introduction What
    [Show full text]
  • An User & Developer Perspective on Immutable Oses
    An User & Developer Perspective on Dario Faggioli Virtualization SW. Eng. @ SUSE Immutable OSes [email protected] dariof @DarioFaggioli https://dariofaggioli.wordpress.com/ https://about.me/dario.faggioli About Me What I do ● Virtualization Specialist Sw. Eng. @ SUSE since 2018, working on Xen, KVM, QEMU, mostly about performance related stuff ● Daily activities ⇒ how and what for I use my workstation ○ Read and send emails (Evolution, git-send-email, stg mail, ...) ○ Write, build & test code (Xen, KVM, Libvirt, QEMU) ○ Work with the Open Build Service (OBS) ○ Browse Web ○ Test OSes in VMs ○ Meetings / Video calls / Online conferences ○ Chat, work and personal ○ Some 3D Printing ○ Occasionally play games ○ Occasional video-editing ○ Maybe scan / print some document 2 ● Can all of the above be done with an immutable OS ? Immutable OS: What ? Either: ● An OS that you cannot modify Or, at least: ● An OS that you will have an hard time modifying What do you mean “modify” ? ● E.g., installing packages ● ⇒ An OS on which you cannot install packages ● ⇒ An OS on which you will have an hard time installing packages 3 Immutable OS: What ? Seriously? 4 Immutable OS: Why ? Because it will stay clean and hard to break ● Does this sound familiar? ○ Let’s install foo, and it’s dependency, libfoobar_1 ○ Let’s install bar (depends from libfoobar_1, we have it already) ○ Actually, let’s add an external repo. It has libfoobar_2 that makes foo work better! ○ Oh no... libfoobar_2 would break bar!! ● Yeah. It happens. Even in the best families distros
    [Show full text]
  • Release Notes for Fedora 15
    Fedora 15 Release Notes Release Notes for Fedora 15 Edited by The Fedora Docs Team Copyright © 2011 Red Hat, Inc. and others. The text of and illustrations in this document are licensed by Red Hat under a Creative Commons Attribution–Share Alike 3.0 Unported license ("CC-BY-SA"). An explanation of CC-BY-SA is available at http://creativecommons.org/licenses/by-sa/3.0/. The original authors of this document, and Red Hat, designate the Fedora Project as the "Attribution Party" for purposes of CC-BY-SA. In accordance with CC-BY-SA, if you distribute this document or an adaptation of it, you must provide the URL for the original version. Red Hat, as the licensor of this document, waives the right to enforce, and agrees not to assert, Section 4d of CC-BY-SA to the fullest extent permitted by applicable law. Red Hat, Red Hat Enterprise Linux, the Shadowman logo, JBoss, MetaMatrix, Fedora, the Infinity Logo, and RHCE are trademarks of Red Hat, Inc., registered in the United States and other countries. For guidelines on the permitted uses of the Fedora trademarks, refer to https:// fedoraproject.org/wiki/Legal:Trademark_guidelines. Linux® is the registered trademark of Linus Torvalds in the United States and other countries. Java® is a registered trademark of Oracle and/or its affiliates. XFS® is a trademark of Silicon Graphics International Corp. or its subsidiaries in the United States and/or other countries. MySQL® is a registered trademark of MySQL AB in the United States, the European Union and other countries. All other trademarks are the property of their respective owners.
    [Show full text]
  • The Next-Gen Apertis Application Framework 1 Contents
    The next-gen Apertis application framework 1 Contents 2 Creating a vibrant ecosystem ....................... 2 3 The next-generation Apertis application framework ........... 3 4 Application runtime: Flatpak ....................... 4 5 Compositor: libweston ........................... 6 6 Audio management: PipeWire and WirePlumber ............ 7 7 Session management: systemd ....................... 7 8 Software distribution: hawkBit ...................... 8 9 Evaluation .................................. 8 10 Focus on the development user experience ................ 12 11 Legacy Apertis application framework 13 12 High level implementation plan for the next-generation Apertis 13 application framework 14 14 Flatpak on the Apertis images ...................... 15 15 The Apertis Flatpak application runtime ................. 15 16 Implement a new reference graphical shell/compositor ......... 16 17 Switch to PipeWire for audio management ................ 16 18 AppArmor support ............................. 17 19 The app-store ................................ 17 20 As a platform, Apertis needs a vibrant ecosystem to thrive, and one of the 21 foundations of such ecosystem is being friendly to application developers and 22 product teams. Product teams and application developers are more likely to 23 choose Apertis if it offers flows for building, shipping, and updating applications 24 that are convenient, cheap, and that require low maintenance. 25 To reach that goal, a key guideline is to closely align to upstream solutions 26 that address those needs and integrate them into Apertis, to provide to appli- 27 cation authors a framework that is made of proven, stable, complete, and well 28 documented components. 29 The cornerstone of this new approach is the adoption of Flatpak, the modern 30 application system already officially supported on more than 20 Linux distribu- 1 31 tions , including Ubuntu, Fedora, Red Hat Enterprise, Alpine, Arch, Debian, 32 ChromeOS, and Raspian.
    [Show full text]
  • SUSE® Linux Enterprise Desktop 12 and the Workstation Extension: What's New ?
    SUSE® Linux Enterprise Desktop 12 and the Workstation Extension: What's New ? Frédéric Crozat <[email protected]> Enterprise Desktop Release Manager Scott Reeves <[email protected]> Enterprise Desktop Development Manager Agenda • Design Criteria • Desktop Environment in SUSE Linux Enterprise 12 • GNOME Shell • Desktop Features and Applications 2 Design Criteria SUSE Linux Enterprise Desktop Interoperability Ease of Use Security Ease of Management Lower Costs 4 SUSE Linux Enterprise Desktop 12 • Focus on technical workstation ‒ Developers and System administrators • One tool for the job • Main desktop applications will be shipped: ‒ Mail client, Office Suite, Graphical Editors, ... • SUSE Linux Enterprise Workstation Extension ‒ Extend SUSE Linux Enterprise Server with packages only available on SUSE Linux Enterprise Desktop. (x86-64 only) 5 Desktop in SUSE Linux Enterprise 12 As Part of the Common Code Base SUSE Linux Enterprise 12 Desktop Environment • SUSE Linux Enterprise 12 contains one primary desktop environment • Additional light-weight environment for special use-cases: ‒ Integrated Systems • Desktop environment is shared between the server and desktop products 7 SUSE Linux Enterprise 12 Desktop Environment • GNOME 3 is the main desktop environment ‒ SLE Classic mode by default ‒ GNOME 3 Classic Mode and GNOME 3 Shell Mode also available • SUSE Linux Enterprise 12 ships also lightweight IceWM ‒ Targeted at Integrated Systems • QT fully supported: ‒ QT5 supported for entire SLE12 lifecycle ‒ QT4 supported, will be removed in future
    [Show full text]