Possible Approaches to Certification Authority Implementation

Total Page:16

File Type:pdf, Size:1020Kb

Possible Approaches to Certification Authority Implementation MASARYK UNIVERSITY FACULTY OF INFORMATICS ¨ © ¦¨§ ! " ¤ ¥ # $ ¢ £ F G H ¡ % & D E ')(+* ?@ACB ,.-0/132 46587:9<;>= Possible approaches to certification authority implementation DIPLOMA THESIS Jan´ Lieskovsky´ Brno, 2007 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. I would like to express thanks to prof. RNDr. Jozef Gruska, DrSc., Doc. RNDr. Vaclav´ Matya´s,ˇ Ms.C Ph.D and Ing. Mgr. Zdenekˇ Rˇ ´ıha, Ph.D for their explanatory, exhaustive and interesting courses and materials related to the topic of cryptography that brought me round to the complex, mathematical and beautiful world of computer security. My special thanks to my adviser Doc. RNDr. Vaclav´ Matya´s,ˇ Ms.C Ph.D for his perceptive leadership, showing me the direction, this work should follow, in times of doubt and for his patience during my study of this com- plex topic. ii Keywords certificate, certificate authority, certificate request, extensions, PKI, QCA, registration authority, signature algorithm, subject of the certificate, X.509 iii Abstract The presented work covers the subject of certification authorities and re- lated topics. First, we discuss the relevant cryptography areas, like public- key cryptography, hash functions and digital signatures which are used in the digital certificates. Then we analyze the particular parts of the public- key infrastructure (PKI) to be able to determine the CA position in it and to separate the function, it should perform. Further we discuss in more detail the structure of the digital certificate request and digital certificate. We fo- cus on the extensions, in order to exactly describe the meaning of particular extension and relations between them (like allowed combinations of bits in the “KeyUsage” extension). In the second part of our work, we analyze current approaches to a CA implementation. We discuss them in order to select our own approach. In the end, we describe library used and tools and talk about gained experi- ences and insights. This diploma thesis should also provide information needed for CA im- plementation – introductory describing basic principles, CA functions and methods, structure of issued electronic documents, as well as description of currently used CA implementation techniques. A result of this investiga- tion should be a fully functional CA, implemented by us. iv To Vierka Contents 1 Introduction . 4 1.1 Overview and structure of this diploma thesis . 4 2 Cryptography and certification authorities . 6 2.1 Important cryptographic properties . 6 2.2 Symmetric-key cryptography . 7 2.3 Public-key cryptography . 8 2.4 Hash functions . 10 2.5 Digital signatures . 12 2.5.1 Features of digital signatures . 14 3 Internet public-key infrastructure (PKI) . 15 3.1 Public-key infrastructure (PKI) . 15 3.1.1 E-commerce scenario . 16 3.1.2 Registration Authority (RA) . 17 3.1.3 Certification Authority (CA) . 19 3.1.4 Subject of the certificate – End entity . 20 3.1.5 Receiver of the certificate – Relying party . 20 3.1.6 The Repository . 21 3.1.7 X.509 (RFC 3280) [8] . 21 3.1.8 Certificate revocation lists (CRL) and Online certifi- cate status protocol (OCSP) . 22 4 From certificate request to digital certificate . 26 4.1 Digital certificate request (DCR) . 26 4.2 Types of extensions used in digital certificate requests and digital certificates . 30 4.2.1 Authority Key Identifier . 30 4.2.2 Subject Key Idenfitier . 31 4.2.3 Key Usage . 31 4.2.4 Subject Alternative Name . 34 4.2.5 Basic Constraints . 36 4.2.6 Extended Key Usage . 36 4.2.7 Inhibit Any Policy . 38 4.3 Digital certificate (DC) . 39 2 4.3.1 Self-Signed and CA certificates . 42 5 Possible approaches to the certification authority implementation 43 5.1 OpenCA (OpenPKIX) . 44 5.2 Java Cryptographic Architecture (JCA) [15] . 47 5.3 What features we need to realize CA via the “library” approach 48 6 Qt Cryptographic Architecture (QCA) . 51 6.1 Description . 51 7 Qintca – CA implemented in QCA . 53 8 Conclusions . 60 A Examples of digital certificate request and digital certificate . 66 A.1 Example of digital certificate request . 67 A.2 Example of digital certificate . 68 B Digital certificate request and digital certificate creation . 69 B.1 Using the OpenSSL suite . 69 C Sample related QCA class . 71 C.1 Look and methods of the QCA::CertificateRequest class . 71 D Qintca screenshots . 75 3 Chapter 1 Introduction “How is an error possible in mathematics?” Jules H. Poincare Nowadays, communication over the Internet and the possibility to use various Internet services is gradually becoming available to a wider part of the population. We can benefit from usage of electronic mail, chat, file- sharing and file transport. We can watch movies or lectures, listen to mu- sic and play games. Besides this ”amusement” part, there is also the far more visible “official part” of Internet. Many government organizations have their electronic equivalents. We can reserve and buy tickets and watch the meteorological progress or stock options on-line. So the “electronic life” is becoming more and more a part of our ordinary life. This fact is bringing as well as new challenges and responsibilities for us. We should take more care about topics like cryptography, digital signatures, computer security, subject authentication and authorization. We want the benefit of these new Internet possibilities while simultaneously protecting our property, identity or other things important for us like our medical records and bank account numbers etc. To achieve this goal we need to be more and more interested in modern computer security and the techniques it can provide. 1.1 Overview and structure of this diploma thesis The aim of the second chapter is to pinpoint and explain cryptographic terms, that may be needed for CA implementation. It is an attempt to collect and define such terms. In the third chapter we are describing the infrastructure that is needed to be able to meet four security goals.1 We are focusing on particular items 1. The list will be provided in section 2.3. 4 1. INTRODUCTION of Public-Key Infrastructure (PKI) and explaining what it consist, of, the function of its specific parts, what they can be used for and where we can find its representatives. In the fourth chapter we continue in developing the image of the PKI by describing the exact structure of digital certificate request (DCR) and digital certificate (DC). Some portion is also dedicated to the description of the process of creating the digital certificates from DCRs. In the fifth chapter we are trying to describe and analyze current ap- proaches to certification authority implementation. We describe the char- acteristics of representatives in each category by comparing these various ways. Then we select one to implement our CA. The content of the sixth chapter is dedicated to the description of the structure and function of the Qt cryptographic architecture (QCA) – the library we have chosen for our CA implementation. We are discussing its parts, describing the selection proces and focusing on details of its classes. The seventh chapter is a summarized overview of insights and impres- sions experienced by the creation and implementation of our CA. We present a description of tools used, applications and algorithms. We also provide a TO-DO list (list of desired future possible enhancements and features). The conclusions is dedicated to the summarizing of goals, we have suc- cessfully reached and specification of the meaning of this diploma thesis. In the attachment one can find an overview of the usage of OpenSSL suite for the creation of digital certificate requests, end user and self signed CA certificates. 5 Chapter 2 Cryptography and certification authorities “The enchanting charms of this sublime science reveal only to those who have the courage to go deeply into it.” Carl Friedrich Gauss 2.1 Important cryptographic properties Let us suppose, we want to design, develop and maintain an e-commerce shop to be able to distribute our products over the Internet. One of the things we need to do, 1, is to make a list of all security goals, we would like to achieve. This is one of the tasks of modern cryptography, we will describe. But let us begin with a short classification of the cryptography. The modern cryptography is usually divided into two categories: • The classical cryptography and • the quantum cryptography. Functions, principles, methods and algorithms of classical cryptography came out of laws of classical physics – the smallest unit of information is a bit. Octets of bits are combined into bytes (B). Sequences of bits are input into many arithmetical and logical operations, and many classical cryptosys- tems can be viewed on, as processing such streams of bits. In contrast, methods used in quantum cryptography, are organized in a different way. The source of this difference is formed within the laws of microcosms and modern quantum physics. Thus, quantum cryptography 1. We will forget the need to organize and ensure the economic related tasks of our busi- ness at this moment and take into account only the informatics related part. 6 2. CRYPTOGRAPHY AND CERTIFICATION AUTHORITIES can benefit not only from the mathematical complexity of known crypto- graphic problems, 2 but also from the combination of these features with unexpected and inconvenient laws of quantum physics, to develop even better and more secure cryptographic algorithms and protocols. It is a good practice to divide classical cryptography into two groups: • Symmetric-key cryptography. • Public-key cryptography [10]. 2.2 Symmetric-key cryptography Kerchhoff's 3 principle claims: “ The security of transmitted message should not rely on secrecy of mechanism of used encryption algorithm, but on the protection of the shared secret – so called key”.
Recommended publications
  • Openpgp Card Application User Guide
    OpenPGP Card Application User Guide Cédric Mesnil ([email protected]) May 30, 2018 Contents 1 License 3 2 Introduction 4 3 How to install GPG Application 5 3.1 Nano S / Blue . 5 3.1.1 From Binary . 5 3.1.2 From source . 6 3.2 System Configuration . 6 3.2.1 Linux . 6 3.2.2 MAC . 6 3.2.3 Windows . 7 4 Nano S OpenPGP Card application explained 8 4.1 Menu Overview . 8 4.2 Device Info . 9 4.3 Select Slot . 9 4.4 Settings . 10 4.4.1 Key Template . 10 4.4.2 Seed mode . 11 4.4.3 PIN mode . 11 4.4.4 UIF mode . 13 4.4.5 Reset . 13 5 Nano S OpenPGP Card application usage 14 5.1 GPG . 14 5.1.1 Configuration . 14 5.1.2 Get/Set basic information . 15 5.1.3 Generate new key pair . 16 5.1.4 Moving existing key pair . 21 5.1.5 Decrypting and Signing . 23 5.2 SSH . 23 5.2.1 Overview . 23 5.2.2 Generate new key on device . 23 1 5.2.3 Add sub-key . 23 5.2.4 Configure SSH and GPG . 26 5.3 Trouble/FAQ . 28 6 Annexes 29 6.1 References . 29 2 Chapter 1 License Author: Cedric Mesnil <[email protected]> License: Copyright 2017 Cedric Mesnil <[email protected]>, Ledger SAS Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    [Show full text]
  • An Architecture for Cryptography with Smart Cards and NFC Rings on Android
    OpenKeychain: An Architecture for Cryptography with Smart Cards and NFC Rings on Android DOMINIK SCHÜRMANN, TU Braunschweig, Germany SERGEJ DECHAND, University of Bonn, Germany LARS WOLF, TU Braunschweig, Germany While many Android apps provide end-to-end encryption, the cryptographic keys are still stored on the device itself and can thus be stolen by exploiting vulnerabilities. External cryptographic hardware solves this issue, but is currently only used for two-factor authentication and not for communication encryption. In this paper, we design, implement, and evaluate an architecture for NFC-based cryptography on Android. Our high-level API provides cryptographic operations without requiring knowledge of public-key cryptography. By developing OpenKeychain, we were able to roll out this architecture for more than 100,000 users. It provides encryption for emails, messaging, and a password manager. We provide a threat model, NFC performance measurements, and discuss their impact on our architecture design. As an alternative form factor to smart cards, we created the prototype of an NFC signet ring. To evaluate the UI components and form factors, a lab study with 40 participants at a large company has been conducted. We measured the time required by the participants to set up the system and reply to encrypted emails. These measurements and a subsequent interview indicate that our NFC-based solutions are more user friendly in comparison to traditional password-protected keys. CCS Concepts: • Security and privacy → Usability in security and privacy; Key management; Hardware-based security protocols; • Human-centered computing → Mobile devices; Additional Key Words and Phrases: NFC, near-field communication, smart card, ring ACM Reference Format: Dominik Schürmann, Sergej Dechand, and Lars Wolf.
    [Show full text]
  • Applying Mix Nets to Email Document
    Ref. Ares(2016)2647269 - 08/06/2016 Harry Halpin (Greenhost/LEAP)) Kali Kaneko (Greenhost/LEAP) Ruben Pollan (Greenhost/LEAP) Elijah Sparrow (Greenhost/LEAP)) Mooness Davarian (Greenhost/LEAP) Raf Degens (Medialaan/Mobile Vikings) Tariq Elahi (KUL) George Danezis (UCL) Applying Mix Nets to Email Document Deliverable D 7.1 June 8, 2016 Panoramix Project, # 653497, Horizon 2020 http://www.panoramix-project.eu Contents 1 Introduction 3 2 Use-cases 4 2.1 Companies and Government Use-case . 4 2.2 Journalist Use-case . 5 2.3 Activists . 5 3 Email Systems 7 4 Threat Models and Requirements 9 4.1 Threat Models . 9 4.2 Requirements . 10 4.2.1 Security Requirements . 11 4.2.2 Privacy Requirements . 11 4.3 Problems and Meditations . 12 4.3.1 Security Requirement Problem: StartTLS downgrade . 12 4.3.2 Security Requirement Problem: DNS hijacking . 12 4.3.3 Security Requirement Problem: MX impersonation . 13 4.3.4 Privacy Requirement Problem: Abusive Users . 13 4.3.5 Privacy Requirement Problem: Spam . 14 4.3.6 Privacy and Abuse Prevention Mediations . 15 5 LEAP Software 17 5.1 The LEAP Architecture . 18 5.1.1 LEAP Platform . 19 5.1.2 Soledad . 20 5.1.3 LEAP Client . 21 5.1.4 Nicknym Key-Management . 22 5.2 LEAP for Email Encryption Example . 22 1 5.2.1 Setting up a new device . 22 5.2.2 Receiving Mail . 23 5.2.3 Mailbox Sync . 23 5.2.4 Sending Mail . 23 5.3 Current State and Future Work . 23 6 End-user Usability 25 7 System Administration Usability 27 8 Empirical Mix-net Parameters 30 8.1 Empirical Data .
    [Show full text]
  • Gnuk — a Free Software USB Token Implementation Niibe Yutaka
    Gnuk — A Free Software USB Token Implementation Niibe Yutaka <[email protected]> What’s Gnuk? Free Software implementation of Cryptographic Token For GNU Privacy Guard Supports OpenPGP card protocol version 2 Runs on STM32 processor Named after NUK® My son used to be with his NUK®, always, everywhere I wish Gnuk Token can be a soother for GnuPG user NUK® is a registered trademark owend by MAPA GmbH, Germany. Cryptographic Token? Stores your Secret Keys Performs security operations on the device Digital signature Authentication Decryption No direct access of Secret Keys How useful? Can bring secret keys securely On the go, you can do: Make digital signature Authenticate yourself Read encrypted mail GNU Privacy Guard (GnuPG) Tool for Privacy by Cryptography Conforms to OpenPGP standard Usage: Digital Signature Encryption/Decryption Authentication Supports "OpenPGP card" OpenPGP card Smartcard to put GnuPG keys Follows OpenPGP protocol standard Features of v2.0: RSA 1024-bit, 2048-bit, 3072-bit Three keys: Sign, Decrypt, Auth Key generation on the card RSA accelerator OpenPGP card Applications GnuPG OpenSSH → gpg-agent TLS/SSL Client authentication Scute (Network Security Service) PAM Poldi Problem to solve Where and how we put our secret keys? On the disk of our PC Encrypted by passphrase Not Secure Enough OpenPGP card Good (portable, secure) Not easily deployed (reader is not common) FSIJ USB Token v1 (2008) Hardware: Built a PCB CPU: Atmel AVR ATmega 328 @20MHz Software: RSA computation routine for AVR RSA 1024-bit About 5sec Data objects
    [Show full text]
  • Metadefender Core V4.17.3
    MetaDefender Core v4.17.3 © 2020 OPSWAT, Inc. All rights reserved. OPSWAT®, MetadefenderTM and the OPSWAT logo are trademarks of OPSWAT, Inc. All other trademarks, trade names, service marks, service names, and images mentioned and/or used herein belong to their respective owners. Table of Contents About This Guide 13 Key Features of MetaDefender Core 14 1. Quick Start with MetaDefender Core 15 1.1. Installation 15 Operating system invariant initial steps 15 Basic setup 16 1.1.1. Configuration wizard 16 1.2. License Activation 21 1.3. Process Files with MetaDefender Core 21 2. Installing or Upgrading MetaDefender Core 22 2.1. Recommended System Configuration 22 Microsoft Windows Deployments 22 Unix Based Deployments 24 Data Retention 26 Custom Engines 27 Browser Requirements for the Metadefender Core Management Console 27 2.2. Installing MetaDefender 27 Installation 27 Installation notes 27 2.2.1. Installing Metadefender Core using command line 28 2.2.2. Installing Metadefender Core using the Install Wizard 31 2.3. Upgrading MetaDefender Core 31 Upgrading from MetaDefender Core 3.x 31 Upgrading from MetaDefender Core 4.x 31 2.4. MetaDefender Core Licensing 32 2.4.1. Activating Metadefender Licenses 32 2.4.2. Checking Your Metadefender Core License 37 2.5. Performance and Load Estimation 38 What to know before reading the results: Some factors that affect performance 38 How test results are calculated 39 Test Reports 39 Performance Report - Multi-Scanning On Linux 39 Performance Report - Multi-Scanning On Windows 43 2.6. Special installation options 46 Use RAMDISK for the tempdirectory 46 3.
    [Show full text]
  • Gnuk — an Openpgp USB Token Implementation Niibe Yutaka <[email protected]>
    Gnuk — An OpenPGP USB Token Implementation Niibe Yutaka <[email protected]> About Me Contributor to GNU Project GNU Emacs, Guile, glibc, GCC GPLv3, GNU Privacy Guard Japanese Translation Team Contributor to Linux: PLIP, SuperH, M32R Debian Developer: Golly Chair of FSIJ Distro and Crypto Token Distribution developers care about integrity of distribution GnuPG is our friend Where to put my GPG keys? OpenPGP card is great but card reader (possibly big) is not my friend Crypto Stick is great too What’s Gnuk? Free Software implementation of Cryptographic Token Supports OpenPGP card protocol version 2 Runs on STM32 processor Supports RSA 2048-bit Named after NUK® My son used to be with his NUK®, always, everywhere I wish Gnuk Token can be a soother for GnuPG user NUK® is a registered trademark owend by MAPA GmbH, Germany. Cryptographic Token? Stores your Secret Keys Performs security operations on the device Digital signature Authentication Decryption No direct access to Secret Keys How useful? Can bring secret keys securely On the go, you can do: Make digital signature Authenticate yourself Read encrypted mail GNU Privacy Guard (GnuPG) Privacy Tool by Cryptography Conforms to OpenPGP standard Usage: Digital Signature Encryption/Decryption Authentication Supports "OpenPGP card" OpenPGP card Smartcard to put GnuPG keys Follows OpenPGP protocol standard Features of v2.0: RSA 1024-bit, 2048-bit, 3072-bit Three keys: Sign, Decrypt, Auth Key generation on the card RSA accelerator OpenPGP card Applications GnuPG OpenSSH → gpg-agent TLS/SSL Client authentication
    [Show full text]
  • IDOL Connector Framework Server 12.0 Administration Guide
    Connector Framework Server Software Version 12.0 Administration Guide Document Release Date: June 2018 Software Release Date: June 2018 Administration Guide Legal notices Copyright notice © Copyright 2018 Micro Focus or one of its affiliates. The only warranties for products and services of Micro Focus and its affiliates and licensors (“Micro Focus”) are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. Micro Focus shall not be liable for technical or editorial errors or omissions contained herein. The information contained herein is subject to change without notice. Trademark notices Adobe™ is a trademark of Adobe Systems Incorporated. Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation. UNIX® is a registered trademark of The Open Group. Documentation updates The title page of this document contains the following identifying information: l Software Version number, which indicates the software version. l Document Release Date, which changes each time the document is updated. l Software Release Date, which indicates the release date of this version of the software. To verify you are using the most recent edition of a document, go to https://softwaresupport.softwaregrp.com/group/softwaresupport/search-result?doctype=online help. You will also receive new or updated editions of documentation if you subscribe to the appropriate product support service. Contact your Micro Focus sales representative for details. To check for new versions of software, go to https://www.hpe.com/software/entitlements. To check for recent software patches, go to https://softwaresupport.softwaregrp.com/patches. The sites listed in this section require you to sign in with a Software Passport.
    [Show full text]
  • Scdaemon — a New Framework for Smart Card Access
    SCdaemon — A New Framework for Smart Card Access Werner Koch g10 Code <[email protected]> February 9, 2007 For GnuPG 2.0 a new framework to access hardware token with an integrated GUI. Its smart cards has been developed. It is based on a API is text based and thus easy to debug and daemon process and designed as a replacement audit. An internal interface within SCdae- for the PC/SC architecture. The problems of mon provides a standardized interface to any PC/SC as and the new solution are described. smart card application module to implement The new API as well as an introduction on how the host part of an actual smart card applica- supporting code for new smart cards needs to tion. These modules allow implementing parts be written is given. Further we briefly describe of smart card application on the host to utilize a PKCS#11 connector based on this API. the host’s larger resources. As of now, mod- ules for several PKCS#15 applications, DIN- SIG, OpenPGP and the Telesec card are avail- 1 Overview able. We briefly describe the history of SCdae- Smart card support under Unix suffers from mon, the API, the general structure of mod- non-standard interfaces and non-matured sup- ules and explain one concrete module. Scute, porting software. Only slowly the landscape a PKCS#11 connector will be explained as an is changing but there are still more than just example on how the API is used by a real world a few problems left. In fact, applications on client.
    [Show full text]
  • PGP-Zertifikate: Des Signaturrechts Vergessene Kinder?
    PGP-Zertifikate: des Signaturrechts vergessene Kinder? PGP-Zertifikate „...des Signaturrechts vergessene Kinder?“ Die Teilnahme am Rechtsleben mit OpenPGP im europäischen und österreichischen Rechtsrahmen Studie im Rahmen der netidee 2007 mit freundlicher Unterstützung der Internet Privatstiftung Austria (IPA) Ziviltechniker DDipl.-Ing. Gernot W. Schmied Diese Studie steht unter einer Creative Commons Lizenz PGP-Studie-5.1 © 2008 DDipl.-Ing. Gernot Schmied Seite 1 von 31 PGP-Zertifikate: des Signaturrechts vergessene Kinder? Inhaltsverzeichnis 1.Vorwort.............................................................................................................4 2.Urherberschaft, Verbreitung und Verwertung.................................................5 3.Begriffskonvention...........................................................................................5 4.Kernfragen der Studie.....................................................................................6 5.Einleitung und historischer Rückblick.............................................................6 5.1.von Phil Zimmermann bis GnuPG & PGP Corp....................................................6 5.2.Verbreitung von OpenPGP (GnuPG & PGP Corp.)...............................................7 6.Anforderungen der Informationsgesellschaft..................................................8 6.1.wirtschaftliche und gesellschaftliche Aspekte – das Wesen der Informationsgesellschaft................................................................8 6.2.Rollen von Signatur
    [Show full text]
  • Security Architecture for Smart Hubs
    Sichere Architektur für Smart Hubs BACHELORARBEIT zur Erlangung des akademischen Grades Bachelor of Science im Rahmen des Studiums Technische Informatik eingereicht von Viktor Ullmann Matrikelnummer 00925881 an der Fakultät für Informatik der Technischen Universität Wien Betreuung: Ao.Univ.Prof.Dr. Wolfgang Kastner Wien, 8. Juni 2018 Viktor Ullmann Wolfgang Kastner Technische Universität Wien A-1040 Wien Karlsplatz 13 Tel. +43-1-58801-0 www.tuwien.ac.at Security Architecture for Smart Hubs BACHELOR’S THESIS submitted in partial fulfillment of the requirements for the degree of Bachelor of Science in Computer Engineering by Viktor Ullmann Registration Number 00925881 to the Faculty of Informatics at the TU Wien Advisor: Ao.Univ.Prof.Dr. Wolfgang Kastner Vienna, 8th June, 2018 Viktor Ullmann Wolfgang Kastner Technische Universität Wien A-1040 Wien Karlsplatz 13 Tel. +43-1-58801-0 www.tuwien.ac.at Erklärung zur Verfassung der Arbeit Viktor Ullmann Gersthoferstraße 86, 1180 Wien Hiermit erkläre ich, dass ich diese Arbeit selbständig verfasst habe, dass ich die verwen- deten Quellen und Hilfsmittel vollständig angegeben habe und dass ich die Stellen der Arbeit – einschließlich Tabellen, Karten und Abbildungen –, die anderen Werken oder dem Internet im Wortlaut oder dem Sinn nach entnommen sind, auf jeden Fall unter Angabe der Quelle als Entlehnung kenntlich gemacht habe. Wien, 8. Juni 2018 Viktor Ullmann v Danksagung Ich danke Nora, meinen Eltern und meinem Betreuer, Wolfgang Kastner. vii Kurzfassung Mit zunehmender Zahl an smarten Geräten in den Haushalten steigt der Bedarf, auf diese Geräte in einer einheitlichen Schnittstelle zuzugreifen und sie zu steuern. Smart Hubs ermöglichen dies. Diese Arbeit zielt darauf ab, Design-Vorschläge für Smart Hub Entwickler bereitzustellen.
    [Show full text]
  • The Enigmail Handbook V1.0.0
    EnigMail openpgp email security for mozilla applications The Handbook by Daniele Raffo with Robert J. Hansen and Patrick Brunschwig v 1.0.0 and earlier 1. Table of Contents 2. Introduction..................................................................................5 3. Acknowledgements.....................................................................8 4. The Enigmail team.......................................................................9 5. Getting started...........................................................................10 5.1. Installing GnuPG.....................................................................................10 5.1.1. Installing GnuPG on Microsoft Windows..........................................10 5.1.2. Installing GnuPG on Macintosh OS X..............................................10 5.1.3. Installing GnuPG on Linux / UNIX....................................................11 5.2. Installing Thunderbird / SeaMonkey........................................................11 5.3. Installing Enigmail....................................................................................12 5.3.1. Installing Enigmail on Thunderbird...................................................12 5.3.2. Installing Enigmail on SeaMonkey...................................................12 5.3.3. Installing a locale for Enigmail..........................................................13 6. Quick start..................................................................................14 6.1. The Setup Wizard....................................................................................15
    [Show full text]
  • Q1. Explain Secret and Public Key Cryptography Schemes. Use Small Examples to Illustrate Your Claims
    Q1. Explain secret and public key cryptography schemes. Use small examples to illustrate your claims. State relative advantages of each scheme. Secret Key Cryptography Overview Alice wants to send a message to Bob. Both Alice and Bob share the same secret key. To encrypt the message Alice XORs her message with the shared secret key. To decrypt the message Bob also XORs the message with his (the same) secret key. Ex. Key = 0011 Alice’s message = 0101 Alice’s message XORed with the key: 0011 XOR 0101 = 0110 What Bob Recieves = 0110 Bob applies the secret key again to get the original message: 0110 XOR key = 0101 This works for three reasons: • XOR is associative and • Any binary value XORed with itself is 0 • Any binary value XORed with 0 is itself The advantages of secret key cryptography are that 1. Performing XOR is very fast. 2. It has been well tested. The disadvantages are that 1. The key must remain secret. 2. Exchanging keys with someone must be done in secret. 3. Each communicating pair of people need to share a key. Public Key Cryptography Overview In public key cryptography there are two parts to the key: a secret part and a public part. In order for Alice to send Bob a message she first needs to obtain his public key. Because Bob likes to be contacted (albeit only via encrypted messages) he has published his public key on his homepage for anyone to download. Alice obtains his public key, encrypts a message using this key and then sends it to Bob.
    [Show full text]