DOCSLIB.ORG

PKCS #11 Cryptographic Token Interface Current Mechanisms Specification Version 3.00

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
PKCS #11 Cryptographic Token Interface Current Mechanisms Specification Version 3.00 1 2 PKCS #11 Cryptographic Token Interface 3 Current Mechanisms Specification Version 4 3.0 5 Working Draft 110 Rev. 2 6 728 May 2019 7 Technical Committee: 8 OASIS PKCS 11 TC 9 Chairs: 10 Robert Relyea ([email protected]), Red Hat 11 Tony Cox ([email protected]), Cryptsoft 12 Editor: 13 Chris Zimman ([email protected]), Individual 14 Dieter Bong ([email protected]), Utimaco 15 Additional artifacts: 16 This prose specification is one component of a Work Product that also includes the following 17 normative computer language definition files for PKCS #11 v3.0 rev01 18 include/pkcs11-v3.0/pkcs11.h 19 include/pkcs11-v3.0/pkcs11t.h 20 include/pkcs11-v3.0/pkcs11f.hThis prose specification is one component of a Work Product that Formatted: List Paragraph, Bulleted + Level: 1 + Aligned at: 21 also includes these computer language files: 0.63 cm + Indent at: 1.27 cm 22 pkcs11-curr-v30.h Formatted: List Paragraph, No bullets or numbering 23 Related work: 24 This specification replaces or supersedes: 25 PKCS #11 Cryptographic Token Interface Current Mechanisms Specification Version 2.40 26 Plus Errata 01. Edited by Susan Gleeson, Chris Zimman, Robert Griffin, Tim Hudson. OASIS 27 Standard. http://docs.oasis-open.org/pkcs11/pkcs11-base/v2.40/errata01/pkcs11-base-v2.40- 28 errata01-complete.html . 29 This specification is related to: 30 PKCS #11 Cryptographic Token Interface Base Specification Version 3.0 31 <URL> 32 PKCS #11 Cryptographic Token Interface Historical Mechanisms Specification Version 3.0 33 <URL> 34 PKCS #11 Cryptographic Token Interface Profiles Version 3.0 35 <URL>PKCS #11 Cryptographic Token Interface Base Specification Version 3.0. Edited by 36 Chris Zimman, Dieter Bong. Latest version. http://docs.oasis-open.org/pkcs11/pkcs11- 37 base/v2.41/pkcs11-base-v2.41.html. 38 PKCS #11 Cryptographic Token Interface Historical Mechanisms Specification Version 3.0. 39 Edited by Chris Zimman, Dieter Bong. Latest version. http://docs.oasis- 40 open.org/pkcs11/pkcs11-hist/v2.41/pkcs11-hist-v2.41.html. pkcs11-curr-v3.0-wd110-rev2 Working Draft 10 Rev. 21 287 May 2019 Standards Track Draft Copyright © OASIS Open 2019. All Rights Reserved. Page 1 of 278 41 PKCS #11 Cryptographic Token Interface Usage Guide Version 3.0. Edited by John 42 Leiseboer and Robert Griffin. Latest version. http://docs.oasis-open.org/pkcs11/pkcs11- 43 ug/v2.41/pkcs11-ug-v2.41.html. 44 PKCS #11 Cryptographic Token Interface Profiles Version 3.0. Edited by Tim Hudson. Latest 45 version. http://docs.oasis-open.org/pkcs11/pkcs11-profiles/v2.41/pkcs11-profiles-v2.41.html. 46 Abstract: 47 This document defines mechanisms that are anticipated for use with the current version of PKCS 48 #11. 49 Status: 50 This Working Draft (WD) has been produced by one or more TC Members; it has not yet been 51 voted on by the TC or approved as a Committee Draft (Committee Specification Draft or a 52 Committee Note Draft). The OASIS document Approval Process begins officially with a TC vote 53 to approve a WD as a Committee Draft. A TC may approve a Working Draft, revise it, and re- 54 approve it any number of times as a Committee Draft. 55 URI patterns: 56 Initial publication URI: 57 http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.41/csd01/pkcs11-curr-v2.41-csd01.doc 58 Permanent “Latest version” URI: 59 http://docs.oasis-open.org/pkcs11/pkcs11-curr/v2.41/pkcs11-curr-v2.41.doc 60 (Managed by OASIS TC Administration; please don’t modify.) 61 62 63 Copyright © OASIS Open 2019. All Rights Reserved. 64 All capitalized terms in the following text have the meanings assigned to them in the OASIS Intellectual 65 Property Rights Policy (the "OASIS IPR Policy"). The full Policy may be found at the OASIS website. 66 This document and translations of it may be copied and furnished to others, and derivative works that 67 comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, 68 and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice 69 and this section are included on all such copies and derivative works. However, this document itself may 70 not be modified in any way, including by removing the copyright notice or references to OASIS, except as 71 needed for the purpose of developing any document or deliverable produced by an OASIS Technical 72 Committee (in which case the rules applicable to copyrights, as set forth in the OASIS IPR Policy, must 73 be followed) or as required to translate it into languages other than English. 74 The limited permissions granted above are perpetual and will not be revoked by OASIS or its successors 75 or assigns. 76 This document and the information contained herein is provided on an "AS IS" basis and OASIS 77 DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY 78 WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY 79 OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 80 PARTICULAR PURPOSE. 81 pkcs11-curr-v3.0-wd110-rev2 Working Draft 10 Rev. 21 287 May 2019 Standards Track Draft Copyright © OASIS Open 2019. All Rights Reserved. Page 2 of 278 82 Table of Contents 83 1 Introduction ................................................................................................................................... 14 84 1.1 Terminology ................................................................................................................................ 14 85 1.2 Definitions ................................................................................................................................... 14 86 1.3 Normative References ................................................................................................................. 15 87 1.4 Non-Normative References ......................................................................................................... 17 88 2 Mechanisms .................................................................................................................................. 20 89 2.1 RSA ............................................................................................................................................ 20 90 2.1.1 Definitions ............................................................................................................................ 21 91 2.1.2 RSA public key objects ......................................................................................................... 22 92 2.1.3 RSA private key objects ........................................................................................................ 23 93 2.1.4 PKCS #1 RSA key pair generation ........................................................................................ 24 94 2.1.5 X9.31 RSA key pair generation ............................................................................................. 25 95 2.1.6 PKCS #1 v1.5 RSA ............................................................................................................... 25 96 2.1.7 PKCS #1 RSA OAEP mechanism parameters ...................................................................... 26 97 2.1.8 PKCS #1 RSA OAEP ........................................................................................................... 28 98 2.1.9 PKCS #1 RSA PSS mechanism parameters ......................................................................... 28 99 2.1.10 PKCS #1 RSA PSS ............................................................................................................ 29 100 2.1.11 ISO/IEC 9796 RSA ............................................................................................................. 29 101 2.1.12 X.509 (raw) RSA................................................................................................................. 30 102 2.1.13 ANSI X9.31 RSA ................................................................................................................ 31 103 2.1.14 PKCS #1 v1.5 RSA signature with MD2, MD5, SHA-1, SHA-256, SHA-384, SHA-512, RIPE- 104 MD 128 or RIPE-MD 160 ............................................................................................................... 32 105 2.1.15 PKCS #1 v1.5 RSA signature with SHA-224 ....................................................................... 32 106 2.1.16 PKCS #1 RSA PSS signature with SHA-224 ....................................................................... 32 107 2.1.17 PKCS #1 RSA PSS signature with SHA-1, SHA-256, SHA-384 or SHA-512 ........................ 32 108 2.1.18 PKCS #1 v1.5 RSA signature with SHA3 ............................................................................ 33 109 2.1.19 PKCS #1 RSA PSS signature with SHA3 ............................................................................ 33 110 2.1.20 ANSI X9.31 RSA signature with SHA-1 ............................................................................... 33 111 2.1.21 TPM 1.1b and TPM 1.2 PKCS #1 v1.5 RSA ........................................................................ 34 112 2.1.22 TPM 1.1b and TPM 1.2 PKCS #1 RSA OAEP ..................................................................... 34 113 2.1.23 RSA AES KEY WRAP ........................................................................................................ 35 114 2.1.24 RSA AES KEY WRAP mechanism parameters ................................................................... 36 115 2.1.25 FIPS 186-4 ........................................................................................................................
Load more

Recommended publications
  • DRAFT Special Publication 800-56A, Recommendation for Pair-Wise Key
    The attached DRAFT document (provided here for historical purposes) has been superseded by the following publication: Publication Number: NIST Special Publication (SP) 800-56A Revision 2 Title: Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography Publication Date: 05/13/2013 • Final Publication: https://doi.org/10.6028/NIST.SP.800-56Ar2 (which links to http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-56Ar2.pdf). • Information on other NIST Computer Security Division publications and programs can be found at: http://csrc.nist.gov/ The following information was posted with the attached DRAFT document: Aug 20, 2012 SP 800-56 A Rev.1 DRAFT Recommendation for Pair-Wise Key-Establishment Schemes Using Discrete Logarithm Cryptography (Draft Revision) NIST announces the release of draft revision of Special Publication 800-56A, Recommendation for Pair-Wise Key Establishment Schemes Using Discrete Logarithm Cryptography. SP 800-56A specifies key-establishment schemes based on the discrete logarithm problem over finite fields and elliptic curves, including several variations of Diffie-Hellman and MQV key establishment schemes. The revision is made on the March 2007 version. The main changes are listed in Appendix D. Please submit comments to 56A2012rev-comments @ nist.gov with "Comments on SP 800-56A (Revision)" in the subject line. The comment period closes on October 31, 2012. NIST Special Publication 800-56A Recommendation for Pair-Wise August 2012 Key-Establishment Schemes Using Discrete Logarithm Cryptography (Draft Revision) Elaine Barker, Lily Chen, Miles Smid and Allen Roginsky C O M P U T E R S E C U R I T Y Abstract This Recommendation specifies key-establishment schemes based on the discrete logarithm problem over finite fields and elliptic curves, including several variations of Diffie-Hellman and MQV key establishment schemes.
    [Show full text]
  • Guidelines on Cryptographic Algorithms Usage and Key Management
    EPC342-08 Version 7.0 4 November 2017 [X] Public – [ ] Internal Use – [ ] Confidential – [ ] Strictest Confidence Distribution: Publicly available GUIDELINES ON CRYPTOGRAPHIC ALGORITHMS USAGE AND KEY MANAGEMENT Abstract This document defines guidelines on cryptographic algorithms usage and key management. Document Reference EPC342-08 Issue Version 7.0 Date of Issue 22 November 2017 Reason for Issue Maintenance of document Produced by EPC Authorised by EPC Document History This document was first produced by ECBS as TR 406, with its latest ECBS version published in September 2005. The document has been handed over to the EPC which is responsible for its yearly maintenance. DISCLAIMER: Whilst the European Payments Council (EPC) has used its best endeavours to make sure that all the information, data, documentation (including references) and other material in the present document are accurate and complete, it does not accept liability for any errors or omissions. EPC will not be liable for any claims or losses of any nature arising directly or indirectly from use of the information, data, documentation or other material in the present document. Conseil Européen des Paiements AISBL– Cours Saint-Michel 30A – B 1040 Brussels Tel: +32 2 733 35 33 – Fax: +32 2 736 49 88 Enterprise N° 0873.268.927 – www.epc-cep.eu – [email protected] © 2016 Copyright European Payments Council (EPC) AISBL: Reproduction for non-commercial purposes is authorised, with acknowledgement of the source Table of Content MANAGEMENT SUMMARY ............................................................. 5 1 INTRODUCTION .................................................................... 7 1.1 Scope of the document ...................................................... 7 1.2 Document structure .......................................................... 7 1.3 Recommendations ............................................................ 8 1.4 Implementation best practices .........................................
    [Show full text]
  • On Robust Key Agreement Based on Public Key Authentication Feng Hao Thales E-Security, Cambridge, UK [email protected]
    1 On Robust Key Agreement Based on Public Key Authentication Feng Hao Thales E-Security, Cambridge, UK [email protected] Abstract—This paper discusses public-key authenticated key Elliptic Curve Cryptography (ECC) [10]. Using ECC essen- agreement protocols. First, we critically analyze several authen- tially replaces the underlying (multiplicative) cyclic group ticated key agreement protocols and uncover various theoretical with another (additive) cyclic group defined over some elliptic and practical flaws. In particular, we present two new attacks on the HMQV protocol, which is currently being standardized curve. The essence of the protocol remains unchanged. by IEEE P1363. The first attack presents a counterexample to The acute problem with the Diffie-Hellman key agreement invalidate the basic authentication in HMQV. The second attack is that it is unauthenticated [2]. While secure against passive is applicable to almost all past schemes, despite that many of attackers, the protocol is inherently vulnerable to active attacks them have formal security proofs. These attacks highlight the such as the man-in-the-middle attack [6]. This is a serious lim- difficulty to design a crypto protocol correctly and suggest the caution one should always take. itation, which for many years has been motivating researchers We further point out that many of the design errors are caused to find a solution [3]–[5], [7], [9], [11], [13], [20]. by sidestepping an important engineering principle, namely To add authentication, we must start with assuming some “Do not assume that a message you receive has a particular shared secret. In general, there are two approaches.
    [Show full text]
  • The Whole Is Less Than the Sum of Its Parts: Constructing More Efficient Lattice-Based Akes Rafael Del Pino, Vadim Lyubashevsky, David Pointcheval
    The Whole is Less Than the Sum of Its Parts: Constructing More Efficient Lattice-Based AKEs Rafael del Pino, Vadim Lyubashevsky, David Pointcheval To cite this version: Rafael del Pino, Vadim Lyubashevsky, David Pointcheval. The Whole is Less Than the Sum of Its Parts: Constructing More Efficient Lattice-Based AKEs. SCN 2016 - 10th International Conference Security and Cryptography for Networks, Aug 2016, Amalfi, Italy. pp.273 - 291, 10.1007/978-3-319- 44618-9_15. hal-01378005 HAL Id: hal-01378005 https://hal.inria.fr/hal-01378005 Submitted on 8 Oct 2016 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. The Whole is Less than the Sum of its Parts: Constructing More Efficient Lattice-Based AKEs? Rafael del Pino1;2;3, Vadim Lyubashevsky4, and David Pointcheval3;2;1 1 INRIA, Paris 2 Ecole´ Normale Sup´erieure,Paris 3 CNRS 4 IBM Research Zurich Abstract. Authenticated Key Exchange (AKE) is the backbone of internet security protocols such as TLS and IKE. A recent announcement by standardization bodies calling for a shift to quantum-resilient crypto has resulted in several AKE proposals from the research community. Be- cause AKE can be generically constructed by combining a digital signature scheme with public key encryption (or a KEM), most of these proposals focused on optimizing the known KEMs and left the authentication part to the generic combination with digital signatures.
    [Show full text]
  • The Odd Couple: MQV and HMQV
    The odd couple: MQV and HMQV Jean-Philippe Aumasson 1 / 49 Summary MQV = EC-DH-based key agreement protocol, I proposed by Menezes, Qu and Vanstone (1995), I improved with Law and Solinas (1998), I widely standardized (ANSI, ISO/IEC, IEEE), and recommended (NIST, NSA suite B). HMQV = variant of MQV, I proposed by Krawczyk (2005), I attacked by Menezes, I validity of attacks unclear. 2 / 49 References A. Menezes, M. Qu, S. Vanstone. Some new key agreement protocols providing implicit authentication. SAC’95. L. Law, A. Menezes, M. Qu, J. Solinas, S. Vanstone. An efficient protocol for authenticated key agreement. Design, Codes, and Cryptography, 2003. H. Krawczyk. HMQV: A high-performance secure Diffie-Hellman protocol. CRYPTO’ 05. Full version on ePrint (2005/176). A. Menezes. Another look at HMQV. ePrint (2005/205). Journal of Mathematical Cryptology, 2007. A. Menezes, B. Ustaoglu. On the importance of public-key validation in the MQV and HMQV key agreement protocols. INDOCRYPT’06. 3 / 49 Road map PART I I Key agreement protocols I Elliptic curves I The MQV protocols PART II I The “insecurity” of MQV I HMQV I The “insecurity” of HMQV CONCLUSION 4 / 49 PART I 5 / 49 Key agreement protocols 6 / 49 Taxonomy From the HAC. Key establishment is a protocol whereby a shared secret becomes available to two or more parties, for subsequent cryptographic use. A key transport protocol is a key establishment technique where one party creates or otherwise obtains a secret value, and securely transfers it to the other(s). A key agreement protocol is a key establishement in which a shared secret is derived by two (or more) parties as a function of information contributed by, or associated with, each of these, (ideally) such that no party can predetermine the resulting value.
    [Show full text]
  • NIST)  Quantum Computing Will Break Many Public-Key Cryptographic Algorithms/Schemes ◦ Key Agreement (E.G
    Post Quantum Cryptography Team Presenter: Lily Chen National Institute of Standards and Technology (NIST) Quantum computing will break many public-key cryptographic algorithms/schemes ◦ Key agreement (e.g. DH and MQV) ◦ Digital signatures (e.g. RSA and DSA) ◦ Encryption (e.g. RSA) These algorithms have been used to protect Internet protocols (e.g. IPsec) and applications (e.g.TLS) NIST is studying “quantum-safe” replacements This talk will focus on practical aspects ◦ For security, see Yi-Kai Liu’s talk later today ◦ Key establishment: ephemeral Diffie-Hellman ◦ Authentication: signature or pre-shared key Key establishment through RSA, DHE, or DH Client Server ◦ RSA – Client encrypts pre- master secret using server’s Client RSA public key Hello Server Hello Certificate* ◦ DHE – Ephemeral Diffie- ServerKeyExchange* Hellman CertificateRequest* ◦ DH – Client generates an ServerHelloDone ephemeral DH public value. Certificate* ClientKeyExchange* Pre-master secret is generated CertificateVerify* using server static public key {ChangeCipherSpec} Finished Server authentication {ChangeCipherSpec} ◦ RSA – implicit (by key Finished confirmation) ◦ DHE - signature Application data Application Data ◦ DH – implicit (by key confirmation) IKE ◦ A replacement of ephemeral Diffie-Hellman key agreement should have a fast key pair generation scheme ◦ If signatures are used for authentication, both signing and verifying need to be equally efficient TLS ◦ RSA - encryption replacement needs to have a fast encryption ◦ DHE – fast key pair generation and efficient signature verification ◦ DH – fast key pair generation Which are most important in practice? ◦ Public and private key sizes ◦ Key pair generation time ◦ Ciphertext size ◦ Encryption/Decryption speed ◦ Signature size ◦ Signature generation/verification time Not a lot of benchmarks in this area Lattice-based ◦ NTRU Encryption and NTRU Signature ◦ (Ring-based) Learning with Errors Code-based ◦ McEliece encryption and CFS signatures Multivariate ◦ HFE, psFlash , Quartz (a variant of HFE), Many more….
    [Show full text]
  • BC FIPS Java Description
    The Bouncy Castle FIPS Java API 20 November 2015 1. Introduction The Bouncy Castle APIs (BC) divide into 3 groups: there is a light-weight API which provides direct access to cryptographic services, a provider for the Java Cryptography Architecture (JCA) and the Java Cryptography Extension (JCE) built on top of the light-weight API that provides access to services required to use the JCA/JCE, and another set of APIs which provide handling of protocols such as Cryptographic Message Syntax (CMS), OpenPGP, Time Stamp Protocol (TSP), Secure Mime (S/MIME), Certificate Management Protocol (CMP), as well as APIs for generating Certification Requests (CRMF, PKCS#10), X.509 certificates, PKCS#12 files and other protocol elements used in a variety of standards. The total code base, including porting code for different JVMs, is currently sitting at around 499,000 lines of Java. Overall, the design of the original BC APIs is such that the classes can be used to create objects which can be assembled in many different ways, regardless of whether it makes sense. This has given us a very agile API to work with, in the sense that it is easy to formulate new combinations of algorithms, modes, and padding types, as well as to define a wide variety of things like signature types. However the boundaries are loosely defined, and the agility results in widespread leakage – FIPS style programming requires specific paths to access cryptographic functions with defined boundaries between what's in the cryptographic world and what is not. For the purposes of many application developers using BC, the BC approach is either fine, or they are simply not aware of the potential issues as they only work at the JCA/JCE level or even at a higher level such as CMS or OpenPGP.
    [Show full text]
  • Recommendation for Key Management, Part 1: General Publication Date(S) January 2016 Withdrawal Date May 4, 2020 Withdrawal Note SP 800-57 Part 1 Rev
    Withdrawn NIST Technical Series Publication Warning Notice The attached publication has been withdrawn (archived), and is provided solely for historical purposes. It may have been superseded by another publication (indicated below). Withdrawn Publication Series/Number NIST Special Publication 800-57 Part 1 Revision 4 Title Recommendation for Key Management, Part 1: General Publication Date(s) January 2016 Withdrawal Date May 4, 2020 Withdrawal Note SP 800-57 Part 1 Rev. 4 is superseded in its entirety by the publication of SP 800-57 Part 1 Rev. 5. Superseding Publication(s) (if applicable) The attached publication has been superseded by the following publication(s): Series/Number NIST Special Publication 800-57 Part 1 Revision 5 Title Recommendation for Key Management: Part 1 – General Author(s) Elaine Barker Publication Date(s) May 2020 URL/DOI https://doi.org/10.6028/NIST.SP.800-57pt1r5 Additional Information (if applicable) Contact Computer Security Division (Information Technology Laboratory) Latest revision of the attached publication Related Information https://csrc.nist.gov/projects/key-management/key-management-guidelines https://csrc.nist.gov/publications/detail/sp/800-57-part-1/rev-5/final Withdrawal Announcement Link Date updated: May 4, 2020 NIST Special Publication 800-57 Part 1 Revision 4 Recommendation for Key Management Part 1: General Elaine Barker This publication is available free of charge from: http://dx.doi.org/10.6028/NIST.SP.800-57pt1r4 C O M P U T E R S E C U R I T Y NIST Special Publication 800-57 Part 1 Revision 4 Recommendation for Key Management Part 1: General Elaine Barker Computer Security Division Information Technology Laboratory This publication is available free of charge from: http://dx.doi.org/10.6028/NIST.SP.800-57pt1r4 January 2016 U.S.
    [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]
  • H. Krawczyk, IBM Reasearch R. Barnes, O. Friel, Cisco N. Sullivan
    OPAQUE IN TLS 1.3 NICK SULLIVAN H. Krawczyk, IBM Reasearch CLOUDFLARE R. Barnes, O. Friel, Cisco @GRITTYGREASE N. Sullivan, Cloudflare MODERN PASSWORD-BASED AUTHENTICATION IN TLS OPAQUE IN TLS 1.3 A SHORT HISTORY ▸ Password-based authentication ▸ * without sending the password to the server ▸ SRP (Secure Remote Password) — RFC 2945 ▸ aPAKE (Augmented Password-Authenticated Key Exchange) ▸ Widely implemented, used in Apple iCloud, ProtonMail, etc. ▸ Dragonfly — RFC 8492 ▸ SPEKE (Simple password exponential key exchange) derived ▸ Independent submission OPAQUE IN TLS 1.3 SRP IN TLS (RFC 5054) ▸ Salt sent in the clear ▸ Leads to pre-computation attack on password database ▸ Unsatisfying security analysis ▸ Finite fields only, no ECC ▸ Awkward fit for TLS 1.3 ▸ Needs missing messages (challenges outlined in draft-barnes-tls-pake) ▸ Post-handshake requires renegotiation OPAQUE A new methodology for designing secure aPAKEs OPAQUE IN TLS 1.3 OPAQUE OVERVIEW ▸ Methodology to combine an authenticated key exchange (such as TLS 1.3) with an OPRF (Oblivious Pseudo-Random Function) to get a Secure aPAKE ▸ Desirable properties ▸ Security proof ▸ Secure against pre-computation attacks ▸ Efficient implementation based on ECC OPAQUE IN TLS 1.3 OPAQUE DEPENDENCIES OVERVIEW ▸ Underlying cryptographic work in CFRG ▸ OPAQUE (draft-krawczyk-cfrg-opaque) ▸ OPRF (draft-sullivan-cfrg-voprf) ▸ Hash-to-curve (draft-irtf-cfrg-hash-to-curve) EC-OPRF FUNDAMENTALS FUNDAMENTAL COMPONENTS / TERMINOLOGY ▸ The OPRF protocol allows the client to obtain a value based on the password and the server’s private key without revealing the password to the server ▸ OPRF(pwd) is used to encrypt an envelope containing OPAQUE keys ▸ The client’s TLS 1.3-compatible private key ▸ The server’s TLS 1.3-compatible public key EC-OPRF FUNDAMENTALS FUNDAMENTAL COMPONENTS / TERMINOLOGY ▸ Prime order group ▸ e.g.
    [Show full text]
  • Year 2010 Issues on Cryptographic Algorithms
    IMES DISCUSSION PAPER SERIES Year 2010 issues on cryptographic algorithms Masashi Une and Masayuki Kanda Discussion Paper No. 2006-E-8 INSTITUTE FOR MONETARY AND ECONOMIC STUDIES BANK OF JAPAN C.P.O BOX 203 TOKYO 100-8630 JAPAN You can download this and other papers at the IMES Web site: http://www.imes.boj.or.jp Do not reprint or reproduce without permission. NOTE: IMES Discussion Paper Series is circulated in order to stimulate discussion and comments. Views expressed in Discussion Paper Series are those of authors and do not necessarily reflect those of the Bank of Japan or the Institute for Monetary and Economic Studies. IMES Discussion Paper Series 2006-E-8 June 2006 Year 2010 issues on cryptographic algorithms Masashi Une† and Masayuki Kanda* Abstract In the financial sector, cryptographic algorithms are used as fundamental techniques for assuring confidentiality and integrity of data used in financial transactions and for authenticating entities involved in the transactions. Currently, the most widely used algorithms appear to be two-key triple DES and RC4 for symmetric ciphers, RSA with a 1024-bit key for an asymmetric cipher and a digital signature, and SHA-1 for a hash function according to international standards and guidelines related to the financial transactions. However, according to academic papers and reports regarding the security evaluation for such algorithms, it is difficult to ensure enough security by using the algorithms for a long time period such as ten or fifteen years due to advances in cryptanalysis techniques, improvement of computing power and so on. In order to enhance the transition to more secure ones, NIST (National Institute of Standards and Technology) of the United States describes in various guidelines that NIST will no longer approve two-key triple DES, RSA with a 1024-bit key, and SHA-1 as the algorithms suitable for IT systems of the Federal Government after 2010.
    [Show full text]
  • The Factoring Dead: Preparing for the Cryptopocalypse
    THE FACTORING DEAD: PREPARING FOR THE CRYPTOPOCALYPSE Javed Samuel — javed[at]isecpartners[dot]com iSEC Partners, Inc 123 Mission Street, Suite 1020 San Francisco, CA 94105 https://www.isecpartners.com March 20, 2014 Abstract This paper will explain the latest breakthroughs in the academic cryptography community and look ahead at what practical issues could arise for popular cryptosystems. Specifically, we will focus on the recent major devel- opments in discrete mathematics and their potential ability to undermine our trust in the most basic asymmetric primitives, including RSA. We will explain the basic theories behind RSA and the state-of-the-art in large number- ing factoring, and how several recent papers may point the way to massive improvements in this area. The paper will then switch to the practical aspects of the doomsday scenario, and will answer the question “What happens the day after RSA is broken?” We will point out the many obvious and hidden uses of RSA and related algorithms and outline how software engineers and security teams can operate in a post-RSA world. We will also discuss the results of our survey of popular products and software, and point out the ways in which individuals can prepare for the “zombie cryptopocalypse”. 1 INTRODUCTION Over the past few years, there have been numerous attacks on the current SSL infrastructure. These have ranged from BEAST [97], CRIME [88], Lucky 13 [2][86], RC4 bias attacks [1][91] and BREACH [42]. These attacks all show the fragility of the current SSL architecture as vulnerabilities have been found in a variety of features ranging from compression, timing and padding [90].
    [Show full text]