A Proactive Network Surveillance Framework

Total Page:16

File Type:pdf, Size:1020Kb

A Proactive Network Surveillance Framework A Proactive Network Surveillance Framework A Thesis submitted for the award of the degree of DOCTOR OF PHILOSOPHY by Maninder Singh under the Guidance of Dr. S. C. Saxena Director, Indian Institute of Technology, Roorkee Uttaranchal, INDIA -247667 & Dr. Seema Bawa Professor, Department of Computer Science & Engineering Thapar Institute of Engineering & Technology, Patiala Punjab, INDIA -147004 Computer Science and Engineering Department Thapar Institute of Engineering & Technology A Deemed University, Patiala – 147 004, INDIA January, 2007 dedicated to One Universal Creator God. The Name Is Truth. Creative Being Personified. No Fear. No Hatred. Image Of The Undying, Beyond Birth, Self-Existent. By Guru’s Grace Chant And Meditate True In The Primal Beginning. True Throughout The Ages. True Here And Now. O Nanak, Forever And Ever True ||1||1 1Sri Guru Granth Sahib Ji Contents List of Figures . v List of Tables . viii Certificate . ix Acknowledgement . x Abstract . xii 1 Introduction 1 1.1 Primary Network stakeholders: Hosts and Domains . 2 1.1.1 World Internet Usage and Population Statistics . 4 1.2 A preamble to Network Security . 5 1.3 Organization of the Thesis . 9 2 Literature Review 12 2.1 OSI Model and Various Protocols . 13 2.1.1 Open System Interconnection Model . 13 2.1.2 Internet Protocol (IP) . 16 2.1.3 Transport Control Protocol (TCP) . 18 2.1.4 Address Resolution Protocol (ARP) . 21 2.1.5 Internet Control Message Protocol (ICMP) . 22 2.2 Network Security Expatiation . 23 2.2.1 Reactive Security . 38 2.2.2 Proactive Security . 44 2.3 Problem Formulation . 50 3 Exploits and their Detrimental Effects 52 ii 3.1 Life Cycle of a Vulnerability and an Exploit . 52 3.2 Stack Overruns . 54 3.2.1 Exploit Development Process . 58 3.2.2 Life Cycle of a Typical Windows Exploit . 59 3.2.3 Finding the Attack Vector . 60 3.2.4 Selecting a Control Vector . 64 3.2.5 Finding and Using a Return Address . 65 3.2.6 Finding Bad Characters . 66 3.2.7 Choosing a Payload and Encoder . 67 3.2.8 Suggested Overflow Defense Methods . 68 3.3 Denial of Service Attacks (DoS) . 71 3.3.1 Ping of Death . 72 3.3.2 Land Exploit . 75 3.3.3 Smurf . 76 3.3.4 SYN Flood . 78 3.4 A Live walk-through into System Hacking . 80 3.4.1 Reconnaissance and Enumeration Phase . 81 3.4.2 Attack Phase . 85 3.4.3 Analysis of Hacked Data . 86 3.5 Conclusions . 87 4 Analysis of Opensource Honeypots 88 4.1 Use of Honeypots in Network Security . 88 4.1.1 Using Honeypots in the DeMilitarized Zone (DMZ) . 89 4.2 Tradeoffs between Levels of Interaction . 90 4.2.1 Low Level of Interaction . 90 4.2.2 Medium Level of Interaction . 91 4.2.3 High Level of Interaction . 92 4.3 Honeypots: Exploration and Analysis . 92 4.3.1 BackOfficer Friendly (BOF) . 93 4.3.2 Honeyd . 95 iii 4.3.3 Honeynets . 100 4.4 Conclusions . 106 5 Proposed Proactive Network Surveillance Framework: Design and Im- plementation Details 107 5.1 Core Security Layer . 108 5.1.1 Implementation Details: Filesystem Level . 108 5.1.2 Implementation Details: SSH login Key-pair . 115 5.2 Routing and Traffic Control Layer . 119 5.2.1 Implementation Details . 120 5.3 Security Information System Layer . 128 5.3.1 Implementation Details . 129 5.4 Perimeter Security Layer . 137 5.4.1 Implementation Details: Firewall . 137 5.4.2 Implementation Details: IDS . 141 5.5 Learn and Monitor the Unknown Layer . 144 5.5.1 Implementation Details: Hardening Steps . 144 5.5.2 Implementation Details: Honeypot . 148 5.6 Conclusions . 150 6 Deployment, Testing of the Framework and Results Obtained 151 6.1 Framework Evaluation and Results: Case I . 151 6.2 Framework Evaluation and Results: Case II . 157 6.3 Conclusions . 164 7 Conclusions and Future Scope of the Work 175 7.1 Conclusions . 175 7.2 Future Scope of Work . 178 References 180 List of Publications 191 iv List of Figures 1.1 Internet Domain Survey Host Count . 5 1.2 Crime Loss Statistics . 7 1.3 Dial-up Connections bypassing Network Periphery Security. 7 2.1 Headers and Data can be Encapsulated during Information Exchange . 15 2.2 IP Packet Format . 17 2.3 TCP Packet Format . 19 2.4 A Transport Control Protocol [TCP] Session. 20 2.5 The hierarchy of Security specializations. 24 2.6 Layout showing the major ISPs [Che99] . 27 2.7 Cyberspace and the Physical World . 28 2.8 Attack Sophistication and required Intruder Knowledge . 29 2.9 Number of Intruders able to Execute Attack . 30 2.10 Security Attacks . 31 2.11 Schematic of a Firewall . 39 2.12 Generation I Honeynet . 49 2.13 Generation II Honeynet . 50 3.1 Vulnerability Life Cycle . 53 3.2 Exploit Categorization . 54 3.3 Memory layout of a Linux process . 56 3.4 View of a Stack . 57 3.5 Exploit Analysis Test-Bed . 60 3.6 A Banner Grab of IIS version 5.0 . 62 3.7 A Banner Grab of IIS version 5.1 . 62 v 3.8 First Attack String after appropriate buffer calculations . 63 3.9 IIS 5.0 attached to OllyDbg for debugging . 64 3.10 Successful Exploitation of Windows2000 Sp0 . 68 3.11 Distributed Denial of Service Attack . 71 3.12 Smurf Attack Signatures . 77 3.13 SYN Flood Attack Signatures . 80 3.14 Active Reconnaissance: Probing the system with a tool . 82 3.15 Enumeration Phase of the Victim Machine . 83 3.16 Using DCOM-RPC Exploit . 85 3.17 Importing LM and NT hashes for password Cracking . 86 4.1 Honeypot Deployment in DeMilitarized Zone (DMZ) . 90 4.2 Test Bed for Honeypots Exploration and Analysis . 93 4.3 Back Officer Friendly Honeypot Running and Emulating services . 94 4.4 BOF Honeypot Telnet fake replies . 95 4.5 Nmap output: Attacker scanning Honeyd default host . 96 4.6 Basic Architecture of Honeynet . 102 4.7 Tcpdump network traffic log analyzed using Wireshark . 105 4.8 Flow graph statistics of an attack . 105 5.1 Proposed Framework . 109 5.2 Packet’s Journey through Kernel Tables and qdiscs . 123 5.3 Security Information System Layer . 129 5.4 Firewall placement inside network security hierarchy. 137 5.5 Firewall flow chart based on IPTables. 139 5.6 Intrusion Detection System (IDS) placement inside network security hier- archy. ..................................... 142 5.7 Virtual Honeypots Setup . 149 6.1 Test Bed for Testing the Proposed Framework . 152 6.2 Protocol Hierarchy Statistics . 154 6.3 IO Flow Graphs . 155 vi 6.4 Testing with Live Network at Thapar Institute of Engineering and Tech- nology . ..
Recommended publications
  • Administration and Reference Guide
    Oracle® Database Appliance Administration and Reference Guide Release 12.2.1.4.0 for Linux x86-64 E97563-01 June 2018 Oracle Database Appliance Administration and Reference Guide, Release 12.2.1.4.0 for Linux x86-64 E97563-01 Copyright © 2014, 2018, 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.
    [Show full text]
  • MINCS - the Container in the Shell (Script)
    MINCS - The Container in the Shell (script) - Masami Hiramatsu <[email protected]> Tech Lead, Linaro Ltd. Open Source Summit Japan 2017 LEADING COLLABORATION IN THE ARM ECOSYSTEM Who am I... Masami Hiramatsu - Linux kernel kprobes maintainer - Working for Linaro as a Tech Lead LEADING COLLABORATION IN THE ARM ECOSYSTEM Demo # minc top # minc -r /opt/debian/x86_64 # minc -r /opt/debian/arm64 --arch arm64 LEADING COLLABORATION IN THE ARM ECOSYSTEM What Is MINCS? My Personal Fun Project to learn how linux containers work :-) LEADING COLLABORATION IN THE ARM ECOSYSTEM What Is MINCS? Mini Container Shell Scripts (pronounced ‘minks’) - Container engine implementation using POSIX shell scripts - It is small (~60KB, ~2KLOC) (~20KB in minimum) - It can run on busybox - No architecture dependency (* except for qemu/um mode) - No need for special binaries (* except for libcap, just for capsh --exec) - Main Features - Namespaces (Mount, PID, User, UTS, Net*) - Cgroups (CPU, Memory) - Capabilities - Overlay filesystem - Qemu cross-arch/system emulation - User-mode-linux - Image importing from dockerhub And all are done by CLI commands :-) LEADING COLLABORATION IN THE ARM ECOSYSTEM Why Shell Script? That is my favorite language :-) - Easy to understand for *nix administrators - Just a bunch of commands - Easy to modify - Good for prototyping - Easy to deploy - No architecture dependencies - Very small - Able to run on busybox (+ libcap is perfect) LEADING COLLABORATION IN THE ARM ECOSYSTEM MINCS Use-Cases For Learning - Understand how containers work For Development - Prepare isolated (cross-)build environment For Testing - Test new applications in isolated environment - Test new kernel features on qemu using local tools For products? - Maybe good for embedded devices which has small resources LEADING COLLABORATION IN THE ARM ECOSYSTEM What Is A Linux Container? There are many linux container engines - Docker, LXC, rkt, runc, ..
    [Show full text]
  • Hardening Linux
    eBooks-IT.org 4444_FM_final.qxd 1/5/05 12:39 AM Page i eBooks-IT.org Hardening Linux JAMES TURNBULL 4444_FM_final.qxd 1/5/05 12:39 AM Page ii eBooks-IT.org Hardening Linux Copyright © 2005 by James Turnbull 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 information storage or retrieval system, without the prior written permission of the copyright owner and the publisher. ISBN (pbk): 1-59059-444-4 Printed and bound in the United States of America 987654321 Trademarked names may appear in this book. Rather than use a trademark symbol with every occurrence of a trademarked name, we use the names only in an editorial fashion and to the benefit of the trademark owner, with no intention of infringement of the trademark. Lead Editor: Jim Sumser Technical Reviewer: Judith Myerson Editorial Board: Steve Anglin, Dan Appleman, Ewan Buckingham, Gary Cornell, Tony Davis, Jason Gilmore, Chris Mills, Dominic Shakeshaft, Jim Sumser Project Manager: Kylie Johnston Copy Edit Manager: Nicole LeClerc Copy Editor: Kim Wimpsett Production Manager: Kari Brooks-Copony Production Editor: Kelly Winquist Compositor: Linda Weidemann Proofreader: Lori Bring Indexer: Kevin Broccoli Artist: Kinetic Publishing Services, LLC Cover Designer: Kurt Krames Manufacturing Manager: Tom Debolski Distributed to the book trade in the United States by Springer-Verlag New York, Inc., 233 Spring Street, 6th Floor, New York, NY 10013, and outside the United States by Springer-Verlag GmbH & Co. KG, Tiergartenstr. 17, 69112 Heidelberg, Germany. In the United States: phone 1-800-SPRINGER, fax 201-348-4505, e-mail [email protected], or visit http://www.springer-ny.com.
    [Show full text]
  • MC-1200 Series Linux Software User's Manual
    MC-1200 Series Linux Software User’s Manual Version 1.0, November 2020 www.moxa.com/product © 2020 Moxa Inc. All rights reserved. MC-1200 Series Linux Software User’s Manual The software described in this manual is furnished under a license agreement and may be used only in accordance with the terms of that agreement. Copyright Notice © 2020 Moxa Inc. All rights reserved. Trademarks The MOXA logo is a registered trademark of Moxa Inc. All other trademarks or registered marks in this manual belong to their respective manufacturers. Disclaimer Information in this document is subject to change without notice and does not represent a commitment on the part of Moxa. Moxa provides this document as is, without warranty of any kind, either expressed or implied, including, but not limited to, its particular purpose. Moxa reserves the right to make improvements and/or changes to this manual, or to the products and/or the programs described in this manual, at any time. Information provided in this manual is intended to be accurate and reliable. However, Moxa assumes no responsibility for its use, or for any infringements on the rights of third parties that may result from its use. This product might include unintentional technical or typographical errors. Changes are periodically made to the information herein to correct such errors, and these changes are incorporated into new editions of the publication. Technical Support Contact Information www.moxa.com/support Moxa Americas Moxa China (Shanghai office) Toll-free: 1-888-669-2872 Toll-free: 800-820-5036 Tel: +1-714-528-6777 Tel: +86-21-5258-9955 Fax: +1-714-528-6778 Fax: +86-21-5258-5505 Moxa Europe Moxa Asia-Pacific Tel: +49-89-3 70 03 99-0 Tel: +886-2-8919-1230 Fax: +49-89-3 70 03 99-99 Fax: +886-2-8919-1231 Moxa India Tel: +91-80-4172-9088 Fax: +91-80-4132-1045 Table of Contents 1.
    [Show full text]
  • The Linux Device File-System
    The Linux Device File-System Richard Gooch EMC Corporation [email protected] Abstract 1 Introduction All Unix systems provide access to hardware via de- vice drivers. These drivers need to provide entry points for user-space applications and system tools to access the hardware. Following the \everything is a file” philosophy of Unix, these entry points are ex- posed in the file name-space, and are called \device The Device File-System (devfs) provides a power- special files” or \device nodes". ful new device management mechanism for Linux. Unlike other existing and proposed device manage- This paper discusses how these device nodes are cre- ment schemes, it is powerful, flexible, scalable and ated and managed in conventional Unix systems and efficient. the limitations this scheme imposes. An alternative mechanism is then presented. It is an alternative to conventional disc-based char- acter and block special devices. Kernel device drivers can register devices by name rather than de- vice numbers, and these device entries will appear in the file-system automatically. 1.1 Device numbers Devfs provides an immediate benefit to system ad- ministrators, as it implements a device naming scheme which is more convenient for large systems Conventional Unix systems have the concept of a (providing a topology-based name-space) and small \device number". Each instance of a driver and systems (via a device-class based name-space) alike. hardware component is assigned a unique device number. Within the kernel, this device number is Device driver authors can benefit from devfs by used to refer to the hardware and driver instance.
    [Show full text]
  • Singularityce User Guide Release 3.8
    SingularityCE User Guide Release 3.8 SingularityCE Project Contributors Aug 16, 2021 CONTENTS 1 Getting Started & Background Information3 1.1 Introduction to SingularityCE......................................3 1.2 Quick Start................................................5 1.3 Security in SingularityCE........................................ 15 2 Building Containers 19 2.1 Build a Container............................................. 19 2.2 Definition Files.............................................. 24 2.3 Build Environment............................................ 35 2.4 Support for Docker and OCI....................................... 39 2.5 Fakeroot feature............................................. 79 3 Signing & Encryption 83 3.1 Signing and Verifying Containers.................................... 83 3.2 Key commands.............................................. 88 3.3 Encrypted Containers.......................................... 90 4 Sharing & Online Services 95 4.1 Remote Endpoints............................................ 95 4.2 Cloud Library.............................................. 103 5 Advanced Usage 109 5.1 Bind Paths and Mounts.......................................... 109 5.2 Persistent Overlays............................................ 115 5.3 Running Services............................................. 118 5.4 Environment and Metadata........................................ 129 5.5 OCI Runtime Support.......................................... 140 5.6 Plugins.................................................
    [Show full text]
  • Building Embedded Linux Systems ,Roadmap.18084 Page Ii Wednesday, August 6, 2008 9:05 AM
    Building Embedded Linux Systems ,roadmap.18084 Page ii Wednesday, August 6, 2008 9:05 AM Other Linux resources from O’Reilly Related titles Designing Embedded Programming Embedded Hardware Systems Linux Device Drivers Running Linux Linux in a Nutshell Understanding the Linux Linux Network Adminis- Kernel trator’s Guide Linux Books linux.oreilly.com is a complete catalog of O’Reilly’s books on Resource Center Linux and Unix and related technologies, including sample chapters and code examples. ONLamp.com is the premier site for the open source web plat- form: Linux, Apache, MySQL, and either Perl, Python, or PHP. Conferences O’Reilly brings diverse innovators together to nurture the ideas that spark revolutionary industries. We specialize in document- ing the latest tools and systems, translating the innovator’s knowledge into useful skills for those in the trenches. Visit con- ferences.oreilly.com for our upcoming events. Safari Bookshelf (safari.oreilly.com) is the premier online refer- ence library for programmers and IT professionals. Conduct searches across more than 1,000 books. Subscribers can zero in on answers to time-critical questions in a matter of seconds. Read the books on your Bookshelf from cover to cover or sim- ply flip to the page you need. Try it today for free. main.title Page iii Monday, May 19, 2008 11:21 AM SECOND EDITION Building Embedded Linux SystemsTomcat ™ The Definitive Guide Karim Yaghmour, JonJason Masters, Brittain Gilad and Ben-Yossef, Ian F. Darwin and Philippe Gerum Beijing • Cambridge • Farnham • Köln • Sebastopol • Taipei • Tokyo Building Embedded Linux Systems, Second Edition by Karim Yaghmour, Jon Masters, Gilad Ben-Yossef, and Philippe Gerum Copyright © 2008 Karim Yaghmour and Jon Masters.
    [Show full text]
  • ODROID-HC2: 3.5” High Powered Storage  February 1, 2018
    ODROID WiFi Access Point: Share Files Via Samba February 1, 2018 How to setup an ODROID with a WiFi access point so that an ODROID’s hard drive can be accessed and modied from another computer. This is primarily aimed at allowing access to images, videos, and log les on the ODROID. ODROID-HC2: 3.5” High powered storage February 1, 2018 The ODROID-HC2 is an aordable mini PC and perfect solution for a network attached storage (NAS) server. This device home cloud-server capabilities centralizes data and enables users to share and stream multimedia les to phones, tablets, and other devices across a network. It is an ideal tool for many use Using SquashFS As A Read-Only Root File System February 1, 2018 This guide describes the usage of SquashFS PiFace: Control and Display 2 February 1, 2018 For those who have the PiFace Control and Display 2, and want to make it compatible with the ODROID-C2 Android Gaming: Data Wing, Space Frontier, and Retro Shooting – Pixel Space Shooter February 1, 2018 Variations on a theme! Race, blast into space, and blast things into pieces that are racing towards us. The fun doesn’t need to stop when you take a break from your projects. Our monthly pick on Android games. Linux Gaming: Saturn Games – Part 1 February 1, 2018 I think it’s time we go into a bit more detail about Sega Saturn for the ODROID-XU3/XU4 Gaming Console: Running Your Favorite Games On An ODROID-C2 Using Android February 1, 2018 I built a gaming console using an ODROID-C2 running Android 6 Controller Area Network (CAN) Bus: Implementation
    [Show full text]
  • Kernel Command Line: Root=/Dev/Disk/By-Path/Ccw-0.0.0160-Part1 TERM=Dumb BOOT IMAGE=0
    Ready; T=0.01/0.01 20:49:10 ipl 160 clear zIPL v1.8.0-44.45.2 interactive boot menu 0. default (ipl) 1. ipl Note: VM users please use '#cp vi vmsg <number> <kernel-parameters>' Please choose (default will boot in 10 seconds): Booting default (ipl)... Initializing cgroup subsys cpuset Initializing cgroup subsys cpu Linux version 2.6.32.36-0.5-default (geeko@buildhost) (gcc version 4.3.4 [gcc-4_3- branch revision 152973] (SUSE Linux) ) #1 SMP 2011 -04-14 10:12:31 +0200 setup.1a06a7: Linux is running as a z/VM guest operating system in 64-bit mode Zone PFN ranges: DMA 0x00000000 -> 0x00080000 Normal 0x00080000 -> 0x00080000 Movable zone start PFN for each node early_node_map[1] active PFN ranges 0: 0x00000000 -> 0x00020000 PERCPU: Embedded 11 pages/cpu @0000000000e92000 s12544 r8192 d24320 u65536 pcpu-alloc: s12544 r8192 d24320 u65536 alloc=16*4096 pcpu-alloc: [0] 00 [0] 01 [0] 02 [0] 03 [0] 04 [0] 05 [0] 06 [0] 07 pcpu-alloc: [0] 08 [0] 09 [0] 10 [0] 11 [0] 12 [0] 13 [0] 14 [0] 15 pcpu-alloc: [0] 16 [0] 17 [0] 18 [0] 19 [0] 20 [0] 21 [0] 22 [0] 23 pcpu-alloc: [0] 24 [0] 25 [0] 26 [0] 27 [0] 28 [0] 29 [0] 30 [0] 31 pcpu-alloc: [0] 32 [0] 33 [0] 34 [0] 35 [0] 36 [0] 37 [0] 38 [0] 39 pcpu-alloc: [0] 40 [0] 41 [0] 42 [0] 43 [0] 44 [0] 45 [0] 46 [0] 47 pcpu-alloc: [0] 48 [0] 49 [0] 50 [0] 51 [0] 52 [0] 53 [0] 54 [0] 55 pcpu-alloc: [0] 56 [0] 57 [0] 58 [0] 59 [0] 60 [0] 61 [0] 62 [0] 63 Built 1 zonelists in Zone order, mobility grouping on.
    [Show full text]
  • Petalinux Tools Documentation: Reference Guide
    See all versions of this document PetaLinux Tools Documentation Reference Guide UG1144 (v2021.1) June 16, 2021 Revision History Revision History The following table shows the revision history for this document. Section Revision Summary 06/16/2021 Version 2021.1 Chapter 7: Customizing the Project Added a new section: Configuring UBIFS Boot. Chapter 5: Booting and Packaging Updated Steps to Boot a PetaLinux Image on Hardware with SD Card. Appendix A: Migration Added FPGA Manager Changes, Yocto Recipe Name Changes, Host GCC Version Upgrade. Chapter 10: Advanced Configurations Updated U-Boot Configuration and Image Packaging Configuration. UG1144 (v2021.1) June 16, 2021Send Feedback www.xilinx.com PetaLinux Tools Documentation Reference Guide 2 Table of Contents Revision History...............................................................................................................2 Chapter 1: Overview.................................................................................................... 8 Introduction................................................................................................................................. 8 Navigating Content by Design Process.................................................................................... 9 Chapter 2: Setting Up Your Environment...................................................... 11 Installation Steps.......................................................................................................................11 PetaLinux Working Environment Setup................................................................................
    [Show full text]
  • Linux Kernel User Documentation V4.20.0
    usepackagefontspec setsansfontDejaVu Sans setromanfontDejaVu Serif setmonofontDejaVu Sans Mono Linux Kernel User Documentation v4.20.0 The kernel development community 1 16, 2019 Contents 1 Linux kernel release 4.x <http://kernel.org/> 3 2 The kernel’s command-line parameters 9 3 Linux allocated devices (4.x+ version) 109 4 L1TF - L1 Terminal Fault 171 5 Reporting bugs 181 6 Security bugs 185 7 Bug hunting 187 8 Bisecting a bug 193 9 Tainted kernels 195 10 Ramoops oops/panic logger 197 11 Dynamic debug 201 12 Explaining the dreaded “No init found.” boot hang message 207 13 Rules on how to access information in sysfs 209 14 Using the initial RAM disk (initrd) 213 15 Control Group v2 219 16 Linux Serial Console 245 17 Linux Braille Console 247 18 Parport 249 19 RAID arrays 253 20 Kernel module signing facility 263 21 Linux Magic System Request Key Hacks 267 i 22 Unicode support 273 23 Software cursor for VGA 277 24 Kernel Support for miscellaneous (your favourite) Binary Formats v1.1 279 25 Mono(tm) Binary Kernel Support for Linux 283 26 Java(tm) Binary Kernel Support for Linux v1.03 285 27 Reliability, Availability and Serviceability 293 28 A block layer cache (bcache) 309 29 ext4 General Information 319 30 Power Management 327 31 Thunderbolt 349 32 Linux Security Module Usage 353 33 Memory Management 369 ii Linux Kernel User Documentation, v4.20.0 The following is a collection of user-oriented documents that have been added to the kernel over time. There is, as yet, little overall order or organization here — this material was not written to be a single, coherent document! With luck things will improve quickly over time.
    [Show full text]
  • Linux Add-In: User Guide
    Linux Add-in: User Guide Linux Add-in: User Guide © 2019 Analog Devices, Inc. Version 1.3.1, May 2019 http://www.analog.com Contents 1 Introduction 8 2 Quick Start Guide 9 2.1 Feature list for Linux on sc5xx boards 9 2.2 SC5xx EZ-Kit Linux Quick Start Guide 12 2.2.1 Introduction 12 2.2.2 Environment set up 13 2.2.3 Flashing U-Boot for the First Time 17 2.2.4 Booting Linux Overview 20 2.2.5 Boot method 1: Copying the Linux image across the network 21 2.2.6 Boot method 2: Booting flashed Linux with persistent file system on SD Card 29 2.2.7 Boot Method 3: Booting the kernel from the SD Card (Quicker Boot) 33 2.2.8 Troubleshooting 34 2.3 Configure and build from source code 35 2.3.1 Introduction 35 2.3.2 Extract the source code 35 2.3.3 Configure and build u-boot 36 2.3.4 Configure and build Buildroot and Linux kernel 37 2.3.5 Customize the Buildroot and Linux kernel 37 2.3.6 Generate Kernel Image for Booting From Non-Volatile Storage 39 2.3.7 More tips about buildroot 39 2.4 SC589-MINI Linux Quick Start Guide 40 2.4.1 Introduction 40 2.4.2 Set up the Board and Console output 42 2.4.3 Booting the board Out of the Box 44 2.4.4 Recovering the board 50 2.4.5 Configuring and Building Source Code 56 2.4.6 Board Component Descriptions 56 3 Das U-boot 62 3.1 Ethernet Driver in U-Boot on SC5xx-EZKIT 62 3.1.1 Overview 62 3.1.2 Hardware Setup 62 3.1.3 Build U-Boot with emac0 or emac1 62 3.1.4 Using EMAC Driver 62 3.2 Creating and Booting Linux Using the New U-Boot "fitImage" 64 3.2.1 Introduction 64 3.2.2 Hardware Setup 64 3.2.3 Builroot and kernel
    [Show full text]