Towards a Verifiably Secure Quantum-Resistant Key Exchange
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Efficient, Dos-Resistant, Secure Key Exchange
Efficient, DoS-Resistant, Secure Key Exchange for Internet Protocols∗ William Aiello Steven M. Bellovin Matt Blaze AT&T Labs Research AT&T Labs Research AT&T Labs Research [email protected] [email protected] [email protected] Ran Canetti John Ioannidis Angelos D. Keromytis IBM T.J. Watson Research Center AT&T Labs Research Columbia University [email protected] [email protected] [email protected] Omer Reingold AT&T Labs Research [email protected] Categories and Subject Descriptors While it might be possible to “patch” the IKE protocol to fix C.2.0 [Security and Protection]: Key Agreement Protocols some of these problems, it may be perferable to construct a new protocol that more narrorwly addresses the requirements “from the ground up.” We set out to engineer a new key exchange protocol General Terms specifically for Internet security applications. We call our new pro- Security, Reliability, Standardization tocol “JFK,” which stands for “Just Fast Keying.” Keywords 1.1 Design Goals We seek a protocol with the following characteristics: Cryptography, Denial of Service Attacks Security: No one other than the participants may have access to ABSTRACT the generated key. We describe JFK, a new key exchange protocol, primarily designed PFS: It must approach Perfect Forward Secrecy. for use in the IP Security Architecture. It is simple, efficient, and secure; we sketch a proof of the latter property. JFK also has a Privacy: It must preserve the privacy of the initiator and/or re- number of novel engineering parameters that permit a variety of sponder, insofar as possible. -
Network Access Control and Cloud Security
Network Access Control and Cloud Security Raj Jain Washington University in Saint Louis Saint Louis, MO 63130 [email protected] Audio/Video recordings of this lecture are available at: http://www.cse.wustl.edu/~jain/cse571-17/ Washington University in St. Louis http://www.cse.wustl.edu/~jain/cse571-17/ ©2017 Raj Jain 16-1 Overview 1. Network Access Control (NAC) 2. RADIUS 3. Extensible Authentication Protocol (EAP) 4. EAP over LAN (EAPOL) 5. 802.1X 6. Cloud Security These slides are based partly on Lawrie Brown’s slides supplied with William Stallings’s book “Cryptography and Network Security: Principles and Practice,” 7th Ed, 2017. Washington University in St. Louis http://www.cse.wustl.edu/~jain/cse571-17/ ©2017 Raj Jain 16-2 Network Access Control (NAC) AAA: Authentication: Is the user legit? Supplicant Authenticator Authentication Server Authorization: What is he allowed to do? Accounting: Keep track of usage Components: Supplicant: User Authenticator: Network edge device Authentication Server: Remote Access Server (RAS) or Policy Server Backend policy and access control Washington University in St. Louis http://www.cse.wustl.edu/~jain/cse571-17/ ©2017 Raj Jain 16-3 Network Access Enforcement Methods IEEE 802.1X used in Ethernet, WiFi Firewall DHCP Management VPN VLANs Washington University in St. Louis http://www.cse.wustl.edu/~jain/cse571-17/ ©2017 Raj Jain 16-4 RADIUS Remote Authentication Dial-In User Service Central point for Authorization, Accounting, and Auditing data ⇒ AAA server Network Access servers get authentication info from RADIUS servers Allows RADIUS Proxy Servers ⇒ ISP roaming alliances Uses UDP: In case of server failure, the request must be re-sent to backup ⇒ Application level retransmission required TCP takes too long to indicate failure Proxy RADIUS RADIUS Network Remote Access User Customer Access ISP Net Server Network Server Ref: http://en.wikipedia.org/wiki/RADIUS Washington University in St. -
Lecture 12: Security Systems Using Public Keys 11.1 PGP 11.2 SSL/TLS 11.3 IPSEC Stallings: Ch 16,17
T-79.4501 Cryptography and Data Security Lecture 12: Security systems using public keys 11.1 PGP 11.2 SSL/TLS 11.3 IPSEC Stallings: Ch 16,17 1 Pretty Good Privacy • Email encryption program • Bottom–up approach to the distribution of trust • Each user acts as his/her own CA and signs the public keys of other users • User can accept authenticity of a public key based on recommendation by a third trusted user • RSA public key encryption used for distribution of session keys *) • Digital signatures produced by RSA or DSA signature algorithms • Hash functions are MD5 and SHA-1 • Symmetric encryption performed using IDEA in CFB mode (self- synchronising stream cipher) • Public keys held in ”Key-ring” • Revocation of public keys is a problem *) A data encryption protocol, where the data is encrypted using symmetric encryption, and the symmetric encryption key is encrypted using public key encryption, is called as ”hybrid encryption” 2 1 Secure Sockets Layer /Transport Layer Security • SSL (by Netscape) adds security to the TCP level of the Internet Protocol stack • Reliable end-to-end service. • TLS developed by IETF is basically equivalent to SSL v 3.1 Structure: SSL SSL Change SSL Handshake Cipher Spec Alert HTTP Protocol Protocol Protocol SSL Record Protocol TCP IP • Hypertext Transfer Protocol (Web client/server interaction) can operate on top of SSL (https://...) 3 SSL Record Protocol Application data fragment compressed fragment MAC added encrypted SSL record header appended 4 2 SSL Record Protocol Crypto • The MAC is similar to HMAC (indeed, an early version of HMAC) with the difference that OPAD and IPAD fields are concatenated to the key data (not xored as in HMAC). -
Nist Sp 800-77 Rev. 1 Guide to Ipsec Vpns
NIST Special Publication 800-77 Revision 1 Guide to IPsec VPNs Elaine Barker Quynh Dang Sheila Frankel Karen Scarfone Paul Wouters This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-77r1 C O M P U T E R S E C U R I T Y NIST Special Publication 800-77 Revision 1 Guide to IPsec VPNs Elaine Barker Quynh Dang Sheila Frankel* Computer Security Division Information Technology Laboratory Karen Scarfone Scarfone Cybersecurity Clifton, VA Paul Wouters Red Hat Toronto, ON, Canada *Former employee; all work for this publication was done while at NIST This publication is available free of charge from: https://doi.org/10.6028/NIST.SP.800-77r1 June 2020 U.S. Department of Commerce Wilbur L. Ross, Jr., Secretary National Institute of Standards and Technology Walter Copan, NIST Director and Under Secretary of Commerce for Standards and Technology 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. § 3551 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. -
Guidelines for the Secure Deployment of Ipv6
Special Publication 800-119 Guidelines for the Secure Deployment of IPv6 Recommendations of the National Institute of Standards and Technology Sheila Frankel Richard Graveman John Pearce Mark Rooks NIST Special Publication 800-119 Guidelines for the Secure Deployment of IPv6 Recommendations of the National Institute of Standards and Technology Sheila Frankel Richard Graveman John Pearce Mark Rooks C O M P U T E R S E C U R I T Y Computer Security Division Information Technology Laboratory National Institute of Standards and Technology Gaithersburg, MD 20899-8930 December 2010 U.S. Department of Commerce Gary Locke, Secretary National Institute of Standards and Technology Dr. Patrick D. Gallagher, Director GUIDELINES FOR THE SECURE DEPLOYMENT OF IPV6 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 analysis to advance the development and productive use of information technology. ITL’s responsibilities include the development of technical, physical, administrative, and management standards and guidelines for the cost-effective security and privacy of sensitive unclassified information in Federal computer systems. This Special Publication 800-series reports on ITL’s research, guidance, and outreach efforts in computer security and its collaborative activities with industry, government, and academic organizations. National Institute of Standards and Technology Special Publication 800-119 Natl. Inst. Stand. Technol. Spec. Publ. 800-119, 188 pages (Dec. 2010) Certain commercial entities, equipment, or materials may be identified in this document in order to describe an experimental procedure or concept adequately. -
Nanosec™ ] Mocana’S Comprehensive Ipsec and Ikev1/V2 Solution with Integrated Certificate Management Functionality
Security of Things Connectivity [ NanoSec™ ] Mocana’s comprehensive IPsec and IKEv1/v2 solution with integrated certificate management functionality. Features & Benefits • Small footprint, high performance • Full NIST USGv6 compliant implementation of IETF IPsec version 3 • FIPS 140-2 Level 1 validated (optional) • Guaranteed “GPL-Free” code protects your • Complete IPSec & IKEv1/v2 solution with intellectual property certificate management • Zero-threaded, asynchronous architecture • Dramatically speeds integration & testing of IPsec and certificate management • Expert development support from Mocana engineers •NIST-Approved “Suite B” cryptography included IPsec/IKE is a standard designed by IETF to provide interoperable, high quality, cryptographically- based security for IP communication. It’s useful for providing authentication (to ensure peers are communicating with the intended trusted parties), data confidentiality (to ensure data cannot be read in transit) and message integrity (to ensure traffic has not been altered in transit). These security services are provided at the IP layer, offering protection to all the protocols carried over PI . IPsec provides a great deal of flexibility and granular control over the security services offered. The most popular application of IPsec is the VPN (Virtual Private Network) which creates a secure encrypted “tunnel” over the unsecured Internet. Once a VPN is established, the two ends can run virtually any data, voice and video application securely. IPsec is terrific for reducing the threat of packet sniffers or man-in-the-middle attacks. Unfortunately, most IPsec packages are designed for PC’s, not embedded devices. That means that they can be somewhat unwieldy in memory-constrained device environments...and the performance of typical commercial or open-source IPsec offerings can be pretty disappointing, as well. -
Linux Ipsec Tutorial
Linux IPsec Tutorial Sowmini Varadhan (Oracle) & Paul Wouters (Redhat) Netdev0x12, July 2018, Montreal, Canada Agenda • Background: brief introduction to IPsec and IKE terminology • IPsec datapath walk-through: trace the life of a UDP packet for the transmit and receive path as it passes through the Linux kernel’s network stack (Sowmini Varadhan) • IPsec control plane walk-through: everything you wanted to know about the IKE control plane (Paul Wouters) Netdev0x12, July 2018, Montreal, Canada First, a review of IPsec/IKE terminology/definitions Netdev0x12, July 2018, Montreal, Canada What is IPsec? • IP Security • Suite of protocols for encryption (adding a “ESP” header) and Authentication (adding a “AUTH” header) • Encryption parameters (e.g., key, algorithm) are determined from two databases: – Security Policy database (SPD) – Security Association database (SADB) Netdev0x12, July 2018, Montreal, Canada SPD and SADB • SPD: Security Policy Database – What must be done: e.g., “for packets in 13.0.0.0/24, perform IPsec ESP processing”, “discard packets in 192.168.0.0/16” – Multiple transforms may be specified, e.g., “for packets from 12.0.0.1→12.0.0.2, apply ESP, then apply compression” – May need to create/lookup a Security Association to perform the action defined the SPD entry • SADB: Security Association Database – How to apply the security transform(s): e.g., “for packets from 13.0.0.1 → 13.0.0.2, apply AES-GCM-256 with the key 0x1234.. and a 128 bit IV” – IKE (Internet Key Exchange) protocol for negotiating and establishing SADB parameters -
Implementation of Ipv6 in Internet Key Exhange Version 2
Implementation of IPv6 in Internet Key Exhange version 2 Marko Salkić, Stjepan Groš, Vlado Glavinić Department of Electronics, Microelectronics, Computer and Intelligent Systems Faculty of Electrical Engineering and Computing Address: Unska 3, 10000 Zagreb, Croatia Telephone: +385 1 6129-935 E-mail: [email protected] Summary ± IKEv2 is a protocol for key exchange in Internet concluded in section five, followed by a list of references security architecture. We have implemented first, stripped- in section six. down version of IKEv2 that supported only IPv4 addresses. The implementation had some provisions that have been introduced in order to make later implementation of IPv6 II. IKEV2 PROTOCOL easier. Currently, we are extending IKEv2 implementation with missing functionality in order to make it fully IP security (IPsec) is a suite of security protocols and functional. In this paper we describe implementation details open standards developed by the Internet Engineering of IPv6 introduction into IKEv2 protocol implementation. Task Force (IETF) for secure transmission over unprotected networks, such as Internet. IPsec is required I. INTRODUCTION for IPv6 and optional for IPv4, but has not yet been widely deployed. Using cryptographic security services, IPsec IPv4 address architecture [1] is currently dominating provides confidentiality, data integrity, authenticity and on the Internet. This version has been in use for over 20 availability. Setting the parameters of an IPsec security years and during this period of time many deficiencies association (SA) manually does not scale well [4], so were discovered and identified. This led to a new version, another protocol ± Internet Key Exchange (IKE) ± is used IPv6 architecture [2], that has been in active development to automate and enhance negotiation of parameters and for over a decade. -
Subliminal Channels in High-Speed Signatures
Die approbierte Originalversion dieser Diplom-/ Masterarbeit ist in der Hauptbibliothek der Tech- nischen Universität Wien aufgestellt und zugänglich. http://www.ub.tuwien.ac.at institute of telecommunications The approved original version of this diploma or master thesis is available at the main library of the Vienna University of Technology. http://www.ub.tuwien.ac.at/eng Subliminal Channels in High-Speed Signatures Master’s Thesis for obtaining the academic degree Diplom-Ingenieur as part of the study Electrical Engineering and Information Technology carried out by Alexander Hartl student number: 01125115 Institute of Telecommunications at TU Wien Supervision: Univ. Prof. Dipl.-Ing. Dr.-Ing. Tanja Zseby Dipl.-Ing. Robert Annessi, B.Sc Acknowledgments I want to express my gratitude for everyone who assisted or encouraged me in various ways during my studies. In particular, I would like to thank Prof. Tanja Zseby and Dipl.-Ing. Robert Annessi for giving me the opportunity to write this thesis, for supporting me actively while I was working on it and for many valuable comments and suggestions. I owe special thanks to my family, especially my parents Edith and Rudolf, for their endless support during all these years. Thank you, Sabrina, for encouraging me and for so many cheerful hours in my life. Abstract One of the fundamental building blocks for achieving security in data networks is the use of digital signatures. A digital signature is a bit string which allows the receiver of a message to ensure that the message indeed originated from the apparent sender and has not been altered along the path. -
Cryptography and Public Key Infrastructure on the Internet
Cryptography and Public Key Infrastructure on the Internet Klaus Schmeh Gesellsschaft für IT-Sicherheit AG Bochum, Germany Cryptography and Public Key Infrastructure on the Internet Cryptography and Public Key Infrastructure on the Internet Klaus Schmeh Gesellsschaft für IT-Sicherheit AG Bochum, Germany Copyright © 2001 by dpunkt.verlag GmbH, Heidelberg, Germany. Title of the German original: Kryptografie und Publik-Key-Infrastrukturen im Internet. ISBN: 3 932588 90 8 English translation Copyright 2003 by John Wiley & Sons Ltd, The Atrium, Southern Gate, Chichester, West Sussex PO19 8SQ, England. All rights reserved National 01243 779777 International (+44) 1243 779777 e-mail (for orders and customer service enquiries): [email protected] Visit our Home Page on http://www.wileyeurope.com or http://www.wiley.com All Rights Reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, scanning or otherwise, except under the terms of the Copyright, Designs and Patents Act 1988 or under the terms of a licence issued by the Copyright Licensing Agency Ltd, 90 Tottenham Court Road, London W1T 4LP, UK, without the permission in writing of the Publisher, with the exception of any material supplied specifically for the purpose of being entered and executed on a computer system, for exclusive use by the purchaser of the publication. Requests to the Publisher should be addressed to the Permissions Department, John Wiley & Sons Ltd, The Atrium, Southern Gate, Chichester, West Sussex PO19 8SQ, England, or emailed to [email protected], or faxed to (+44) 1243 770571. -
225738Pre.Pdf
PDF hosted at the Radboud Repository of the Radboud University Nijmegen The following full text is a preprint version which may differ from the publisher's version. For additional information about this publication click this link. https://hdl.handle.net/2066/225738 Please be advised that this information was generated on 2021-09-27 and may be subject to change. Post-quantum TLS without handshake signatures Full version, May 7, 2020 Peter Schwabe Douglas Stebila Thom Wiggers Radboud University University of Waterloo Radboud University [email protected] [email protected] [email protected] ABSTRACT Client Server static (sig): pk(, sk( We present KEMTLS, an alternative to the TLS 1.3 handshake that TCP SYN uses key-encapsulation mechanisms (KEMs) instead of signatures TCP SYN-ACK for server authentication. Among existing post-quantum candidates, G $ Z@ signature schemes generally have larger public key/signature sizes 6G compared to the public key/ciphertext sizes of KEMs: by using an ~ $ Z@ IND-CCA-secure KEM for server authentication in post-quantum ss 6G~ TLS, we obtain multiple benefits. A size-optimized post-quantum KDF(ss) ~ instantiation of KEMTLS requires less than half the bandwidth of a 6 , AEAD (cert[pk( ]kSig(sk(, transcript)kkey confirmation) size-optimized post-quantum instantiation of TLS 1.3. In a speed- AEAD 0 (key confirmation) optimized instantiation, KEMTLS reduces the amount of server CPU AEAD 00 (application data) cycles by almost 90% compared to TLS 1.3, while at the same time AEAD 000 (application data) reducing communication size, reducing the time until the client can start sending encrypted application data, and eliminating code for Figure 1: High-level overview of TLS 1.3, using signatures signatures from the server’s trusted code base. -
Post-Quantum Authentication in TLS 1.3: a Performance Study
Post-Quantum Authentication in TLS 1.3: A Performance Study Dimitrios Sikeridis∗, Panos Kampanakisy, Michael Devetsikiotis∗ ∗ Dept. of Electrical and Computer Engineering, The University of New Mexico, Albuquerque, NM, USA ySecurity & Trust Organization, Cisco Systems, USA fdsike, [email protected], [email protected] Abstract—The potential development of large-scale quantum Apart from connection integrity and confidentiality, TLS computers is raising concerns among IT and security research provides authentication usually with the use of X.509 certifi- professionals due to their ability to solve (elliptic curve) discrete cates [45]. Such certificates are issued by trusted third-parties logarithm and integer factorization problems in polynomial time. called Certificate Authorities (CAs). Endpoints verify the All currently used public key algorithms would be deemed communicating peer’s identity and public key (PK) contained insecure in a post-quantum (PQ) setting. In response, the National inside his certificate by leveraging a chain of certificates that is Institute of Standards and Technology (NIST) has initiated a pro- rooted to a pre-trusted root CA. The two most popular digital cess to standardize quantum-resistant crypto algorithms, focusing primarily on their security guarantees. Since PQ algorithms signature algorithms used in certificates today are the Elliptic present significant differences over classical ones, their overall Curve Digital Signature (ECDSA) and RivestShamirAdleman evaluation should not be performed out-of-context. This work (RSA). Their security guaranties rely on the hardness of the presents a detailed performance evaluation of the NIST signa- elliptic curve discrete logarithm (ECDL) and integer factoriza- ture algorithm candidates and investigates the imposed latency tion (IF) problems respectively.