Aplicación Móvil Usable Dirigida a Un Sistema Ami Con Sistema De Amarre Automático (Saa) En El Sector Eléctrico Existente, En El Marco Del Proyecto Id 4249

Total Page:16

File Type:pdf, Size:1020Kb

Aplicación Móvil Usable Dirigida a Un Sistema Ami Con Sistema De Amarre Automático (Saa) En El Sector Eléctrico Existente, En El Marco Del Proyecto Id 4249 APLICACIÓN MÓVIL USABLE DIRIGIDA A UN SISTEMA AMI CON SISTEMA DE AMARRE AUTOMÁTICO (SAA) EN EL SECTOR ELÉCTRICO EXISTENTE, EN EL MARCO DEL PROYECTO ID 4249 ANEXOS LEIDY JOHANNA IJAJÍ GUACA YENNY ALEXANDRA WAITOTO PÉREZ UNIVERSIDAD DEL CAUCA FACULTAD DE INGENIERÍA ELECTRÓNICA Y TELECOMUNICACIONES INGENIERÍA ELECTRÓNICA Y TELECOMUNICACIONES POPAYÁN 2017 APLICACIÓN MÓVIL USABLE DIRIGIDA A UN SISTEMA AMI CON SISTEMA DE AMARRE AUTOMÁTICO (SAA) EN EL SECTOR ELÉCTRICO EXISTENTE, EN EL MARCO DEL PROYECTO ID 4249 LEIDY JOHANNA IJAJÍ GUACA YENNY ALEXANDRA WAITOTO PÉREZ Director: PhD. PABLO AUGUSTO MAGÉ IMBACHÍ Codirector: MSc. JUAN FERNANDO FLÓREZ MARULANDA UNIVERSIDAD DEL CAUCA FACULTAD DE INGENIERÍA ELECTRÓNICA Y TELECOMUNICACIONES INGENIERÍA EN ELECTRÓNICA Y TELECOMUNICACIONES POPAYÁN 2017 2 CONTENIDO ANEXO A ............................................................................................................. ..1 ESTUDIO DE LAS TECNOLOGÍAS DEL LADO CLIENTE USADAS EN APLICACIONES MÓVILES .................................................................................... 1 1. INTRODUCCIÓN ....................................................................................... 2 2. DESCRIPCIÓN DE TECNOLOGÍAS WEB LADO CLIENTE MÓVIL .......... 2 2.1. Android (Linux) .................................................................................... 2 2.2. IPhone OS .......................................................................................... 3 2.3. Windows Mobile .................................................................................. 6 2.4. BlackBerry OS (RIM) ........................................................................... 7 2.5. LiMo Platform (Linux) Tizen ................................................................. 8 2.6. webOS (Linux) (Antes PalmOS) .......................................................... 9 3. COMPARACIÓN DE TECNOLOGÍAS ..................................................... 10 4. CONCLUSIONES .................................................................................... 15 ANEXO B ............................................................................................................. … SISTEMA OPERATIVO ANDROID ....................................................................... 16 1. INTRODUCCION ..................................................................................... 17 2. ARQUITECTURA DE LA PLATAFORMA ................................................ 17 2.1. KERNEL DE LINUX .......................................................................... 18 2.2. CAPA DE ABSTRACCIÓN DE HARDWARE (HAL) .......................... 18 2.3. TIEMPO DE EJECUCION DE ANDROID (ART) ............................... 18 2.4. BIBLIOTECAS C/C++ nativas ........................................................... 19 2.5. FRAMEWORK DE LA JAVA API ....................................................... 19 2.6. APPS DEL SISTEMA ........................................................................ 20 3. CICLO DE VIDA DE UNA ACTIVIDAD .................................................... 21 3.1. onCreate() ......................................................................................... 22 3.2. onStart() ............................................................................................ 22 3.3. onResume() ...................................................................................... 22 3.4. onPaused()........................................................................................ 22 3.5. onStop() ............................................................................................ 23 I 3.6. onRestart() ........................................................................................ 23 3.7. onDestroy() ....................................................................................... 23 ANEXO C ............................................................................................................. … VISUAL STORY MAPPING DE ATEMSAA .......................................................... 25 1. INTRODUCCIÓN ..................................................................................... 26 2. HISTORIAS DE USUARIO ...................................................................... 26 3. TAREAS Y RESPONSABLES ................................................................. 44 ANEXO D ............................................................................................................. … CONCEPTOS RELACIONADOS CON LA METODOLOGÍA MPIu+a ................... 46 1. ANÁLISIS DE REQUISITOS .................................................................... 47 1.1. ANÁLISIS ETNOGRÁFICO ............................................................... 47 1.2. ANÁLISIS DE IMPLICADOS (STAKEHOLDERS) ............................. 48 1.3. CLASIFICAR LOS USUARIOS.......................................................... 48 1.4. PLATAFORMA .................................................................................. 48 2. DISEÑO ................................................................................................... 49 2.1. MODELO MENTAL Y MODELO CONCEPTUAL .............................. 49 ANEXO E ............................................................................................................. … FUNCIONALIDADES DISPOSITIVOS PLC .......................................................... 55 1. FUNCIONALIDADES PLC-MMS ............................................................. 56 2. FUNCIONALIDADES PLC-TU ................................................................. 57 3. FUNCIONALIDADES PLC-MC ................................................................ 58 ANEXO F .............................................................................................................. … ENCUESTAS Y PRUEBAS .................................................................................. 59 1. INTRODUCCIÓN ..................................................................................... 60 2. ENCUESTAS Y RESULTADOS DE USABILIDAD ................................... 60 2.1. ENCUESTAS .................................................................................... 60 3. PRUEBAS Y RESULTADOS DE FUNCIONALIDAD ............................... 66 3.1. PRUEBA 1 ........................................................................................ 66 3.2. PRUEBA 2 ........................................................................................ 67 3.3. PRUEBA 3 ........................................................................................ 68 II 3.4. PRUEBA 4 ........................................................................................ 69 3.5. PRUEBA 5 ........................................................................................ 71 3.6. PRUEBA 6 ........................................................................................ 73 3.7. PRUEBA 7 ........................................................................................ 75 3.8. PRUEBA 8 ........................................................................................ 77 3.9. PRUEBA 9 ........................................................................................ 78 3.10. PRUEBA 10 ...................................................................................... 79 3.11. PRUEBA 11 ...................................................................................... 80 3.12. PRUEBA 12 ...................................................................................... 81 3.13. PRUEBA 13 ...................................................................................... 82 3.14. PRUEBA 14 ...................................................................................... 83 3.15. PRUEBA 15 ...................................................................................... 84 3.16. PRUEBA 16 ...................................................................................... 86 3.17. PRUEBA 17 ...................................................................................... 87 3.18. PRUEBA 18 ...................................................................................... 88 3.19. PRUEBA 19 ...................................................................................... 89 3.20. PRUEBA 20 ...................................................................................... 90 3.21. PRUEBA 21 ...................................................................................... 92 3.22. PRUEBA 22 ...................................................................................... 93 3.23. PRUEBA 23 ...................................................................................... 94 3.24. PRUEBA 24 ...................................................................................... 95 ANEXO G ............................................................................................................. … MANUAL DE INSTALACIÓN DE ATEMSAA ........................................................ 97 1. REQUISITOS DEL DISPOSITIVO ......................................................... 100 2. PROCESO DE INSTALACIÓN .............................................................. 100 3. TABLA DE ILUSTRACIONES ................................................................ 103 ANEXO H ............................................................................................................. … MANUAL DE USUARIO DE ATEMSAA .............................................................. 104 1. INTRODUCCION ..................................................................................
Recommended publications
  • Incubating the Next Generation of Offshore Outsourcing Entrepreneurs
    Mobile Phone Programming Introduction Dr. Christelle Scharff Pace University, USA http://atlantis.seidenberg.pace.edu/wiki/mobile2008 Objectives Getting an overall view of the mobile phone market, its possibilities and weaknesses Providing an overview of the J2ME architecture and define the buzzwords that accompanies it Why mobile phones? Nowadays mobile phones outnumber desktop computers for Internet connections in the developer world A convenient and simpler alternative to the desktop/laptop for all (developed and developing countries) Mobile phones are computers! Some numbers and important facts: • Target of 10 million iphones sales by the end of 2008 (just one year after being launched) • Google phone to be launched in 2008 • 70% of the world’s mobile subscriptions are in developing countries, NY Times April 13, 2008 Global Handset Sales by Device Type http://linuxdevices.com/files/misc/StrategyAnalytics- mobilephone-segments.jpg Devices A wide variety of devices by the main vendors: • E.g, Nokia, Motoral, Sony Ericson A wide variety of operating systems • E.g., Blackberry, Palm OS, Windows CE/Mobile, Symbian, motomagx, linux A wide variety of development environments • E.g., Java ME, Qualcomm’s BREW, Google’ Android, Google App Engine (GAE) for mobile web applications, JavaFX Programming languages: • Java, Python, Flast-lith, Objective C Operating Systems http://mobiledevices.kom.aau.dk Mobile Web Access to wireless data services using a mobile device cHTML (Compact HTML) is a subset of HTML that excludes JPEG images,
    [Show full text]
  • Google Android
    Google Android 2008/3/10 NemusTech, Inc. Lee Seung Min 네무스텍㈜ Agenda Introduction Mobile Platform Overview Background : Current Linux Mobile Platform What is Android? Features Architecture Technical Detail Android SDK Porting Android to Real Target Future of Android A conceptual model for mobile software Software Stack Kernel the core of the SW (HW drivers, memory, filesystem, and process management) Middleware The set of peripheral software libraries (messaging and communication engines, WAP renders, codecs, etc) Application Execution Environment An application manager and set APIs UI framework A set of graphic components and an interaction framework Application Suite The set of core handset application ( IDLE screen, dialer, menu screen, contacts, calendar, etc) Mobile Platforms Feature Phone Vendor Platform : Mocha, PDK, WAVE, WISE, KX, etc...... Carrier Platform : SKTelecom TPAK, NTT i-Mode (WAP), Java, WIPI, BREW, etc…… 3rd Party Solution : TAT Cascade, Qualcomm uiOne Smart Phone MicroSoft Windows Mobile Nokia : Symbian, Series 60 Apple, iPhone – OSX 10.5 Leopard Linux Customers & Licensees Not all customers or licensees are shown Source:vendor data Smartphone OS Market Share by Region Smartphone OS market share by region, 2006 Source : Canalys Current Linux Mobile Platforms LiMo Foundation https://www.limofoundation.org/sf/sfmain/do/home TrollTech Qtopia GreenPhone Acquired by Nokia OpenMoko : GNU/Linux based software development platform http://www.openmoko.org , http://www.openmoko.com Linux
    [Show full text]
  • A Taxonomy and Business Analysis for Mobile Web Applications
    A Taxonomy and Business Analysis for Mobile Web Applications Kevin Hao Liu Working Paper CISL# 2009-01 January 2009 Composite Information Systems Laboratory (CISL) Sloan School of Management, Room E53-320 Massachusetts Institute of Technology Cambridge, MA 02142 A Taxonomy and Business Analysis for Mobile Web Applications By Kevin Hao Liu Ph.D. Computer Science Victoria University Submitted to the System Design and Management Program in Partial Fulfillment of the Requirements for the Degree of Master of Science in Management and Engineering At the Massachusetts Institute of Technology February 2009 © 2009 Kevin H Liu. All rights reserved The author hereby grants to MIT permission to reproduce and to distribute publicly paper and electronic copies of this thesis document in whole or in part in any medium now known or hereafter created. Signature of Author Kevin H Liu System Design and Management Program February 2009 Certified by Stuart E Madnick John Norris Maguire Professor of Information Technology Sloan School of Management Professor of Engineering Systems School of Engineering Massachusetts Institute of Technology Thesis Supervisor Certified by Patrick Hale Director System Design & Management Program Massachusetts Institute of Technology A Taxonomy and Business Analysis for Mobile Web Applications By Kevin Hao Liu Submitted to the System Design and Management Program in February 2009 in Partial Fulfillment of the Requirements for the Degree of Master of Science in Management and Engineering ABSTRACT Mobile web applications refer to web applications on mobile devices, aimed at personalizing, integrating, and discovering mobile contents in user contexts. This thesis presents a comprehensive study of mobile web applications by proposing a new taxonomy for mobile web applications, and conducting a business analysis in the field of mobile web applications.
    [Show full text]
  • Mobile Linux Mojo the XYZ of Mobile Tlas PDQ!
    Mobile Linux Mojo The XYZ of Mobile TLAs PDQ! Bill Weinberg January 29, 2009 Copyright © 2009 Bill Weinberg, LinuxPundit,com Alphabet Soup . Too many TLAs – Non-profits – Commercial Entities – Tool Kits – Standards . ORG Typology – Standards Bodies – Implementation Consortia – Hybrids MIPS and Open Source Copyright © 2008 Bill Weinberg, LinuxPundit,com Page: 2 The Big Four . Ahem, Now Three . OHA - Open Handset Alliance – Founded by Google, together with Sprint, TIM, Motorola, et al. – Performs/support development of Android platform . LiMo Foundation – Orig. Motorola, NEC, NTT, Panasonic, Samsung, Vodaphone – Goal of created shared, open middleware mobile OS . LiPS - Linux Phone Standards Forum – Founded by France Telecom/Orange, ACCESS et al. – Worked to create standards for Linux-based telephony m/w – Merged with LiMo Foundation in June 2008 . Moblin - Mobile Linux – Founded by Intel, (initially) targeting Intel Atom CPUs – Platform / distribution to support MIDs, Nettops, UMPC MIPS and Open Source Copyright © 2008 Bill Weinberg, LinuxPundit,com Page: 3 LiMo and Android . Android is a complete mobile stack LiMo is a platform for enabling that includes applications applications and services Android, as Free Software, should LiMo membership represents appeal to Tier II/III OEMs and Tier I OEMs, ISVs and operators ODMs, who lack resources LiMo aims to leave Android strives to be “room for differentiation” a stylish phone stack LiMo presents Linux-native APIs Android is based on Dalvik, a Java work-alike The LiMo SDK has/will have compliance test suites OHA has a “non Fragmentation” pledge MIPS and Open Source Copyright © 2008 Bill Weinberg, LinuxPundit,com Page: 4 And a whole lot more .
    [Show full text]
  • 1 Sistem Operasi
    Sistem operasi - operating system - OS adalah seperangkat program yang mengelola sumber daya perangkat keras komputer, dan menyediakan layanan umum untuk aplikasi perangkat lunak. Sistem operasi adalah jenis yang paling penting dari perangkat lunak sistem dalam sistem komputer. Tanpa sistem operasi, pengguna tidak dapat menjalankan program aplikasi pada komputer mereka, kecuali program aplikasi boot diri. Waktu-berbagi jadwal tugas sistem operasi untuk penggunaan yang efisien dari sistem dan juga dapat mencakup akuntansi untuk alokasi biaya waktu prosesor, penyimpanan massa, cetak, dan sumber daya lainnya. Untuk fungsi-fungsi perangkat keras seperti sebagai masukan dan keluaran dan alokasi memori, sistem operasi bertindak sebagai perantara antara program aplikasi dan perangkat keras komputer, meskipun kode aplikasi biasanya dieksekusi langsung oleh perangkat keras dan seringkali akan menghubungi OS atau terputus oleh itu. Sistem operasi yang ditemukan pada hampir semua perangkat yang berisi komputer-dari ponsel dan konsol permainan video untuk superkomputer dan server web. Contoh populer sistem operasi modern termasuk Linux, Android, iOS, Mac OS X, dan Microsoft Windows. Pendahuluan Biasanya, istilah Sistem Operasi sering ditujukan kepada semua perangkat lunak yang masuk dalam satu paket dengan sistem komputer sebelum aplikasi-aplikasi perangkat lunak terinstal. Sistem operasi adalah perangkat lunak sistem yang bertugas untuk melakukan kontrol dan manajemen perangkat keras serta operasi-operasi dasar sistem, termasuk menjalankan perangkat lunak aplikasi seperti program-program pengolah kata dan peramban web. Secara umum, Sistem Operasi adalah perangkat lunak pada lapisan pertama yang ditempatkan pada memori komputer pada saat komputer dinyalakan. Sedangkan software-software lainnya dijalankan setelah Sistem Operasi berjalan, dan Sistem Operasi akan melakukan layanan inti umum untuk software-software itu.
    [Show full text]
  • Open Ongtang-Phd-Dissertation.Pdf
    The Pennsylvania State University The Graduate School SECURING MOBILE PHONES IN THE EVOLVING MOBILE ECOSYSTEM A Dissertation in Computer Science and Engineering by Machigar Ongtang © 2010 Machigar Ongtang Submitted in Partial Fulfillment of the Requirements for the Degree of Doctor of Philosophy August 2010 The dissertation of Machigar Ongtang was reviewed and approved∗ by the following: Patrick D. McDaniel Associate Professor of Computer Science and Engineering Dissertation Advisor, Chair of Committee Thomas F. La Porta Distinguished Professor of Computer Science and Engineering Trent Jaeger Associate Professor of Computer Science and Engineering Ling Rothrock Associate Professor of Industrial and Manufacturing Engineering Raj Acharya Professor of Computer Science and Engineering Department Head ∗Signatures are on file in the Graduate School. Abstract The revolution of mobile phone industry has been altering our life and business practices over the past few decades. Driven by user demands and technological advancement, we now experience rich mobile phone applications and sophisticated cellular services ranging from mobile payment, stock trading, to social networking, vehicle tracking to in-car control. As more players joining the community, this mobile phone environment has transformed into a complex network of interacting companies, known as mobile ecosystem. Unfortunately, this opening and converging mobile ecosystem has brought in more opportunities for more attacks on mobile phones, a key element of the system. This dissertation aims to achieve mobile phone security. We reveal two main chal- lenges that we need to overcome, namely developing a clear definition of secure phones, and building security infrastructure that imposes such definition on the phones. We also identify three key elements that contribute to the fidelity of mobile phones, namely, mobile phone platforms, mobile phone applications, and mobile content.
    [Show full text]
  • Cours Système Embarqué Et Système D'exploitation Mobile
    COURS SYSTÈME EMBARQUÉ ET SYSTÈME D’EXPLOITATION MOBILE Ikbel Daly Briki 2018/2019 SYSTÈME EMBARQUÉ Un système embarqué: c’est une combinaison de matériels et logiciels permettant de remplir une ou plusieurs fonctions spécifiques avec des contraintes plus ou moins sévères tel que la consommation, la température, la taille, les performances…[Patrice Kadionik, 2004] Un système embarqué est susceptible d’être utilisé dans un environnement matériel de faibles performances (si l’on compare au PC de bureau d’aujourd’hui). Si l’ajout de quelques Mo de mémoire sur un PC de bureau n’a pas une grosse influence sur le budget d’un utilisateur, le gain de quelques Mo sur un produit de grande consommation (téléphone, équipement auto mobile, organiseur personnel) a une énorme influence sur le coût final. [Pierre Ficheux, 2003] 2 SYSTÈME EMBARQUÉ Ébauche d’une définition: c’est un système électronique et informatique autonome qui est dédié à une tâche particulière et contenue dans un système englobant. Il n’est « généralement » pas programmable. Pas d’E/S standards Matériel et application intimement liés Logiciel enfoui … noyé dans le matériel … pas facilement discernable comme dans un PC. Il sont partout ; Radio/réveil Machine à café Télévision / télécommande Moyen de transport 3 Téléphone portable …. CARACTÉRISTIQUES D’UN SYSTÈME EMBARQUÉ Un système embarqué: des ressources limitées Système principalement numérique Le moins cher possible Une puissance de calcul limitée Pas de consommation d’énergie inutile Exécution de logiciel dédié
    [Show full text]
  • Beyond.Pdf (Slides)
    Beyond Traditional Mobile Linux by Carsten “Stskeeps” Munk, Mer project architect http://www.merproject.org Mobile Linux up to 2011 ● Moblin, MeeGo, Maemo, LiMo, OpenEmbedded (Yocto, WebOS), OpenWRT, etc.. ● OpenMoko-centric (QtMoko, FSO/SHR, etc.) ● Android (Replicant, Ophone, Baidu Yi, B2G, etc.) ● Familiar, Access Linux Platform, Ubuntu Mobile/MID, Mobilinux ● ... and many many more What do most of them have in common? ● Many of them are now dead or zombie projects. ● Many were centric around specific vendors or specific devices. ● Many of them were wasted effort for the Mobile Linux community. Mobile Linux in 2012 ● OpenWRT, OpenEmbedded (Yocto) ● Android & Boot2Gecko ● Tizen, Mer, WebOS, Linaro efforts ● Intentionally not mentioning single- hardware/vendor OS'es, UI projects or open hardware ● Linux in general in all sorts of consumer devices ● Why not Fedora, Debian, Ubuntu, Slackware, etc..? The world around us If we were to interpret the world around us through what we see in popular Linux distributions and attitudes There's just one problem about that.. This is not how real life looks like anymore. ● But but but, what about KDE, GNOME, all our projects centered around the PC as the primary form of computer usage? ● We're experiencing the beginnings of a paradigm shift in how people use computers. “the notion of a major change in a certain thought-pattern — a radical change in personal beliefs, complex systems or organizations, replacing the former way of thinking or organizing with a radically different way of thinking or organizing” But.. ● A lot of open source projects are built around this old paradigm – centered around the PC.
    [Show full text]
  • UNIVERSITY of PIRAEUS DEPARTMENT of DIGITAL SYSTEMS POSTGRADUATE PROGRAMME Economic Management and Digital Systems Security
    UNIVERSITY OF PIRAEUS DEPARTMENT OF DIGITAL SYSTEMS POSTGRADUATE PROGRAMME Economic Management and Digital Systems Security Smartphone Forensics & Data Acquisition DISSERTATION Pachigiannis Panagiotis MTE1219 2015 Contents Contents……… ....................................................................................................................................... 2 Acknowledgement ................................................................................................................................... 7 Abstract……. ........................................................................................................................................... 8 1) Introduction........................................................................................................................................... 9 1.1) Context ........................................................................................................................................... 9 1.2) Aim & Objective .......................................................................................................................... 10 1.3) Background .................................................................................................................................. 11 1.4) Structure of Thesis ....................................................................................................................... 11 2) Mobile Devices ..................................................................................................................................
    [Show full text]
  • Palm OS Cobalt 6.1 in February 2004 6.1 in February Cobalt Palm OS Release: Last 11.2 Ios Release: Latest
    …… Lecture 11 Market Overview of Mobile Operating Systems and Security Aspects Mobile Business I (WS 2017/18) Prof. Dr. Kai Rannenberg . Deutsche Telekom Chair of Mobile Business & Multilateral Security . Johann Wolfgang Goethe University Frankfurt a. M. Overview …… . The market for mobile devices and mobile OS . Mobile OS unavailable to other device manufacturers . Overview . Palm OS . Apple iOS (Unix-based) . Manufacturer-independent mobile OS . Overview . Symbian platform (by Symbian Foundation) . Embedded Linux . Android (by Open Handset Alliance) . Microsoft Windows CE, Pocket PC, Pocket PC Phone Edition, Mobile . Microsoft Windows Phone 10 . Firefox OS . Attacks and Attacks and security features of selected . mobile OS 2 100% 20% 40% 60% 80% 0% Q1 '09 Q2 '09 Q3 '09 Q1 '10 Android Q2 '10 Q3 '10 Q4 '10 u Q1 '11 sers by operating sers by operating iOS Q2 '11 Worldwide smartphone Worldwide smartphone Q3 '11 Q4 '11 Microsoft Q1 '12 Q2 '12 Q3 '12 OS Q4 '12 RIM Q1 '13 Q2 '13 Q3 '13 Bada Q4' 13** Q1 '14 Q2 '14 s ystem ystem (2009 Q3 '14 Symbian Q4 '14 Q1 '15 [ Q2 '15 Statista2017a] Q3 '15 s ales ales to end Others Q4 '15 Q1 '16 Q2 '16 Q3 '16 - 2017) Q4 '16 Q1 '17 Q2 '17 3 . …… Worldwide smartphone sales to end …… users by operating system (Q2 2013) Android 79,0% Others 0,2% Symbian 0,3% Bada 0,4% BlackBerry OS 2,7% Windows 3,3% iOS 14,2% [Gartner2013] . Android iOS Windows BlackBerry OS Bada Symbian Others 4 Worldwide smartphone sales to end …… users by operating system (Q2 2014) Android 84,7% Others 0,6% BlackBerry OS 0,5% Windows 2,5% iOS 11,7% .
    [Show full text]
  • Confine: Automated System Call Policy Generation for Container
    Confine: Automated System Call Policy Generation for Container Attack Surface Reduction Seyedhamed Ghavamnia Tapti Palit Azzedine Benameur Stony Brook University Stony Brook University Cloudhawk.io Michalis Polychronakis Stony Brook University Abstract The performance gains of containers, however, come to the Reducing the attack surface of the OS kernel is a promising expense of weaker isolation compared to VMs. Isolation be- defense-in-depth approach for mitigating the fragile isola- tween containers running on the same host is enforced purely in tion guarantees of container environments. In contrast to software by the underlying OS kernel. Therefore, adversaries hypervisor-based systems, malicious containers can exploit who have access to a container on a third-party host can exploit vulnerabilities in the underlying kernel to fully compromise kernel vulnerabilities to escalate their privileges and fully com- the host and all other containers running on it. Previous con- promise the host (and all the other containers running on it). tainer attack surface reduction efforts have relied on dynamic The trusted computing base in container environments analysis and training using realistic workloads to limit the essentially comprises the entire kernel, and thus all its set of system calls exposed to containers. These approaches, entry points become part of the attack surface exposed to however, do not capture exhaustively all the code that can potentially malicious containers. Despite the use of strict potentially be needed by future workloads or rare runtime software isolation mechanisms provided by the OS, such as conditions, and are thus not appropriate as a generic solution. capabilities [1] and namespaces [18], a malicious tenant can Aiming to provide a practical solution for the protection leverage kernel vulnerabilities to bypass them.
    [Show full text]
  • Deploying IP Office Server Edition
    IP Office Deploying IP Office Server Edition Release 11.0 Issue 12 March 2020 © 2020, Avaya Inc. YOU DO NOT WISH TO ACCEPT THESE TERMS OF USE, YOU All Rights Reserved. MUST NOT ACCESS OR USE THE HOSTED SERVICE OR AUTHORIZE ANYONE TO ACCESS OR USE THE HOSTED Notice SERVICE. While reasonable efforts have been made to ensure that the Licenses information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA the right to make changes and corrections to the information in this WEBSITE, HTTPS://SUPPORT.AVAYA.COM/LICENSEINFO, document without the obligation to notify any person or organization UNDER THE LINK “AVAYA SOFTWARE LICENSE TERMS (Avaya of such changes. Products)” OR SUCH SUCCESSOR SITE AS DESIGNATED BY AVAYA, ARE APPLICABLE TO ANYONE WHO DOWNLOADS, Documentation disclaimer USES AND/OR INSTALLS AVAYA SOFTWARE, PURCHASED “Documentation” means information published in varying mediums FROM AVAYA INC., ANY AVAYA AFFILIATE, OR AN AVAYA which may include product information, operating instructions and CHANNEL PARTNER (AS APPLICABLE) UNDER A COMMERCIAL performance specifications that are generally made available to users AGREEMENT WITH AVAYA OR AN AVAYA CHANNEL PARTNER. of products. Documentation does not include marketing materials. UNLESS OTHERWISE AGREED TO BY AVAYA IN WRITING, Avaya shall not be responsible for any modifications, additions, or AVAYA DOES NOT EXTEND THIS LICENSE IF THE SOFTWARE deletions to the original published version of Documentation unless WAS OBTAINED FROM ANYONE OTHER THAN AVAYA, AN AVAYA such modifications, additions, or deletions were performed by or on AFFILIATE OR AN AVAYA CHANNEL PARTNER; AVAYA the express behalf of Avaya.
    [Show full text]