DOCSLIB.ORG

Sp.800-182 Nist Special Publication 800-182

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

COMPUTER SECURITY DIVISION ANNUAL REPORT 2015 NIST SPECIAL PUBLICATION 800-182 THIS PAGE IS LEFT INTENTIONALLY BLANK. THIS PUBLICATION IS AVAILABLE FREE OF CHARGE FROM: http://dx.doi.org/10.6028/NIST.SP.800-182 NIST SPECIAL PUBLICATION 800-182 COMPUTER SECURITY DIVISION ANNUAL REPORT 2015 PATRICK O’REILLY, EDITOR CO-EDITORS: Computer Security Division Larry Feldman Information Technology Laboratory Greg Witte G2, Inc. Annapolis Junction, Maryland THIS PUBLICATION IS AVAILABLE FREE OF CHARGE FROM http://dx.doi.org/10.6028/NIST.SP.800-182 JULY 2016 U.S. DEPARTMENT OF COMMERCE Penny S. Pritzker, Secretary NATIONAL INSTITUTE OF STANDARDS AND TECHNOLOGY Willie May, Under Secretary of Commerce for Standards and Technology and Director AUTHORITY This publication has been developed by NIST in accordance with its statutory responsibilities under the Federal Information Security Modernization Act (FISMA) of 2014, 44 U.S.C. § 3541 et seq., Public Law (P.L.) 113-283. NIST is responsible for developing information security standards and guidelines, including minimum requirements for federal information systems, but such standards and guidelines shall not apply to national security systems without the express approval of appropriate federal officials exercising policy authority over such systems. This guideline is consistent with the requirements of the Office of Management and Budget (OMB) Circular A-130. Nothing in this publication should be taken to contradict the standards and guidelines made mandatory and binding on federal agencies by the Secretary of Commerce under statutory authority. Nor should these guidelines be interpreted as altering or superseding the existing authorities of the Secretary of Commerce, Director of the OMB, or any other federal official. This publication may be used by nongovernmental organizations on a voluntary basis and is not subject to copyright in the United States. Attribution would, however, be appreciated by NIST. National Institute of Standards and Technology Special Publication 800-182 Natl. Inst. Stand. Technol. Spec. Publ. 800-182, 120 pages (July 2016) CODEN: NSPUE2 This publication is available free of charge from: http://dx.doi.org/10.6028/NIST.SP.800-182 REPORTS ON COMPUTER SYSTEMS TECHNOLOGY The Information Technology Laboratory (ITL) at the National Institute of Standards and Technology (NIST) promotes the U.S. economy and public welfare by providing technical leadership for the Nation’s measurement and standards infrastructure. ITL develops tests, test methods, reference data, proof of concept implementations, and technical analyses to advance the development and productive use of information technology. ITL’s responsibilities include the development of management, administrative, technical, and physical standards and guidelines for the cost-effective security and privacy of other than national security-related information in federal information systems. The Special Publication 800-series reports on ITL’s research, guidelines, and outreach efforts in information system security, and its collaborative activities with industry, government, and academic organizations. i COMPUTER SECURITY DIVISION ANNUAL REPORT | 2015 ACKNOWLEDGMENTS The editor, Patrick O’Reilly of the Computer Security Division, wishes to thank his colleagues in the Computer Security Division, who provided write-ups on their 2015 project highlights and accomplishments for this annual report (their names are mentioned after each project write-up). The editor would also like to acknowledge Elaine Barker (CSD), Lisa Carnahan (Standards Coordination Office, NIST), Greg Witte and Larry Feldman (G2) for reviewing and providing valuable feedback for this annual report. The editor would also like to acknowledge Kristen Dill of Dill and Company, Inc. for designing the cover and inside layout for this 2015 annual report. DISCLAIMER Any mention of commercial products or organizations is for informational purposes only; it is not intended to imply recommendation or endorsement by the National Institute of Standards and Technology, nor is it intended to imply that the products identified are necessarily the best available for the purpose. TRADEMARK INFORMATION All names are trademarks or registered trademarks of their respective owners. ii THIS PUBLICATION IS AVAILABLE FREE OF CHARGE FROM: ACKNOWLEDGMENTS | FY 2015 http://dx.doi.org/10.6028/NIST.SP.800-182 TABLE OF CONTENTS DISCLAIMER ..................................................................................................................................................................................IV ACKNOWLEDGMENTS ...................................................................................................................................................................V TRADEMARK INFORMATION .........................................................................................................................................................V WELCOME LETTER ..........................................................................................................................................................................1 COMPUTER SECURITY DIVISION (CSD) ORGANIZATION ............................................................................................................ 2 INTRODUCTION TO CSD’S FIVE GROUPS ..................................................................................................................................... 3 Cryptographic Technology Group (CTG)................................................................................................................................................................... 4 Security Components and Mechanisms Group (SCMG) .................................................................................................................. 4 Secure Systems and Applications Group (SSAG) ..............................................................................................................................5 Security Outreach and Integration Group (SOIG) ............................................................................................................................ 6 Security Testing, Validation, and Measurement Group (STVMG) ....................................................................................................7 CSD IMPLEMENTS FEDERAL INFORMATION SECURITY MANAGEMENT ACT ............................................................................ 8 PROGRAM AND PROJECT ACHIEVEMENTS FOR FY 2015 .......................................................................................................... 11 NIST RESPONSIBILITIES UNDER EXECUTIVE ORDER 13636, “IMPROVING CRITICAL INFRASTRUCTURE CYBERSECURITY” .12 CSD WORK IN NATIONAL AND INTERNATIONAL STANDARDS .................................................................................................13 Identity Management Standards within INCITS B10 and ISO JTC1/SC17 ................................................................................................................................15 Cloud Computing Standards Developed by ISO/IEC JTC 1/SC 38 Cloud Computing and INCITS Cloud 38 ................................16 ISO Standardization of Security Requirements for Cryptographic Modules.............................................................................................16 FEDERAL INFORMATION SECURITY MANAGEMENT ACT (FISMA) IMPLEMENTATION PROJECT ...........................................18 BIOMETRIC STANDARDS AND ASSOCIATED CONFORMITY ASSESSMENT TESTING TOOLS .................................................20 SECURITY OF CYBER-PHYSICAL SYSTEMS (CPS) ..................................................................................................................... 22 FEDERAL CYBERSECURITY RESEARCH & DEVELOPMENT (R&D) ............................................................................................ 23 SECURITY ASPECTS OF ELECTRONIC VOTING .......................................................................................................................... 23 HEALTH INFORMATION TECHNOLOGY SECURITY .....................................................................................................................24 SUPPLY CHAIN RISK MANAGEMENT (SCRM) FOR INFORMATION AND COMMUNICATIONS TECHNOLOGY (ICT) ............... 25 NATIONWIDE PUBLIC SAFETY BROADBAND NETWORK (NPSBN) CYBERSECURITY ............................................................ 26 SMART GRID CYBERSECURITY ................................................................................................................................................... 27 CYBERSECURITY AWARENESS, TRAINING, EDUCATION, AND OUTREACH ............................................................................ 28 National Initiative for Cybersecurity Education (NICE)................................................................................................................. 28 Computer Security Resource Center (CSRC) .................................................................................................................................. 29 Federal Computer Security Managers’ (FCSM) Forum .................................................................................................................. 29 Federal Information Systems Security Educators’ Association (FISSEA) ...................................................................................30 Information Security and Privacy Advisory Board (ISPAB) .........................................................................................................
Recommended publications
  • Openpgp Card Application User Guide

    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.
  • An Architecture for Cryptography with Smart Cards and NFC Rings on Android

    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.
  • Applying Mix Nets to Email Document

    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 .
  • Gnuk — a Free Software USB Token Implementation Niibe Yutaka

    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
  • Metadefender Core V4.17.3

    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.
  • Gnuk — an Openpgp USB Token Implementation Niibe Yutaka &lt;Gniibe@Fsij.Org&gt;

    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
  • IDOL Connector Framework Server 12.0 Administration Guide

    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.
  • Scdaemon — a New Framework for Smart Card Access

    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.
  • PGP-Zertifikate: Des Signaturrechts Vergessene Kinder?

    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
  • Security Architecture for Smart Hubs

    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.
  • The Enigmail Handbook V1.0.0

    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
  • 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

    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.