LISP Data-Plane Cryptography Draft-Ietf-Lisp-Crypto-01

Total Page：16

File Type：pdf, Size：1020Kb

LISP Data-Plane Cryptography draft-ietf-lisp-crypto-01 LISP Working Group - Prague IETF July 2015 Dino Farinacci & Brian Weis Document Status • Presented ideas in LISP WG at Vancouver fall 2013 • Seek advice from SAAG at Vancouver fall 2013 • Present -00 individual submission draft in London spring 2014 • lispers.net implementation spring 2014 • Present -01 and implementation • Toronto summer 2014 & Honolulu fall 2014 • Created working group draft -00 Jan 2015 • Presented update Dallas spring 2015 • Lots of technical discussion on key sizes, cipher suites, IVs, and ICVs • Led to -01 update in May 2015 where security expert added as co-author (Brian) 2 Design Overview • Difﬁe-Hellman exchange via Map-Request/Map-Reply • Keys not stored by third-party • Keys are ephemeral • ITR encrypt-n-encap -> ETR decap-n-decrypt • Rekeying part of RLOC-probing 3 What We Added in -01 • Initialization Vector (IV) to the start of payload • Integrity Check Veriﬁcation (ICV) at end of payload • Use Authenticated Encryption with Additional Data (AEAD) • Have DH secret key as input to a KDF that produces an encryption-key and integrity-key • Add cipher suite values which are negotiated in the Map- Request/Map-Reply exchange 4 Packet Format 5 Implementation Status • lispers.net has a -01 implementation • Used ECDH instead of regular DH: • RFC5114 gx value from the “192-bit Random ECP Group” • Supports rekeying via RLOC-probing • Support for unidirectional encryption across NATs • RTR to xTR-behind NAT as well as xTR-behind-NAT to RTR 6 lisp-crypto Example plaintext ciphertext xTR1 NAT RTR Internet NAT xTR Home Network Cloud Provider EID 1.1.1.1 EID 5.5.5.5 key-exchange ping 7 lisp-crypto Key Exchange 8 lisp-crypto Encrypt/Decrypt plaintext xTR1 NAT RTR ciphertext RTR NAT xTR 9 Implementation Todo List • Key Related Testing • Larger keys, other ECDH groups, and other ciphers • Multi-key rekeying logic • Multi-Feature Testing • Test multicast in unicast encapsulation • Test with LISP-SEC • Interoperability Testing • Making a call for more implementations • How about lispmob and open source the code? 10 Questions? 11.

Copy Link

Recommended publications

Authentication in Key-Exchange: Definitions, Relations and Composition
Authentication in Key-Exchange: Definitions, Relations and Composition Cyprien Delpech de Saint Guilhem1;2, Marc Fischlin3, and Bogdan Warinschi2 1 imec-COSIC, KU Leuven, Belgium 2 Dept Computer Science, University of Bristol, United Kingdom 3 Computer Science, Technische UniversitätDarmstadt, Germany [email protected], [email protected], [email protected] Abstract. We present a systematic approach to define and study authentication notions in authenti- cated key-exchange protocols. We propose and use a flexible and expressive predicate-based definitional framework. Our definitions capture key and entity authentication, in both implicit and explicit vari- ants, as well as key and entity confirmation, for authenticated key-exchange protocols. In particular, we capture critical notions in the authentication space such as key-compromise impersonation resis- tance and security against unknown key-share attacks. We first discuss these definitions within the Bellare{Rogaway model and then extend them to Canetti{Krawczyk-style models. We then show two useful applications of our framework. First, we look at the authentication guarantees of three representative protocols to draw several useful lessons for protocol design. The core technical contribution of this paper is then to formally establish that composition of secure implicitly authenti- cated key-exchange with subsequent confirmation protocols yields explicit authentication guarantees. Without a formal separation of implicit and explicit authentication from secrecy, a proof of this folklore result could not have been established. 1 Introduction The commonly expected level of security for authenticated key-exchange (AKE) protocols comprises two aspects. Authentication provides guarantees on the identities of the parties involved in the protocol execution.
[Show full text]
2.3 Diffie–Hellman Key Exchange
2.3. Di±e{Hellman key exchange 65 q q q q q q 6 q qq q q q q q q 900 q q q q q q q qq q q q q q q q q q q q q q q q q 800 q q q qq q q q q q q q q q qq q q q q q q q q q q q 700 q q q q q q q q q q q q q q q q q q q q q q q q q q qq q 600 q q q q q q q q q q q q qq q q q q q q q q q q q q q q q q q qq q q q q q q q q 500 q qq q q q q q qq q q q q q qqq q q q q q q q q q q q q q qq q q q 400 q q q q q q q q q q q q q q q q q q q q q q q q q 300 q q q q q q q q q q q q q q q q q q qqqq qqq q q q q q q q q q q q 200 q q q q q q q q q q q q q q q q q q q q q q q q q q q q q q q q qq q q qq q q 100 q q q q q q q q q q q q q q q q q q q q q q q q q 0 q - 0 30 60 90 120 150 180 210 240 270 Figure 2.2: Powers 627i mod 941 for i = 1; 2; 3;::: any group and use the group law instead of multiplication.
[Show full text]
Elliptic Curves in Public Key Cryptography: the Diffie Hellman
Elliptic Curves in Public Key Cryptography: The Diffie Hellman Key Exchange Protocol and its relationship to the Elliptic Curve Discrete Logarithm Problem Public Key Cryptography Public key cryptography is a modern form of cryptography that allows different parties to exchange information securely over an insecure network, without having first to agree upon some secret key. The main use of public key cryptography is to provide information security in computer science, for example to transfer securely email, credit card details or other secret information between sender and recipient via the internet. There are three steps involved in transferring information securely from person A to person B over an insecure network. These are encryption of the original information, called the plaintext, transfer of the encrypted message, or ciphertext, and decryption of the ciphertext back into plaintext. Since the transfer of the ciphertext is over an insecure network, any spy has access to the ciphertext and thus potentially has access to the original information, provided he is able to decipher the message. Thus, a successful cryptosystem must be able encrypt the original message in such a way that only the intended receiver can decipher the ciphertext. The goal of public key cryptography is to make the problem of deciphering the encrypted message too difficult to do in a reasonable time (by say brute-force) unless certain key facts are known. Ideally, only the intended sender and receiver of a message should know these certain key facts. Any certain piece of information that is essential in order to decrypt a message is known as a key.
[Show full text]
Study on the Use of Cryptographic Techniques in Europe
Study on the use of cryptographic techniques in Europe [Deliverable – 2011-12-19] Updated on 2012-04-20 II Study on the use of cryptographic techniques in Europe Contributors to this report Authors: Edward Hamilton and Mischa Kriens of Analysys Mason Ltd Rodica Tirtea of ENISA Supervisor of the project: Rodica Tirtea of ENISA ENISA staff involved in the project: Demosthenes Ikonomou, Stefan Schiffner Agreements or Acknowledgements ENISA would like to thank the contributors and reviewers of this study. Study on the use of cryptographic techniques in Europe III About ENISA The European Network and Information Security Agency (ENISA) is a centre of network and information security expertise for the EU, its member states, the private sector and Europe’s citizens. ENISA works with these groups to develop advice and recommendations on good practice in information security. It assists EU member states in implementing relevant EU leg- islation and works to improve the resilience of Europe’s critical information infrastructure and networks. ENISA seeks to enhance existing expertise in EU member states by supporting the development of cross-border communities committed to improving network and information security throughout the EU. More information about ENISA and its work can be found at www.enisa.europa.eu. Contact details For contacting ENISA or for general enquiries on cryptography, please use the following de- tails: E-mail: [email protected] Internet: http://www.enisa.europa.eu Legal notice Notice must be taken that this publication represents the views and interpretations of the au- thors and editors, unless stated otherwise. This publication should not be construed to be a legal action of ENISA or the ENISA bodies unless adopted pursuant to the ENISA Regulation (EC) No 460/2004 as lastly amended by Regulation (EU) No 580/2011.
[Show full text]
Public Key Infrastructure (PKI)
Public Key Infrastructure Public Key Infrastructure (PKI) Neil F. Johnson [email protected] http://ise.gmu.edu/~csis Assumptions • Understanding of – Fundamentals of Public Key Cryptosystems – Hash codes for message digests and integrity check – Digital Signatures Copyright 1999, Neil F. Johnson 1 Public Key Infrastructure Overview • Public Key Cryptosystems – Quick review – Cryptography – Digital Signatures – Key Management Issues • Certificates – Certificates Information – Certificate Authority – Track Issuing a Certificate • Putting it all together – PKI applications – Pretty Good Privacy (PGP) – Privacy Enhanced Mail (PEM) Public Key Cryptosystems – Quick Review • Key distribution problem of secret key systems – You must share the secret key with another party before you can initiate communication – If you want to communicate with n parties, you require n different keys • Public Key cryptosystems solve the key distribution problem in secret key systems (provided a reliable channel for communication of public keys can be implemented) • Security is based on the unfeasibility of computing B’s private key given the knowledge of – B’s public key, – chosen plaintext, and – maybe chosen ciphertext Copyright 1999, Neil F. Johnson 2 Public Key Infrastructure Key Distribution (n)(n-1) 2 Bob Bob Alice 1 Alice 2 Chris Chris 7 5 8 9 Ellie 3 Ellie 6 David 4 David Secret Key Distribution Directory of Public Keys (certificates) Public Key Cryptosystem INSECURE CHANNEL Plaintext Ciphertext Plaintext Encryption Decryption Algorithm Algorithm Bob’s PUBLIC
[Show full text]
Analysing and Patching SPEKE in ISO/IEC
1 Analysing and Patching SPEKE in ISO/IEC Feng Hao, Roberto Metere, Siamak F. Shahandashti and Changyu Dong Abstract—Simple Password Exponential Key Exchange reported. Over the years, SPEKE has been used in several (SPEKE) is a well-known Password Authenticated Key Ex- commercial applications: for example, the secure messaging change (PAKE) protocol that has been used in Blackberry on Blackberry phones [11] and Entrust’s TruePass end-to- phones for secure messaging and Entrust’s TruePass end-to- end web products. It has also been included into international end web products [16]. SPEKE has also been included into standards such as ISO/IEC 11770-4 and IEEE P1363.2. In the international standards such as IEEE P1363.2 [22] and this paper, we analyse the SPEKE protocol as speciﬁed in the ISO/IEC 11770-4 [24]. ISO/IEC and IEEE standards. We identify that the protocol is Given the wide usage of SPEKE in practical applications vulnerable to two new attacks: an impersonation attack that and its inclusion in standards, we believe a thorough allows an attacker to impersonate a user without knowing the password by launching two parallel sessions with the victim, analysis of SPEKE is both necessary and important. In and a key-malleability attack that allows a man-in-the-middle this paper, we revisit SPEKE and its variants speciﬁed in (MITM) to manipulate the session key without being detected the original paper [25], the IEEE 1363.2 [22] and ISO/IEC by the end users. Both attacks have been acknowledged by 11770-4 [23] standards.
[Show full text]
Lecture 19: Public-Key Cryptography (Diffie-Hellman Key Exchange & Elgamal Encryption)
Lecture 19: Public-key Cryptography (Diffie-Hellman Key Exchange & ElGamal Encryption) Public-key Cryptography Recall In private-key cryptography the secret-key sk is always established ahead of time The secrecy of the private-key cryptography relies on the fact that the adversary does not have access to the secret key sk For example, consider a private-key encryption scheme $ 1 The Alice and Bob generate sk Gen() ahead of time 2 Later, when Alice wants to encrypt and send a message to Bob, she computes the cipher-text c = Encsk(m) 3 The eavesdropping adversary see c but gains no additional information about the message m 4 Bob can decrypt the message me = Decsk(c) 5 Note that the knowledge of sk distinguishes Bob from the eavesdropping adversary Public-key Cryptography Perspective If jskj >jmj, then we can construct private-key encryption schemes (like, one-time pad) that is secure even against adversaries with unbounded computational power If jskj = O(jmj"), where " 2 (0; 1) is a constant, then we can construction private-key encryption schemes using pseudorandom generators (PRGs) What if, jskj = 0? That is, what if Alice and Bob never met? How is “Bob” any different from an “adversary”? Public-key Cryptography In this Lecture We shall introduce the Decisional Diffie-Hellmann (DDH) Assumption and the Diffie-Hellman key-exchange protocol, We shall introduce the El Gamal (public-key) Encryption Scheme, and Finally, abstract out the principal design principles learned. Public-key Cryptography Decisional Diffie-Hellman (DDH) Computational Hardness AssumptionI Let (G; ◦) be a group of size N that is generated by g.
[Show full text]
Analysis of Key-Exchange Protocols and Their Use for Building Secure Channels
Analysis of Key-Exchange Protocols and Their Use for Building Secure Channels Ran Canetti1 and Hugo Krawczyk2, 1 IBM T.J. Watson Research Center, Yorktown Heights, New York 10598. [email protected] 2 EE Department, Technion, Haifa, Israel. [email protected] Abstract. We present a formalism for the analysis of key-exchange pro- tocols that combines previous definitional approaches and results in a definition of security that enjoys some important analytical benefits: (i) any key-exchange protocol that satisfies the security definition can be composed with symmetric encryption and authentication functions to provide provably secure communication channels (as defined here); and (ii) the definition allows for simple modular proofs of security: one can design and prove security of key-exchange protocols in an idealized model where the communication links are perfectly authenticated, and then translate them using general tools to obtain security in the realistic setting of adversary-controlled links. We exemplify the usability of our results by applying them to obtain the proof of two classes of key-exchange protocols, Diffie-Hellman and key-transport, authenticated via symmetric or asymmetric techniques. 1 Introduction Key-exchange protocols (ke, for short) are mechanisms by which two parties that communicate over an adversarially-controlled network can generate a com- mon secret key. ke protocols are essential for enabling the use of shared-key cryptography to protect transmitted data over insecure networks. As such they are a central piece for building secure communications (a.k.a “secure channels”), and are among the most commonly used cryptographic protocols (contemporary examples include SSL, IPSec, SSH, among others).
[Show full text]
Public Key Cryptography
Public Key Cryptography CSS 322 – Security and Cryptography History of Public Key Systems • Until public-key cryptosystems were discovered, cryptography relied on permutations and substitutions: – Caesar cipher, rotor machines, DES, … • Diffie and Hellman published a public key system in 1976. Their motivation: – Symmetric key systems rely heavily on KDC being trustworthy and secure – Digital signatures are important • Others (intelligence communities) claim to have discovered public key in 1960’s and early 1970’s CSS 322 - Public Key Cryptography 2 Public Key Encryption • Public key uses two different keys • Main concept: – Given the encryption key and algorithm, too hard to determine the decryption key CSS 322 - Public Key Cryptography 3 Public Key Encryption • Public key – Key used by sender to encrypt plaintext – Owned by the receiver – Anyone can know the public key • Private (Secret) Key – Key used to decrypt ciphertext – Must be kept secret by the receiver • The public key and private key are related – The pair belong to the receiver: (Public, Secret) or (P, S) CSS 322 - Public Key Cryptography 4 Symmetric vs Public Key Encryption •Symmetric • Public • Same algorithm with same key • One algorithm used for both used for encrypt and decrypt encrypt and decrypt • Sender and receiver must • One key used for encrypt and share algorithm and key another for decrypt • Key must be kept secret • Only one key must be secret CSS 322 - Public Key Cryptography 5 Privacy with Public Key Encryption Y = E(PUb,X) X = D(PRb,Y) CSS 322 - Public Key
[Show full text]
Schnorr-Based Implicit Certification
Schnorr-based implicit certification: improving the security and efficiency of V2X communications Paulo S. L. M. Barreto1, Marcos A. Simplicio Jr.2, Jefferson E. Ricardini2,3 and Harsh Kupwade Patil3 1 University of Washington Tacoma, USA, [email protected], 2 Escola Politécnica, Universidade de São Paulo, Brazil, {mjunior,joliveira}@larc.usp.br 3 LG Electronics, USA, [email protected] Abstract. In the implicit certification model, the process of verifying the validity of the signer’s public key is combined with the verification of the signature itself. When compared to traditional, explicit certificates, the main advantage of the im- plicit approach lies in the shorter public key validation data. This property is particularly important in resource-constrained scenarios where public key valida- tion is performed very often, which is common in vehicular communications (V2X) that employ pseudonym certificates. In this article, we show that an alternative, Schnorr-based implicit certification procedure can improve the efficiency of a popular V2X-oriented pseudonym certificate provisioning approach, the (unified) butterfly key expansion. As an additional contribution, we show that butterfly keys are vulnerable to existential forgery attacks under certain conditions, and also discuss how this issue can be fixed in an effective and efficient manner. Keywords: Vehicular communications (V2X) · implicit certificates · butterfly key expansion · security 1 Introduction Public key authentication is the cornerstone for any security system that relies on pub- lic/private key pairs for digital signature, key exchange and/or asymmetric encryption. Traditionally, this is accomplished by means of explicit certificates, digital documents that enclose the subject’s public key and are signed by a trusted Certificate Authority (CA).
[Show full text]
New Key Exchange Protocol Based on Mandelbrot and Julia Fractal Sets Mohammad Ahmad Alia and Azman Bin Samsudin
302 IJCSNS International Journal of Computer Science and Network Security, VOL.7 No.2, February 2007 New Key Exchange Protocol Based on Mandelbrot and Julia Fractal Sets Mohammad Ahmad Alia and Azman Bin Samsudin, School of Computer Sciences, Universiti Sains Malaysia. Summary by using two keys, a private and a public key. In most In this paper, we propose a new cryptographic key exchange cases, by exchanging the public keys, both parties can protocol based on Mandelbrot and Julia Fractal sets. The Fractal calculate a unique shared key, known only to both of them based key exchange protocol is possible because of the intrinsic [2, 3, 4]. connection between the Mandelbrot and Julia Fractal sets. In the proposed protocol, Mandelbrot Fractal function takes the chosen This paper proposed a new Fractal (Mandelbrot and private key as the input parameter and generates the corresponding public key. Julia Fractal function is then used to Julia Fractal sets) key exchange protocol as a method to calculate the shared key based on the existing private key and the securely agree on a shared key. The proposed method received public key. The proposed protocol is designed to be achieved the secure exchange protocol by creating a resistant against attacks, utilizes small key size and shared secret through the use of the Mandelbrot and Julia comparatively performs faster then the existing Diffie-Hellman Fractal sets. key exchange protocol. The proposed Fractal key exchange protocol is therefore an attractive alternative to traditional 2.1. Fractals number theory based key exchange protocols. A complex number consists of a real and an imaginary Key words: Fractals Cryptography, Key- exchange protocol, Mandelbrot component.
[Show full text]
Example:The Diffie-Hellman Key Exchange
Extreme minimality: Implicitly Authenticated KE Protocols 1 A natural Authenticated DH Solution (ISO 9796) A B A, gx y x y B, g , SIGB(g ,g ,A) y x SIGA(g ,g ,B) Simple, but 3 messages plus signatures [and certificates] 2 The quest for Authenticated DH What is the inherent cost of authentication in Diffie-Hellman? In terms of Communication: number of messages, group elements, authentication information, actual message size Computation: algebraic operations and actual speed Security: What can we prove? How close can we get to the fundamental limits? And still prove security… 3 Implicitly Authenticated DH A A, gx B B, gy Authentication via session key computation No transmitted signatures, MAC values, etc Session key must involve long-term and ephemeral keys: x y K=F(PKA,PKB,SKA,SKB ,g ,g ,x,y) Ability to compute key authentication The simpler the trickier: many insecure proposals 4 (Abuse of) Notation Public key of A (resp. B) denoted A=ga (resp. B=gb) A A=ga, X=gx B B=gb, Y=gy 5 Some Ideas Can we really have a non-replayable 2-msg protocol? x x y y Remember AB: g , SIGA(g ,B), AB: g , SIGB(g ,A) insecurity Combining A, B, X, Y: K=H(gab, gxy): Open to known key and interleaving attacks K=H(gab, gxy, gx, gy) works but open to “KCI attacks” (a general weakness of protocols with gab ) We want that no attack except if learning pair (x,a) or (y,b) Idea: K = g(a+x)(b+y) (computed by A as (BY)a+x, by B as (AX)b+y) Doesn’t work: Attacker sends X*=gx*/A, B sends Y, K=(BY)x* (no need to know A) 6 MQV Idea: set K = g(a+dx)(b+ey) and define d, e so that attacker cannot control e and Y, or d and X MQV: d=half bits of X, e=half bits of Y Does not quite work But a simple variation does 7 The HMQV Protocol 8 The HMQV Protocol Basic DH + special key computation * Notation: G=<g> of prime order q; g in supergroup G’ (eg.
[Show full text]