Comparative Analysis of Operating System of Different Smart Phones
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Symbian OS As a Research Platform – Present and Future
Symbian OS as a Research Platform Present and Future Lawrence Simpson Research Department Symbian Copyright © 2008 Symbian Software Ltd. Symbian Platform Symbian OS is a separate platform, specifically designed for mobile & convergent devices. Not an adaptation of Unix or Windows or .... Symbian OS has facilities to support • Small (memory) footprint • Low power consumption • High reliability • “Always on”, but must deal with unplanned shutdown • Diverse range of hardware • Diverse manufacturers – multiple UIs and multiple brands Different UIs on the same underlying system Series 60 (S60) • Provided by Nokia. • Used by Nokia & S60 licensees. • Originally a keypad-based UI ... now supporting touch-screen variants. UIQ • Provided by UIQ – company has sometimes been owned by Symbian, sometimes by Sony Ericsson/Motorola. • Used by Sony Ericsson & Motorola. • Originally mainly a touch-screen UI ... now supporting keypad-only variants. MOAP(S) • Provided through NTT DOCOMO. • Used by several Symbian licensees in Japan. Software in a Symbian Phone – “Habitats of the Symbian Eco-System” User-Installed Applications “In-the-box” Applications (commissioned/written by the phone-maker, built into the phone ROM) User Interface (S60 or UIQ or MOAP) Symbian OS Hardware Adaptation Software (usually from chip-vendors or 3rd parties) Symbian OS component level view developer.symbian.com/main/documentation/technologies/system_models OS designed for Smartphones & Media Phones Core OS Technologies Other Smartphone Technologies • Telephony Services • PIM (calendars, agenda, etc.) • Shortlink (BT, USB) Services • Messaging • Networking (IP) Services • Remote Management • Multimedia (audio & video) • Java / J2ME • Graphics • Security Management • Location-Based Services (LBS) • Multimedia Middleware • Base Services: (Database Utilities, • Application Protocols Localisation, etc.) • GUI Framework • Kernel Symbian programming paradigms • Several paradigms to support mobility, reliability, security, including.. -
Cygwin User's Guide
Cygwin User’s Guide Cygwin User’s Guide ii Copyright © Cygwin authors Permission is granted to make and distribute verbatim copies of this documentation provided the copyright notice and this per- mission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this documentation under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this documentation into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation. Cygwin User’s Guide iii Contents 1 Cygwin Overview 1 1.1 What is it? . .1 1.2 Quick Start Guide for those more experienced with Windows . .1 1.3 Quick Start Guide for those more experienced with UNIX . .1 1.4 Are the Cygwin tools free software? . .2 1.5 A brief history of the Cygwin project . .2 1.6 Highlights of Cygwin Functionality . .3 1.6.1 Introduction . .3 1.6.2 Permissions and Security . .3 1.6.3 File Access . .3 1.6.4 Text Mode vs. Binary Mode . .4 1.6.5 ANSI C Library . .4 1.6.6 Process Creation . .5 1.6.6.1 Problems with process creation . .5 1.6.7 Signals . .6 1.6.8 Sockets . .6 1.6.9 Select . .7 1.7 What’s new and what changed in Cygwin . .7 1.7.1 What’s new and what changed in 3.2 . -
Cygwin User's Guide
Cygwin User’s Guide i Cygwin User’s Guide Cygwin User’s Guide ii Copyright © 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012 Red Hat, Inc. Permission is granted to make and distribute verbatim copies of this documentation provided the copyright notice and this per- mission notice are preserved on all copies. Permission is granted to copy and distribute modified versions of this documentation under the conditions for verbatim copying, provided that the entire resulting derived work is distributed under the terms of a permission notice identical to this one. Permission is granted to copy and distribute translations of this documentation into another language, under the above conditions for modified versions, except that this permission notice may be stated in a translation approved by the Free Software Foundation. Cygwin User’s Guide iii Contents 1 Cygwin Overview 1 1.1 What is it? . .1 1.2 Quick Start Guide for those more experienced with Windows . .1 1.3 Quick Start Guide for those more experienced with UNIX . .1 1.4 Are the Cygwin tools free software? . .2 1.5 A brief history of the Cygwin project . .2 1.6 Highlights of Cygwin Functionality . .3 1.6.1 Introduction . .3 1.6.2 Permissions and Security . .3 1.6.3 File Access . .3 1.6.4 Text Mode vs. Binary Mode . .4 1.6.5 ANSI C Library . .5 1.6.6 Process Creation . .5 1.6.6.1 Problems with process creation . .5 1.6.7 Signals . .6 1.6.8 Sockets . .6 1.6.9 Select . -
An Encrypted Payload Protocol and Target-Side Scripting Engine
An Encrypted Payload Protocol and Target-Side Scripting Engine Dino A. Dai Zovi [email protected] Abstract into the remote process and then triggering the vulnera- Modern exploit payloads in commercial and open-source bility (the injection vector) in order to cause the remote penetration testing frameworks have grown much more process to execute the injected code (the payload). Tra- advanced than the traditional shellcode they replaced. ditionally, these payloads have been written in processor- These payloads permit interactive access without launch- specific assembly language, assembled, and extracted by ing a shell, network proxying, and many other rich fea- hand into reusable machine code components. These tures. Available payload frameworks have several lim- payloads were typically small and executed an operating itations, however. They make little use of encryption to system shell, causing them to be commonly referred to secure delivery and communications, especially in earlier as shellcode. Common shellcode variants included func- stage payloads. In addition, their richer features require tionality such as restoring dropped privileges, breaking a constant network connection to the penetration tester, out of chroot environments, and attaching the shell to making them unsuitable against mobile clients, such as an inbound or outbound network connection. This style laptops, PDAs, and smart phones. of payload construction was both labor and skill inten- This work introduces a first-stage exploit payload that sive. is able to securely establish an encrypted channel using With the growth of commercial penetration testing ElGamal key agreement and the RC4 stream cipher. The services and especially commercial penetration test- key agreement implementation requires only modular ing products, exploit payloads have gotten considerably exponentiation and RC4 also lends itself to an implemen- more capable and complex. -
The Symbian OS Architecture Sourcebook
The Symbian OS Architecture Sourcebook The Symbian OS Architecture Sourcebook Design and Evolution of a Mobile Phone OS By Ben Morris Reviewed by Chris Davies, Warren Day, Martin de Jode, Roy Hayun, Simon Higginson, Mark Jacobs, Andrew Langstaff, David Mery, Matthew O’Donnell, Kal Patel, Dominic Pinkman, Alan Robinson, Matthew Reynolds, Mark Shackman, Jo Stichbury, Jan van Bergen Symbian Press Head of Symbian Press Freddie Gjertsen Managing Editor Satu McNabb Copyright 2007 Symbian Software, Ltd John Wiley & Sons, Ltd The Atrium, Southern Gate, Chichester, West Sussex PO19 8SQ, England Telephone (+44) 1243 779777 Email (for orders and customer service enquiries): [email protected] Visit our Home Page on www.wileyeurope.com or www.wiley.com All Rights Reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except under the terms of the Copyright, Designs and Patents Act 1988 or under the terms of a licence issued by the Copyright Licensing Agency Ltd, 90 Tottenham Court Road, London W1T 4LP, UK, without the permission in writing of the Publisher. Requests to the Publisher should be addressed to the Permissions Department, John Wiley & Sons Ltd, The Atrium, Southern Gate, Chichester, West Sussex PO19 8SQ, England, or emailed to [email protected], or faxed to (+44) 1243 770620. Designations used by companies to distinguish their products are often claimed as trademarks. All brand names and product names used in this book are trade names, service marks, trademarks or registered trademarks of their respective owners. -
The Fileless Attack SURVIVAL GUIDE
The Fileless Attack SURVIVAL GUIDE Protect Your Company from Attacks Antivirus Can’t Block THE FILELESS ATTACK SURVIVAL GUIDE 1 Table of Contents 3 Executive Summary 5 Introduction 8 Types of fileless attack techniques 10 How attackers use them to… 11 ......Gain initial access 13 ......Escalate privileges 15 ......Execute payloads 17 ......Gain persistence 19 ......Achieve lateral movement 21 Practical tips for preventing and mitigating fileless attacks 22 Fileless Attack Checklist THE FILELESS ATTACK SURVIVAL GUIDE 2 Executive Summary Attacks are constantly evolving. One of the most damaging trends we’ve seen of late is the increasingly widespread adoption of fileless attack techniques. These techniques are designed to silently infect target systems without ever downloading malicious programs or leaving behind any obvious trace, primarily by using a victim company’s trusted software and system tools against it. To clarify what actually constitutes a fileless attack and explain how it can work, here are three things every business leader should know: 1 Fileless attacks exploit a fundamental gap in traditional endpoint security Traditionally, attacks involving malware have revolved around attackers gaining access to a victim’s computer (typically by either exploiting a software vulnerability or tricking the victim into downloading something he or she shouldn’t), and then installing an executable file (the “payload”) that does the damage. The problem with this approach from an attacker’s perspective is that antivirus solutions are built to scan and block any suspicious files that land on the computer. By not installing malicious files, however, attackers can simply bypass these solutions. All they need to do is hijack otherwise legitimate system tools and processes to do their dirty work for them. -
Abkürzungs-Liste ABKLEX
Abkürzungs-Liste ABKLEX (Informatik, Telekommunikation) W. Alex 1. Juli 2021 Karlsruhe Copyright W. Alex, Karlsruhe, 1994 – 2018. Die Liste darf unentgeltlich benutzt und weitergegeben werden. The list may be used or copied free of any charge. Original Point of Distribution: http://www.abklex.de/abklex/ An authorized Czechian version is published on: http://www.sochorek.cz/archiv/slovniky/abklex.htm Author’s Email address: [email protected] 2 Kapitel 1 Abkürzungen Gehen wir von 30 Zeichen aus, aus denen Abkürzungen gebildet werden, und nehmen wir eine größte Länge von 5 Zeichen an, so lassen sich 25.137.930 verschiedene Abkür- zungen bilden (Kombinationen mit Wiederholung und Berücksichtigung der Reihenfol- ge). Es folgt eine Auswahl von rund 16000 Abkürzungen aus den Bereichen Informatik und Telekommunikation. Die Abkürzungen werden hier durchgehend groß geschrieben, Akzente, Bindestriche und dergleichen wurden weggelassen. Einige Abkürzungen sind geschützte Namen; diese sind nicht gekennzeichnet. Die Liste beschreibt nur den Ge- brauch, sie legt nicht eine Definition fest. 100GE 100 GBit/s Ethernet 16CIF 16 times Common Intermediate Format (Picture Format) 16QAM 16-state Quadrature Amplitude Modulation 1GFC 1 Gigabaud Fiber Channel (2, 4, 8, 10, 20GFC) 1GL 1st Generation Language (Maschinencode) 1TBS One True Brace Style (C) 1TR6 (ISDN-Protokoll D-Kanal, national) 247 24/7: 24 hours per day, 7 days per week 2D 2-dimensional 2FA Zwei-Faktor-Authentifizierung 2GL 2nd Generation Language (Assembler) 2L8 Too Late (Slang) 2MS Strukturierte -
Efforts for Global Software Platforms
Platforms Efforts for Global Software Platforms HORIKAWA Fumihiro, FUJIMOTO Hideo Abstract NEC has adopted Linux as the OS for its mobile terminal software and has been developing Linux-based middle- ware for mobile devices based on MOAP (R) (L) jointly with the NTT DoCoMo, Inc. and Panasonic Mobile Communi- cations Co., Ltd. Meanwhile, six companies including both mobile phone carriers and manufacturers started the LiMo Foundation in 2007, defined the API specifications and published the Beta version of the specifications in February 2008. The LiMo Foundation plans to continue its efforts in promoting construction of Linux OS-based platform for mobile terminals and in building so-called “ecosystem.” Keywords mobile terminal, software platform, Linux, LiMo Foundation, ecosystem vice software platforms. 1. Introduction The following sections of this paper introduce the efforts being made by the LiMo Foundation and discuss NEC’s rela- NEC released N900iL in November 2004, thus adopting ted activities. “Linux” as a mobile terminal OS for the first time in Japan. Since then we have been shortening the development period and improving the software quality by using this multifunc- 2. The LiMo Foundation tion OS that features high productivity and reliability. Moreover, we have also developed a mobile terminal mid- dleware for Linux, “MOAP (L) (Mobile-phone Oriented Ap- It was in January 2007 that the LiMo Foundation was star- plication Platform Linux),” which was undertaken together ted jointly by NEC, Motorola Inc., NTT DoCoMo, Inc., Pana- with NTT DoCoMo, Inc. and Panasonic Mobile Communica- sonic Mobile Communications Co., Ltd., Samsung Electron- tions Co., Ltd. We are jointly developing components that can ics Co., Ltd. -
Code Injection in Windows Systems: Where Do We Stand Now?
Code Injection in Windows Systems: Where do We Stand Now? Nick Sempere Advisor: Ming Chow Abstract Since the mass production and distribution of personal computers began, their operating systems have made huge strides in terms of computational abilities and sophistication. With all of the added fortitude, however, these operating system cannot seem to shake their one true achilles heel: security. Despite no small amount of effort, developers seem to be in a constant cycle, identifying and patching vulnerabilities only to encounter more with the next release. This cycle is particularly evident in Windows operating systems, which represents a huge portion of the computers currently in use by the public. With the state of security in Windows systems in such an apparent state of anarchy, it should be no wonder that mainstream users find themselves in a world of uncertainty. What should they be worried about? What should they no longer have to worry about? Where does the greatest risk lie? This paper seeks to answer those questions as it explores the current state of security in Windows operating systems with a focus on one breed of vulnerabilities in particular: code injection. 1 To The Community Simply put, there are a myriad of ways to maliciously inject code nowadays. That is scary because injection acts as one of the most popular vehicles through which malwares establish a foothold in a system or network. While practically every major operating system shares this common threat, Windows systems and their vulnerabilities struck me as most worthy of further research, as they still represent the majority of system that are in use today. -
Mobile Operating Systems, the New Generation V1.01 FINAL
Executive Summary Much has changed from the world of open operating Contents systems of 2003. The mobile software market has Chapter A: Mobile Software Today: Open OSs, Linux grown into a landscape of 100s of vendors where and other Misperceptions understanding the roles, functionality, lines of A.1. The New Generation of Operating Systems partnership and competition across software products A.2. Linux: Myth and Reality is a complex endeavour, even for a seasoned industry A.3. Java: A False Start, But Efforts Continue observer. This paper aims to help change that. A.4. Nokia against Symbian A.5. Conclusions and Market Trends The paper firstly presents the key software layers for mobile phones today and explains the importance of Chapter B: Making Sense of Operating Systems, UI application execution environments and UI frameworks. Frameworks and Application Environments Section A then examines common misperceptions in Chapter C: Product reviews the software market of 2006; the flexible OS genre as In-Depth reviews of A la Mobile, Access Linux the successor to the open OSs, the myth and reality Platform, Adobe Flash Lite, GTK+, MiniGUI, Mizi behind Linux for mobile phones, and the false start but Prizm, Montavista Mobilinux, Nokia S60, Obigo, continued efforts around J2ME. Chapter B compares Openwave Midas, Qualcomm Brew, SavaJe, several software platforms for product functionality, Symbian OS, Trolltech Qtopia, UIQ And Windows licensees and speed of market penetration. Mobile. A reference section follows, consisting of 2-page Chapter D: Trends in the Mobile Software Market reviews of 16 key software products, covering historical Open OSes are out; Flexible OSs are in product background, positioning, technology, strategy, Commoditisation of the core OS technology and including the author’s critical viewpoint. -
Practical-Malware-Analysis Index.Pdf
INDEX Symbols and Numbers administrator privileges, for malware launchers, 254 ! (bang symbol), 305 Adobe Reader -- operation, 112 CVE-2010-0188 critical % operation, 112 vulnerability, 424 % symbol, 423 overflow in, 705 | (pipe symbol), in Snort, 304 ADS (Alternate Data Streams) ++ operation, 112 010 Editor, 468 feature, 139 32-bit applications, WOW64 and, 448 Advanced Encryption Standard 32-bit rotate-right-additive hash, 418 (AES), 618 64-bit malware, 441–449 decrypting, 625–626 clues to functionality, 448 advapi32.dll, 17 labs, 450–451 imports from, 20, 480, 481 solutions, 723–732 obtaining handle to, 237 advertisements, pop-up, 560–561 A AES (Advanced Encryption Standard), 618 A, at end of Windows function decrypting, 625–626 name, 17 Agobot, 376 absolute addresses, 443 air-gapped networks, 29 vs. relative addresses, in OllyDbg, _alloca_probe function, 522 184–185 alphabetic encoding, shellcode abstraction levels, in x86 disassembly, decoder with, 697 66–67 Alternate Data Streams (ADS) accept function, 143, 144, 454 feature, 139 access token, 246 ALU (arithmetic logic unit), 68 accuracy, vs. expediency, 304 AMD64 architecture, 441 active window, logging, 239 “Analysis of the Intel Pentium’s ADD encoding algorithm, 276 Ability to Support a Secure add instruction, 74, 349 Virtual Machine Monitor” AddCodeXref function (IDC), 342 (Robin and Irvine), 373 address space, loading executable AND logical operator, in x86 into another process’s, 595 architecture, 75 address space layout randomization anti-debugging, 351–366 (ASLR), 184 checks, -
Mobile W Development ! J CHAPTER 2 Goin’ Mobile with Windows
A SearchSOA.com E5book ED LETTER 0 9 CHAPTER 1 D Shifting ground f for mobile W development ! j CHAPTER 2 Goin’ mobile with Windows . ? u CHAPTER 3 Create SmartPhone 2 X apps using JavaScript f CHAPTER 4 IBM preps mobile SOA connection CHAPTER 5 Mobile development resource Mobile ApplicationDevelopment: guide Making it easier for developers r 1 MOBILE APPLICATION DEVELOPMENT • SEARCHSOA.COM Ed Letter Developers forge ahead with mobile applications By Jack Vaughan ED LETTER CHAPTER 1 workers pecking away at handheld Shifting ground Mobile applications for mobile devices. Although these machines development have not only have tons more memory than in the past, they still are basically working piqued the interest remotely, hitting on a server some - CHAPTER 2 Goin’ mobile of developers, but where, and dealing with the world via with Windows services. also of the average Behind the scenes will emerge a CHAPTER 3 cell phone user. whole new class of mobile app devel - Create opment tools, writes John K. Waters in SmartPhone Learn what all the apps using our lead story, “Mobile app dev trends: JavaScript fuss is about. Making life easier for developers.” Meanwhile, writer Patrick Meader discusses transfer Microsoft develop - CHAPTER 4 IBM preps ers in “Goin’ mobile with Windows.” mobile SOA MOBILE APPLICATIONS have piqued the Technology writer George Lawton connection interest of developers. First, the talks about JavaScript taking advan - iPhone redefined what a phone was: it tage of iPhone resources in his piece CHAPTER 5 looked a lot like a Web browser, really. “Create smartphone apps using Java- Mobile development Then, Apple opened an iPhone App Script.” Writer Rich Seeley adds IBM’s resource store that promised developers an input in the mobile community in guide opportunity to write and sell an appli - “IBM preps mobile SOA connection.” cation to a new mass audience.