DOCSLIB.ORG

Forensics Book 2: Investigating Hard Disk and File and Operating Systems

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Forensics Book 2: Investigating Hard Disk and File and Operating Systems Chapter 3: Windows, Linux, and Macintosh Boot Processes Objectives (Hedefler/Amaçlar) Understand boot loaders (önyükleyici) Understand boot sectors (önyükleme sektörü) Describe the basic system boot process (önyükleme işlemi) Explain the MS-DOS boot process Explain the Windows XP boot process Copyright © by EC-Council Press All rights reserved. Reproduction is strictly prohibited Objectives (continued) Explain the Linux boot process Explain the Mac OS X boot process Copyright © by EC-Council Press All rights reserved. Reproduction is strictly prohibited Introduction to Windows, Linux, and Macintosh Boot Processes This chapter: Focuses on the boot processes for the major operating systems available today Booting (Önyükleme, Başlatma), also called bootstrapping (Önyükleme, Başlatma) Process of loading an operating system into a computer’s main memory This step takes place during the boot sequence (önyükleme sırası) Set of steps a computer system takes after it has been powered on Copyright © by EC-Council Press All rights reserved. Reproduction is strictly prohibited Boot Loader (önyükleyici) Boot loader or boot manager (önyükleme yöneticisi) Program that loads the operating system into a computer’s memory when the system is booted Multiple-stage boot loaders are common A number of small programs call each other, and the last program loads the operating system Copyright © by EC-Council Press All rights reserved. Reproduction is strictly prohibited Boot Sector (önyükleme sektörü) Boot sector Memory sector of a hard disk, floppy disk, or similar data storage device that contains code for bootstrapping systems Always the first sector on the first track Each valid boot sector has two bytes (0x55AA), called a boot sector signature, at the end of the sector 0x55AA - önyükleme sektörü imzası Copyright © by EC-Council Press All rights reserved. Reproduction is strictly prohibited Boot Sector (continued) Figure 3-1 This shows a boot sector, including the boot sector signature. Copyright © by EC-Council Press All rights reserved. Reproduction is strictly prohibited Boot Sector (continued) Two major kinds of boot sectors: Volume boot record (disk bölümü önyükleme kaydı) Master boot record (Ana önyükleme kaydı) A master boot record contains the following structures: Master partition table (Ana bölüm tablosu) Master boot code (Ana önyükleme kodu) BIOS (Basic Input-Output System) (Temel Giriş-Çıkış Sistemi) Program a personal computer’s microprocessor uses to get the computer system started after a user turns it on EPROM adı verilen bir yonga üzerinde ROM Bellek (Read Only Memory, tr: Salt Okunur Bellek) biçiminde yer alan bir tür yazılımdır. Copyright © by EC-Council Press All rights reserved. Reproduction is strictly prohibited Boot Sector (continued) Figure 3-2 This shows the code for a master boot record. Copyright © by EC-Council Press All rights reserved. Reproduction is strictly prohibited Boot Sector (continued) CHS - Cylinder-head-sector LBA - Logical block addressing Figure 3-3 This shows the structure of a master boot record. Copyright © by EC-Council Press All rights reserved. Reproduction is strictly prohibited Basic System Boot Process Steps: 1. The system clock generates a series of clock ticks, which initializes the CPU (Central Processing Unit) 2. The CPU looks to the system’s startup program in the ROM BIOS for its first instruction 3. The first instruction is to run the power-on self-test (POST), in a predetermined memory address 4. POST checks the BIOS chip and then tests CMOS RAM (Random access memory yani Rastgele Erişilebilir Bellek) CMOS (complementary metal-oxide semiconductor) memory holds the system date, time, and setup parameters Copyright © by EC-Council Press All rights reserved. Reproduction is strictly prohibited Basic System Boot Process (continued) Steps: (continued) 5. If there is no battery failure, POST checks the inventoried hardware devices to check whether they are functioning properly 6. CPU initialization is completed if everything is fine 7. The BIOS looks into the CMOS chip to find the drive where the OS is installed The BIOS then checks the boot record of the drive to find the beginning of the OS and the subsequent program file that initializes the OS The BIOS copies its files into memory after OS initialization Copyright © by EC-Council Press All rights reserved. Reproduction is strictly prohibited Basic System Boot Process (continued) Steps: (continued) 8. The OS takes over control of the boot process 9. The OS performs another inventory of the system’s memory and memory availability and loads the device drivers that it needs to control the peripheral devices Copyright © by EC-Council Press All rights reserved. Reproduction is strictly prohibited MS-DOS Boot Process Steps: The BIOS initiates power-on self-test (POST) POST performs the following actions: Initializes the keyboard and other system hardware, such as the video card Tests the computer’s RAM Checks the disk drives Attempts to find a valid operating system The BIOS searches for the file IO.SYS in the root directory and loads it into RAM IO.SYS provides services for peripherals such as printers, modems, and disk drives Copyright © by EC-Council Press All rights reserved. Reproduction is strictly prohibited MS-DOS Boot Process (continued) Steps: (continued) IO.SYS loads a file called MSDOS.SYS, which is an extension of ROM or the BIOS MSDOS.SYS acts as a gateway for communication between DOS and the BIOS MSDOS.SYS loads the CONFIG.SYS file CONFIG.SYS stores system configurations CONFIG.SYS is processed and executed MSDOS.SYS loads the COMMAND.COM program file into memory COMMAND.COM loads an optional file called AUTOEXEC.BAT and executes it Copyright © by EC-Council Press All rights reserved. Reproduction is strictly prohibited Windows XP Boot Process Steps: The power supply performs a self-test and sends the power good signal to the processor The timer chip stops sending reset signals to the processor, allowing the CPU to begin operations The CPU loads the ROM BIOS starting at ROM memory address FFFF:0000 The ROM BIOS contains a JMP (jump) instruction that points to the actual address of the ROM BIOS code The ROM BIOS performs a basic test of central hardware to verify basic functionality Copyright © by EC-Council Press All rights reserved. Reproduction is strictly prohibited Windows XP Boot Process (continued) Steps: (continued) The BIOS searches for adapters that may need to load their own ROM BIOS routines Startup BIOS routines scan memory addresses C000:0000 through C780:0000 to find video ROM The ROM BIOS checks to see if this is a cold boot (the startup of a system from a powered-down state) or a warm boot (the restart of a system that is already on) If this is a cold boot, the ROM BIOS executes a full POST (power-on self-test) If this is a warm boot, the memory test portion of the POST is switched off Copyright © by EC-Council Press All rights reserved. Reproduction is strictly prohibited Windows XP Boot Process (continued) Steps: (continued) POST can be broken down into two components: A video test initializes the video adapter A video adapter tests the video card and video memory and displays configuration information or any errors The BIOS locates and reads the configuration information stored in CMOS The BIOS examines the disk for a master boot record (MBR) With a valid MBR loaded into memory, the BIOS transfers control of the boot process to the partition loader code Copyright © by EC-Council Press All rights reserved. Reproduction is strictly prohibited Windows XP Boot Process (continued) Steps: (continued) The partition loader, or boot loader, examines the partition table for a partition marked as active The partition loader then searches the very first sector of that partition for a boot record. The active partition’s boot record is checked for a valid boot signature and, if found, the boot sector code is executed as a program Copyright © by EC-Council Press All rights reserved. Reproduction is strictly prohibited Windows XP Boot Process (continued) Steps: (continued) NTLDR, a hidden system file in the root directory of the system partition, controls loading of Windows XP in four stages: Initial boot loader phase Operating system selection Hardware detection Configuration selection NTOSKRNL goes through two phases in its boot process I/O Manager starts loading all the system driver files Win32k.sys switches the screen into graphics mode Copyright © by EC-Council Press All rights reserved. Reproduction is strictly prohibited Windows XP Boot Process (continued) Steps: (continued) The services subsystem starts all services marked as Auto Start Once all devices and services are started, the boot is deemed successful, and this configuration is saved as the last known good configuration The WINLOGON.EXE file starts the logon process This is a login manager file that is responsible for all login and logout procedures The Local Security Authority (LSASS.EXE) process displays the logon dialog box Copyright © by EC-Council Press All rights reserved. Reproduction is strictly prohibited FTK Imager (continued) Figure 3-5 This is the logon dialog box for Windows XP Professional. Copyright © by EC-Council Press All rights reserved. Reproduction is strictly prohibited Linux Boot Process The Linux boot process comprises five major steps: Step 1, boot manager: responsible for starting
Recommended publications
  • Design and Evaluation of Self-Management Approaches for Virtual Machine-Based Environments

    Design and Evaluation of Self-Management Approaches for Virtual Machine-Based Environments

    Fachhochschule Wiesbaden Fachbereich Design Informatik Medien Studiengang Informatik Master-Thesis zur Erlangung des akademischen Grades Master of Science – M.Sc. Design and Evaluation of Self-Management Approaches for Virtual Machine-Based Environments vorgelegt von Dan Marinescu am 29. Februar 2008 Referent: Prof. Dr. Reinhold Kröger Korreferent: Prof. Dr. Steffen Reith II Erklärung gem. BBPO, Ziff. 6.4.2 Ich versichere, dass ich die Master-Thesis selbstständig verfasst und keine anderen als die angegebenen Hilfsmittel benutzt habe. Wiesbaden, 29.02.2008 Dan Marinescu Hiermit erkläre ich mein Einverständnis mit den im Folgenden aufgeführten Verbreitungs- formen dieser Master-Thesis: Verbreitungsform ja nein Einstellung der Arbeit in die √ Bibliothek der FHW Veröffentlichung des Titels der √ Arbeit im Internet Veröffentlichung der Arbeit im √ Internet Wiesbaden, 29.02.2008 Dan Marinescu III IV Contents 1 Introduction 1 2 Background 5 2.1 Virtualization ................................ 5 2.1.1 Taxonomy ............................. 5 2.1.2 Case Study: Xen .......................... 10 2.1.3 Live Migration ........................... 13 2.1.4 Hardware-Assisted Virtualization ................. 16 2.1.5 Management of Vitual Machine Environments .......... 17 2.2 Service Level Management ......................... 20 2.3 Autonomic Computing ........................... 21 2.3.1 Motivation ............................. 21 2.3.2 Taxonomy ............................. 22 2.3.3 Architectural Considerations .................... 23 2.3.4 Examples of Autonomic Computing Systems ........... 24 2.4 Complexity theory and Optimization .................... 25 2.4.1 Introduction to Complexity Theory ................ 25 2.4.2 Complexity Classes ......................... 25 2.4.3 Optimization Problems ....................... 26 2.4.4 The Knapsack Family of Problems ................. 27 2.4.5 Approximation Algorithms ..................... 29 2.4.6 Heuristics .............................. 32 V 3 Analysis 37 3.1 State of the Art ..............................
  • Virtual Square: All the Virtuality You Always Wanted but You Were Afraid to Ask

    Virtual Square: All the Virtuality You Always Wanted but You Were Afraid to Ask

    Virtual Square: all the virtuality you always wanted but you were afraid to ask. Renzo Davoli i Computer Science Department vol Da ALMA MATER STUDIORUM: University of Bologna o Renz eft, yl WorkShop 2007 sul Calcolo e Reti dell'INFN op C 7 Rimini, 10 maggio 2007 00 2 © re ua Sq l ua t Vir Virtual Square VIRTUAL VIRTUAL VIRTUAL SQUARED i VIRTUAL SQUARE vol Da o VIRTUAL VIRTUAL Renz eft, VIRTUAL yl VIRTUAL op C 7 00 2 VIRTUAL © re VIRTUAL ua Sq l ua t Vir VIRTUALITY today ● Virtual Machines – historical topic – lots of papers – lots of tools i vol Da – ... but something is already missing o Renz ● Virtual Networking eft, yl op – less historical C 7 00 2 – several papers © re ua Sq l ua t Vir Virtual Square Virtualization concepts and tools are disconnected. i There is a world of new applications that vol Da can be realized by interoperating, o Renz integrated virtuality eft, yl op C 7 UNIFICATION IS NEEDED 00 2 © re ua Sq l ua t Vir Virtual Square © 2007 Copyleft, Renzo Davoli Vi rtual S qu are Some Examples of VM (free software) ● Qemu: PVM or SVM, User Mode User Access (or dual-mode with KQEMU, proprietary sw). – cross emulation platform (ia32, ia64, ppc, i m68k, sparc, arm...) vol Da o – dynamic translation Renz ● eft, XEN: SVM, Native. yl op C 7 – xen uses para-virtualization (O.S. in domain0 00 2 © has the real device drivers). re ua – (xen ideas come from the Denali project: Sq l ua t SVN, Native, real virtualization).
  • Operating System Boot from Fully Encrypted Device

    Operating System Boot from Fully Encrypted Device

    MASARYK UNIVERSITY FACULTY OF INFORMATICS Operating system boot from fully encrypted device BACHELOR'S THESIS Daniel Chromik Brno, Fall 2016 Replace this page with a copy of the official signed thesis assignment and the copy of the Statement of an Author. Declaration Hereby I declare that this paper is my original authorial work, which I have worked out by my own. All sources, references and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Daniel Chromik Advisor: ing. Milan Brož i Acknowledgement I would like to thank my advisor, Ing. Milan Brož, for his guidance and his patience of a saint. Another round of thanks I would like to send towards my family and friends for their support. ii Abstract The goal of this work is description of existing solutions for boot• ing Linux and Windows from fully encrypted devices with Secure Boot. Before that, though, early boot process and bootloaders are de• scribed. A simple Linux distribution is then set up to boot from a fully encrypted device. And lastly, existing Windows encryption solutions are described. iii Keywords boot process, Linux, Windows, disk encryption, GRUB 2, LUKS iv Contents 1 Introduction 1 1.1 Thesis goals 1 1.2 Thesis structure 2 2 Boot Process Description 3 2.1 Early Boot Process 3 2.2 Firmware interfaces 4 2.2.1 BIOS - Basic Input/Output System 4 2.2.2 UEFI - Unified Extended Firmware Interface . 5 2.3 Partitioning tables 5 2.3.1 MBR - Master Boot Record 5 2.3.2 GPT - GUID Partition Table 7 2.4
  • Partition Wizard About Minitool Partition Wizard Minitool Partition Wizard Is an Easy-To-Use Partitioning Software with High Security and Efficiency

    Partition Wizard About Minitool Partition Wizard Minitool Partition Wizard Is an Easy-To-Use Partitioning Software with High Security and Efficiency

    MiniTool Partition Wizard About MiniTool Partition Wizard MiniTool Partition Wizard is an easy-to-use partitioning software with high security and efficiency. Due of its simple user interface, you can create, delete, format, move, and resize partitions with ease. What’s more, your data will always be protected when using MiniTool Partition Wizard to move and resize partitions. Main Functions of MiniTool Partition Wizard: Resize/ Move partitions Merge Partitions Create partitions Delete partitions Change Partition Label Delete all partitions Format partitions Change Cluster Size Convert file system Convert FAT to NTFS Convert NTFS to FAT Explore Partition Check Partitions Recovery Partition Wipe disk Wipe partition Copy partition Copy disks Initialize to MBR disk Initialize to GPT disk Align All Partitions Align Partition Convert MBR Disk to GPT Disk Convert GPT Disk to MBR Disk Dynamic Disk Create volume Delete Volume Format Volume Move/Resize Volume Wipe Volume Explore Volume Check File System Change Volume Label Change Volume Letter Change Volume Cluster Size Volume Properties MiniTool Partition Wizard Staring MiniTool Partition Wizard You can start MiniTool Partition Wizard from the Start menu in Windows Click Start menu > All Programs > MiniTool Partition Wizard xxx Edition > MiniTool Partition Wizard xxx Edition Xxx is your present edition of MiniTool Partition Wizard, Such as Home, Professional, Server, and Enterprise MiniTool Partition Wizard Hardware Requirements Minimum Hardware requirements: 500 MHz x86 or compatible CPU. 256mb RAM memory. Mouse and Keyboard. Recommended Hardware requirements: 1 GHz x86 or compatible CPU. 512mb RAM memory. Mouse and Keyboard. MiniTool Partition Wizard System Requirements Note: you should have access to administration while using Partition Wizard.
  • Computer Hardware

    Computer Hardware

    Chapter Computer Hardware ENCE EXAM TOPICS COVERED IN 1 THIS CHAPTER: ✓ Computer hardware components ✓ The boot process ✓ Partitions ✓ File systems COPYRIGHTED MATERIAL Computer forensics examiners deal most often with the media on which evidentiary data is stored. This includes, but is not lim- ited to, hard drives, CDs, DVDs, fl ash memory devices, smart phones, tablets, and even legacy fl oppies and tapes. Although these devices might be the bane of the examiner’s existence, media devices don’t exist in a void, and knowledge of a computer’s various components and functions is a must for the competent examiner. As an examiner, you may be called upon to explain how a computer functions to a jury. Doing so requires you know a computer’s function from a technical standpoint and that you can translate those technical concepts into real-world, easy-to-understand terms. As an examiner, you may also be subjected to a voir dire examination by opposing coun- sel to challenge your competence to testify. Acronyms are hardly in short supply in the fi eld of computing—some well-known and meaningful, others more obscure. Imagine being asked during such an examination to explain several of the common acronyms used with computers, such as RAM, CMOS, SCSI, BIOS, and POST. If you were to draw a blank on some obscure or even common acronym, picture its impact on your credibility. Some acronyms are difficult to remember because their meaning is often obscure or meaningless. A good example is TWAIN, which stands for T ech- nology W ithout a n I nteresting N ame.
  • Chapter 1. Origins of Mac OS X

    Chapter 1. Origins of Mac OS X

    1 Chapter 1. Origins of Mac OS X "Most ideas come from previous ideas." Alan Curtis Kay The Mac OS X operating system represents a rather successful coming together of paradigms, ideologies, and technologies that have often resisted each other in the past. A good example is the cordial relationship that exists between the command-line and graphical interfaces in Mac OS X. The system is a result of the trials and tribulations of Apple and NeXT, as well as their user and developer communities. Mac OS X exemplifies how a capable system can result from the direct or indirect efforts of corporations, academic and research communities, the Open Source and Free Software movements, and, of course, individuals. Apple has been around since 1976, and many accounts of its history have been told. If the story of Apple as a company is fascinating, so is the technical history of Apple's operating systems. In this chapter,[1] we will trace the history of Mac OS X, discussing several technologies whose confluence eventually led to the modern-day Apple operating system. [1] This book's accompanying web site (www.osxbook.com) provides a more detailed technical history of all of Apple's operating systems. 1 2 2 1 1.1. Apple's Quest for the[2] Operating System [2] Whereas the word "the" is used here to designate prominence and desirability, it is an interesting coincidence that "THE" was the name of a multiprogramming system described by Edsger W. Dijkstra in a 1968 paper. It was March 1988. The Macintosh had been around for four years.
  • Carbon Copy Cloner Documentation: English

    Carbon Copy Cloner Documentation: English

    Carbon Copy Cloner Documentation: English Getting started with CCC System Requirements, Installing, Updating, and Uninstalling CCC CCC License, Registration, and Trial FAQs Trouble Applying Your Registration Information? Establishing an initial backup Preparing your backup disk for a backup of Mac OS X Restoring data from your backup What's new in CCC Features of CCC specific to Lion and greater Release History Carbon Copy Cloner's Transition to a Commercial Product: Frequently Asked Questions Credits Example backup scenarios I want to clone my entire hard drive to a new hard drive or a new machine I want to backup my important data to another Macintosh on my network I want to backup multiple machines or hard drives to the same hard drive I want my backup task to run automatically on a scheduled basis Backing up to/from network volumes and other non-HFS volumes I want to back up my whole Mac to a Time Capsule or other network volume I want to defragment my hard drive Backup and archiving settings Excluding files and folders from a backup task Protecting data that is already on your destination volume Managing previous versions of your files Automated maintenance of CCC archives Advanced Settings Some files and folders are automatically excluded from a backup task The Block-Level Copy Scheduling Backup Tasks Scheduling a task and basic settings Performing actions Before and After the backup task Deferring and skipping scheduled tasks Frequently asked questions about scheduled tasks Email and Growl notifications Backing Up to Disk Images
  • Wikipedia: Design of the FAT File System

    Wikipedia: Design of the FAT File System

    Design of the FAT file system A FAT file system is a specific type of computer file system architecture and FAT a family of industry-standard file systems utilizing it. Developer(s) Microsoft, SCP, IBM, [3] The FAT file system is a legacy file system which is simple and robust. It Compaq, Digital offers good performance even in very light-weight implementations, but Research, Novell, cannot deliver the same performance, reliability and scalability as some Caldera modern file systems. It is, however, supported for compatibility reasons by Full name File Allocation Table: nearly all currently developed operating systems for personal computers and FAT12 (12- many home computers, mobile devices and embedded systems, and thus is a bit version), well suited format for data exchange between computers and devices of almost FAT16 (16- any type and age from 1981 through the present. bit versions), Originally designed in 1977 for use on floppy disks, FAT was soon adapted and FAT32 (32-bit version used almost universally on hard disks throughout the DOS and Windows 9x with 28 bits used), eras for two decades. Today, FAT file systems are still commonly found on exFAT (64- floppy disks, USB sticks, flash and other solid-state memory cards and bit versions) modules, and many portable and embedded devices. DCF implements FAT as Introduced 1977 (Standalone the standard file system for digital cameras since 1998.[4] FAT is also utilized Disk BASIC-80) for the EFI system partition (partition type 0xEF) in the boot stage of EFI- FAT12: August 1980 compliant computers. (SCP QDOS) FAT16: August 1984 For floppy disks, FAT has been standardized as ECMA-107[5] and (IBM PC DOS 3.0) ISO/IEC 9293:1994[6] (superseding ISO 9293:1987[7]).
  • Mac OS X Intro for UNIX Users

    Mac OS X Intro for UNIX Users

    Mac OS X An Introduction for UNIX Users Leon Towns-von Stauber, Occam's Razor Seattle BSD Users Group, October 2004 http://www.occam.com/osx/ X Contents Opening Remarks.............................3 Where Did Mac OS X Come From?.....5 What is Mac OS X?..........................13 A New Kind of UNIX........................25 A Different Kind of UNIX.................28 Why Use Mac OS X?.........................60 Resources.......................................63 Closing Remarks.............................67 X Opening Remarks 3 This is a technical introduction to Mac OS X, mainly targeted to experienced UNIX users for whom OS X is at least relatively new Some emphasis on comparisons with FreeBSD I'm assuming basic familiarity with operating system design Where I'm coming from: UNIX user and some-time admin since 1990 Full-time UNIX admin since 1995 NeXTstep user and admin since 1991 This presentation covers primarily Mac OS X 10.3.5 (Darwin 7.5) X Legal Notices 4 This presentation Copyright © 2003-2004 Leon Towns-von Stauber. All rights reserved. Trademark notices Apple®, Mac®, Macintosh®, Mac OS®, Aqua®, Finder™, Quartz™, Cocoa®, Carbon®, AppleScript®, Rendezvous™, Panther™, and other terms are trademarks of Apple Computer. See <http:// www.apple.com/legal/appletmlist.html>. NeXT®, NeXTstep®, OpenStep®, and NetInfo® are trademarks of NeXT Software. See <http://www.apple.com/legal/nexttmlist.html>. PowerPC™ is a trademark of International Business Machines. Java™ is a trademark of Sun Microsystems. Other trademarks are the property of their
  • Virtualization Technologies Overview Course: CS 490 by Mendel

    Virtualization Technologies Overview Course: CS 490 by Mendel

    Virtualization technologies overview Course: CS 490 by Mendel Rosenblum Name Can boot USB GUI Live 3D Snaps Live an OS on mem acceleration hot of migration another ory runnin disk alloc g partition ation system as guest Bochs partially partially Yes No Container s Cooperati Yes[1] Yes No No ve Linux (supporte d through X11 over networkin g) Denali DOSBox Partial (the Yes No No host OS can provide DOSBox services with USB devices) DOSEMU No No No FreeVPS GXemul No No Hercules Hyper-V iCore Yes Yes No Yes No Virtual Accounts Imperas Yes Yes Yes Yes OVP (Eclipse) Tools Integrity Yes No Yes Yes No Yes (HP-UX Virtual (Integrity guests only, Machines Virtual Linux and Machine Windows 2K3 Manager in near future) (add-on) Jail No Yes partially Yes No No No KVM Yes [3] Yes Yes [4] Yes Supported Yes [5] with VMGL [6] Linux- VServer LynxSec ure Mac-on- Yes Yes No No Linux Mac-on- No No Mac OpenVZ Yes Yes Yes Yes No Yes (using Xvnc and/or XDMCP) Oracle Yes Yes Yes Yes Yes VM (manage d by Oracle VM Manager) OVPsim Yes Yes Yes Yes (Eclipse) Padded Yes Yes Yes Cell for x86 (Green Hills Software) Padded Yes Yes Yes No Cell for PowerPC (Green Hills Software) Parallels Yes, if Boot Yes Yes Yes DirectX 9 Desktop Camp is and for Mac installed OpenGL 2.0 Parallels No Yes Yes No partially Workstati on PearPC POWER Yes Yes No Yes No Yes (on Hypervis POWER 6- or (PHYP) based systems, requires PowerVM Enterprise Licensing) QEMU Yes Yes Yes [4] Some code Yes done [7]; Also supported with VMGL [6] QEMU w/ Yes Yes Yes Some code Yes kqemu done [7]; Also module supported
  • Vmware Et Sécurité

    Vmware Et Sécurité

    HERVÉ SCHAUER CONSULTANTS Cabinet de Consultants en Sécurité Informatique depuis 1989 Spécialisé sur Unix, Windows, TCP/IP et Internet OSSIROSSIR GroupeGroupe SURSUR 88 juilletjuillet 20082008 VMwareVMware etet sécuritésécurité JulienJulien RaeisRaeis <[email protected]> NicolasNicolas CollignonCollignon <[email protected]> AgendaAgenda Rappels sur la virtualisation Mesures de sécurité intégrées à VMware Virtualisation et DMZ Revue des vulnérabilités Retour d'expérience HSC 2/64 Copyright Hervé Schauer Consultants 2008 - Reproduction Interdite Rappels sur la virtualisation 3/64 Copyright Hervé Schauer Consultants 2008 - Reproduction Interdite DéfinitionsDéfinitions « Virtuel : Se dit des éléments (terminaux, mémoire...) d'un système informatique considérés comme ayant des propriétés différentes de leurs caractéristiques physiques » - Grand Dictionnaire Encyclopédique Larousse « Virtualisation : abstraction des ressources d'un système informatique. » 4/64 Copyright Hervé Schauer Consultants 2008 - Reproduction Interdite HistoriqueHistorique Concept introduit dans les années 60 But : partitionner les ressources des coûteux mainframes de l'époque IBM M44/44X, naissance du terme « pseudo-machine » Première implémentation de machines virtuelles IBM CP-40 Système tournant sur S/360-40 Perte d'intérêt dans les années 80 Déport des applications sur des clients et serveurs x86 Architecture « bon marché » Mais coûts d'infrastructure physique élevés, manque de protection en cas de panne, maintenance des postes de travail coûteuse, etc.
  • Comparison of Platform Virtual Machines - Wikipedia

    Comparison of Platform Virtual Machines - Wikipedia

    Comparison of platform virtual machines - Wikipedia... http://en.wikipedia.org/wiki/Comparison_of_platform... Comparison of platform virtual machines From Wikipedia, the free encyclopedia The table below compares basic information about platform virtual machine (VM) packages. Contents 1 General Information 2 More details 3 Features 4 Other emulators 5 See also 6 References 7 External links General Information Name Creator Host CPU Guest CPU Bochs Kevin Lawton any x86, AMD64 CHARON-AXP Stromasys x86 (64 bit) DEC Alphaserver CHARON-VAX Stromasys x86, IA-64 VAX x86, x86-64, SPARC (portable: Contai ners (al so 'Zones') Sun Microsystems (Same as host) not tied to hardware) Dan Aloni helped by other Cooperati ve Li nux x86[1] (Same as parent) developers (1) Denal i University of Washington x86 x86 Peter Veenstra and Sjoerd with DOSBox any x86 community help DOSEMU Community Project x86, AMD64 x86 1 of 15 10/26/2009 12:50 PM Comparison of platform virtual machines - Wikipedia... http://en.wikipedia.org/wiki/Comparison_of_platform... FreeVPS PSoft (http://www.FreeVPS.com) x86, AMD64 compatible ARM, MIPS, M88K GXemul Anders Gavare any PowerPC, SuperH Written by Roger Bowler, Hercul es currently maintained by Jay any z/Architecture Maynard x64 + hardware-assisted Hyper-V Microsoft virtualization (Intel VT or x64,x86 AMD-V) OR1K, MIPS32, ARC600/ARC700, A (can use all OVP OVP Imperas [1] [2] Imperas OVP Tool s x86 (http://www.imperas.com) (http://www.ovpworld compliant models, u can write own to pu OVP APIs) i Core Vi rtual Accounts iCore Software