DOCSLIB.ORG

AICHAIN Yellowpaper Version

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
AICHAIN Yellowpaper Version AICHAIN yellowpaper AICHAIN Yellowpaper Version: 9.1 AICHAIN 2017 Page 1 of 47 AICHAIN yellowpaper 1. ABSTRACT................................................................................................................................. 3 2. DEFINITION OF PRIVATE KEY, PUBLIC KEY AND ADDRESS ..................................... 4 2.1 PUBLIC KEY CRYPTOGRAPHY ................................................................................................................ 4 2.2 RELATED ALGORITHMS ......................................................................................................................... 4 2.2.1 Elliptic Curve Signature Algorithm ............................................................................................... 4 2.2.2 Hash Function ............................................................................................................................... 5 2.2.3 Base58 encoding ............................................................................................................................ 5 2.3 PRIVATE KEY AND PUBLIC KEY ............................................................................................................. 5 2.4 GENERATING THE ADDRESS ................................................................................................................... 6 2.5 SOME ADDRESS FORMS .......................................................................................................................... 7 2.5.1 P2PKH（Pay to Public Key Hash） ............................................................................................. 7 2.5.2 P2PK（Pay to Public Key） ....................................................................................................... 10 2.5.3 P2SH（Pay to Script Hash） ...................................................................................................... 10 3. MINING ALGORITHM .......................................................................................................... 11 3.1 LYRA2DC (DC – DYNAMIC COMPLEXITY).......................................................................................... 11 3.2 PASSWORD HASHING SCHEMES (PHS) ................................................................................................ 14 3.3 SCRYPT ................................................................................................................................................ 17 3.4 LYRA2.................................................................................................................................................. 19 4. APPLICATION INFORMATION IN THE UTXO TRADING MODEL............................ 22 4.1 APPLICATION DEPLOYMENT PRINCIPLES ............................................................................................. 22 4.2 THE EXPANSION OF TRANSACTION DATA ............................................................................................. 22 4.3 APPLICATION DEPLOYMENT UNIT : ADU ............................................................................................ 23 4.3.1 Customizable data content ........................................................................................................... 24 4.3.2 Application case: standard application unit information ............................................................ 26 4.4 APPLICATION EXECUTION UNIT : AEU ................................................................................................. 27 4.4.1 Custom data modification execution unit information ................................................................. 28 4.4.2 Application case: standard application executive unit information............................................. 31 5. APPLICATION DEPLOYMENT AND IMPLEMENTATION ........................................... 31 5.1 ADU LOCATION IDENTIFIER................................................................................................................. 31 5.2 P2SH ADDRESS OF ADU UNIT ............................................................................................................. 32 5.3 OPERATING ENVIRONMENT OF THE APPLICATION ................................................................................ 33 5.4 TYPES OF APPLICATIONS ...................................................................................................................... 34 5.4.1 Provide executable files ............................................................................................................... 34 5.4.2 Provide direct access to services ................................................................................................. 35 5.4.3 Provides running platform resources ........................................................................................... 35 5.4.4 Data resources ............................................................................................................................. 35 5.4.5 Extend other types of resources ................................................................................................... 35 5.5 USING THE ADU APPLICATION ............................................................................................................ 36 5.5.1 Transaction data containing AEU units ....................................................................................... 36 5.5.2 Transaction data verification ....................................................................................................... 36 5.5.3 The application provider verifies the identity of the user ............................................................ 39 5.6 RUNNING PROCESS .............................................................................................................................. 40 5.6.1 Developers use data resources ..................................................................................................... 41 5.6.2 Applications for users. ................................................................................................................. 42 5.6.3 users use the resources and applications of running platforms ................................................... 43 REFERENCE .................................................................................................................................... 46 AICHAIN 2017 Page 2 of 47 AICHAIN yellowpaper 1. Abstract The aim of AICHAIN is to provide a public blockchain platform for the AI with complex applications. The data resources provider, application development team and runtime platform resources provider and users, they all can deploy the data or application on AICHAIN, and setup an ecology chain system for AI application on blockchain technology with lower cost and lower technology threshold. AICHAIN will build a benign ecosystem, encourage more people to participate in the development and landing of AI applications, promote the development of AI in a credible and reliable environment, and transform the data generated by individuals into more precise services for individuals. The key issues to be solved by the AICHAIN: 1. Based on the blockchain technology of bitcoin and implement a non-chip mining algorithm. Bitcoin-HASH, LTC-scrypt, DASH-X11 have been implemented inside ASIC. ETH is to take up a lot of graphics resources. High-end graphics cards are now also monopolized by big companies. A less expensive graphics card resource is expected, but at the same time it must not be easily implemented inside ASIC). Its purpose is to make blockchain safer, to ensure that participating users have enough the computing power and the right to deploy their own applications. 2. Develop AI application deployment functions based on bitcoin blockchain and definitions of the application deployment or execution unit based on the data format of the transaction. 3. AICHAIN separates the application running environment from the blockchain node. Use docker as the application running platform, which allows AICHAIN to provide standard, upgradeable, customizable and supporting multiple programming languages APP running environment. AICHAIN node program comes with a public standard docker IMG with application running environment. This running environment can be continuously upgraded, even be modified by user freely, and users can deploy their own docker IMG with AICHAIN nodes. 4. Only put the description of AI application on the blockchain, and will not include complete application data, which allows that the size of application data can be very large, and can save the storage space of blockchain. The deployer provides download address for application executable file and data resources, or an address for direct service. Only the description information of those application or resource is recorded in the AI application information unit. AICHAIN 2017 Page 3 of 47 AICHAIN yellowpaper 5. Provide the interface for verification of user’s identity and blockchain transaction information. This allows developers make more customized on their application, which is suitable for more complex application development and running environment. 2. Definition of private key, public key and address 2.1 Public Key Cryptography Asymmetric encryption requires two (one pair) keys: public key and private key. Only the corresponding private key can decrypted the data encrypted with the public key. And vice versa. (If the private key is used in Encryption, only the corresponding public key can be used to decrypt it.) Both parties can establish secure communication
Load more

Recommended publications
  • Permutation-Based Encryption, Authentication and Authenticated Encryption
    Permutation-based encryption, authentication and authenticated encryption Permutation-based encryption, authentication and authenticated encryption Joan Daemen1 Joint work with Guido Bertoni1, Michaël Peeters2 and Gilles Van Assche1 1STMicroelectronics 2NXP Semiconductors DIAC 2012, Stockholm, July 6 . Permutation-based encryption, authentication and authenticated encryption Modern-day cryptography is block-cipher centric Modern-day cryptography is block-cipher centric (Standard) hash functions make use of block ciphers SHA-1, SHA-256, SHA-512, Whirlpool, RIPEMD-160, … So HMAC, MGF1, etc. are in practice also block-cipher based Block encryption: ECB, CBC, … Stream encryption: synchronous: counter mode, OFB, … self-synchronizing: CFB MAC computation: CBC-MAC, C-MAC, … Authenticated encryption: OCB, GCM, CCM … . Permutation-based encryption, authentication and authenticated encryption Modern-day cryptography is block-cipher centric Structure of a block cipher . Permutation-based encryption, authentication and authenticated encryption Modern-day cryptography is block-cipher centric Structure of a block cipher (inverse operation) . Permutation-based encryption, authentication and authenticated encryption Modern-day cryptography is block-cipher centric When is the inverse block cipher needed? Indicated in red: Hashing and its modes HMAC, MGF1, … Block encryption: ECB, CBC, … Stream encryption: synchronous: counter mode, OFB, … self-synchronizing: CFB MAC computation: CBC-MAC, C-MAC, … Authenticated encryption: OCB, GCM, CCM … So a block cipher
    [Show full text]
  • Cryptographic Sponge Functions
    Cryptographic sponge functions Guido B1 Joan D1 Michaël P2 Gilles V A1 http://sponge.noekeon.org/ Version 0.1 1STMicroelectronics January 14, 2011 2NXP Semiconductors Cryptographic sponge functions 2 / 93 Contents 1 Introduction 7 1.1 Roots .......................................... 7 1.2 The sponge construction ............................... 8 1.3 Sponge as a reference of security claims ...................... 8 1.4 Sponge as a design tool ................................ 9 1.5 Sponge as a versatile cryptographic primitive ................... 9 1.6 Structure of this document .............................. 10 2 Definitions 11 2.1 Conventions and notation .............................. 11 2.1.1 Bitstrings .................................... 11 2.1.2 Padding rules ................................. 11 2.1.3 Random oracles, transformations and permutations ........... 12 2.2 The sponge construction ............................... 12 2.3 The duplex construction ............................... 13 2.4 Auxiliary functions .................................. 15 2.4.1 The absorbing function and path ...................... 15 2.4.2 The squeezing function ........................... 16 2.5 Primary aacks on a sponge function ........................ 16 3 Sponge applications 19 3.1 Basic techniques .................................... 19 3.1.1 Domain separation .............................. 19 3.1.2 Keying ..................................... 20 3.1.3 State precomputation ............................ 20 3.2 Modes of use of sponge functions .........................
    [Show full text]
  • Broad View of Cryptographic Hash Functions
    IJCSI International Journal of Computer Science Issues, Vol. 10, Issue 4, No 1, July 2013 ISSN (Print): 1694-0814 | ISSN (Online): 1694-0784 www.IJCSI.org 239 Broad View of Cryptographic Hash Functions 1 2 Mohammad A. AlAhmad , Imad Fakhri Alshaikhli 1 Department of Computer Science, International Islamic University of Malaysia, 53100 Jalan Gombak Kuala Lumpur, Malaysia, 2 Department of Computer Science, International Islamic University of Malaysia, 53100 Jalan Gombak Kuala Lumpur, Malaysia Abstract Cryptographic hash function is a function that takes an arbitrary length as an input and produces a fixed size of an output. The viability of using cryptographic hash function is to verify data integrity and sender identity or source of information. This paper provides a detailed overview of cryptographic hash functions. It includes the properties, classification, constructions, attacks, applications and an overview of a selected dedicated cryptographic hash functions. Keywords-cryptographic hash function, construction, attack, classification, SHA-1, SHA-2, SHA-3. Figure 1. Classification of cryptographic hash function 1. INTRODUCTION CRHF usually deals with longer length hash values. An A cryptographic hash function H is an algorithm that takes an unkeyed hash function is a function for a fixed positive integer n * arbitrary length of message as an input {0, 1} and produce a which has, as a minimum, the following two properties: n fixed length of an output called message digest {0, 1} 1) Compression: h maps an input x of arbitrary finite bit (sometimes called an imprint, digital fingerprint, hash code, hash length, to an output h(x) of fixed bit length n.
    [Show full text]
  • The Password Hashing Competition Prehistory of Password Protection
    The Password Hashing Competition Peter Gutmann University of Auckland Prehistory of Password Protection Before timesharing • Whoever submitted the card deck owned it Prehistory of Password Protection (ctd) Compatible Time-Sharing System (CTSS), 1963 • Introduced the use of a “private code” to protect access to users’ data Prehistory of Password Protection (ctd) Famously failed in 1966 • CTSS editor used a fixed temporary filename • Admin edited the password file and login message file at the same time… Problem occurred at 5pm on a Friday • User noticed it and deliberately executed an HCF instruction in the debugger • When machine was rebooted, users were told to change their passwords – (And given free credit monitoring) History of Password Protection Cambridge Uni Titan timesharing system, 1967, used a one-way cipher to protect the password Spread to CTSS’ successor Multics in the 1970s • And from there to a Multics successor, Unics^H^Hx History of Password Protection (ctd) Unix originally stored passwords in the clear • More problems with editor temp files Encrypt the passwords like Multics had done • Protect against brute-force by iterating the encryption • Protect against comparing encrypted passwords by adding a random quantity (salt) to the password Originally based on a software analogue of the M-209 cipher machine • Encrypt the password using itself as the key • Found to be too fast, vulnerable to brute-forcing History of Password Protection (ctd) Later Unix crypt used 25 iterations of DES encryption • Salt+password used as a
    [Show full text]
  • High Throughput Implementation of the Keccak Hash Function Using the Nios-II Processor †
    technologies Article High Throughput Implementation of the Keccak Hash Function Using the Nios-II Processor † Argyrios Sideris * , Theodora Sanida and Minas Dasygenis Department of Electrical and Computer Engineering, University of Western Macedonia, 50131 Kozani, Greece; [email protected] (T.S.); [email protected] (M.D.) * Correspondence: [email protected]; Tel.: +30-24610-33101 † This paper is an extended version of our paper published in 8th International Conference on Modern Circuit and System Technologies on Electronics and Communications (MOCAST 2019), Thessaloniki, Greece, 13–15 May 2019. Received: 21 December 2019; Accepted: 6 February 2020; Published: 10 February 2020 Abstract: Presently, cryptographic hash functions play a critical role in many applications, such as digital signature systems, security communications, protocols, and network security infrastructures. The new standard cryptographic hash function is Secure Hash Algorithm 3 (SHA-3), which is not vulnerable to attacks. The Keccak algorithm is the winner of the NIST competition for the adoption of the new standard SHA-3 hash algorithm. In this work, we present hardware throughput optimization techniques for the SHA-3 algorithm using the Very High Speed Integrated Circuit Hardware Description Language (VHDL) programming language for all output lengths in the Keccak hash function (224, 256, 384 and 512). Our experiments were performed with the Nios II processor on the FPGA Arria 10 GX (10AX115N2P45E1SG). We applied two architectures, one without custom instruction and one with floating point hardware 2. Finally, we compare the results with other existing similar designs and found that the proposed design with floating point 2 optimizes throughput (Gbps) compared to existing FPGA implementations.
    [Show full text]
  • A Lightweight Implementation of Keccak Hash Function for Radio-Frequency Identification Applications
    A Lightweight Implementation of Keccak Hash Function for Radio-Frequency Identification Applications Elif Bilge Kavun and Tolga Yalcin Department of Cryptography Institute of Applied Mathematics, METU Ankara, Turkey {e168522,tyalcin}@metu.edu.tr Abstract. In this paper, we present a lightweight implementation of the permutation Keccak-f[200] and Keccak-f[400] of the SHA-3 candidate hash function Keccak. Our design is well suited for radio-frequency identification (RFID) applications that have limited resources and demand lightweight cryptographic hardware. Besides its low-area and low-power, our design gives a decent throughput. To the best of our knowledge, it is also the first lightweight implementation of a sponge function, which differentiates it from the previous works. By implementing the new hash algorithm Keccak, we have utilized unique advantages of the sponge construction. Although the implementation is targeted for Application Specific Integrated Circuit (ASIC) platforms, it is also suitable for Field Programmable Gate Arrays (FPGA). To obtain a compact design, serialized data processing principles are exploited together with algorithm-specific optimizations. The design requires only 2.52K gates with a throughput of 8 Kbps at 100 KHz system clock based on 0.13-µm CMOS standard cell library. Keywords: RFID, Keccak, SHA-3, sponge function, serialized processing, low- area, low-power, high throughput. 1 Introduction In recent years, the developments on digital wireless technology have improved many areas such as the mobile systems. Mobile and embedded devices will be everywhere in times to come, making it possible to use communication services and other applications anytime and anywhere. Among these mobile devices, radio-frequency identification (RFID) tags offer low-cost, long battery life and unprecedented mobility [1-2].
    [Show full text]
  • SHA-3 Family of Cryptographic Hash Functions and Extendable-Output Functions
    The SHA-3 Family of Cryptographic Hash Functions and Extendable-Output Functions José Luis Gómez Pardo Departamento de Álxebra, Universidade de Santiago 15782 Santiago de Compostela, Spain e-mail: [email protected] Carlos Gómez-Rodríguez Departamento de Computación, Universidade da Coruña 15071 A Coruña, Spain e-mail: [email protected] Introduction This worksheet contains a Maple implementation of the Secure Hash Algorithm-3 (SHA-3) family of functions wich have been standardized by the US National Institute of Standards and Technology (NIST) in August 2015, as specified in [FIPS PUB 202] (SHA-3 Standard). The SHA-3 family consists of four cryptographic hash functions, called SHA3-224, SHA3-256, SHA3-384, and SHA3 -512, and two extendable-output functions (XOFs), called SHAKE128 and SHAKE256. The XOFs are different from hash functions but, as stated in SHA-3 Standard, "it is possible to use them in similar ways, with the flexibility to be adapted directly to the requirements of individual applications, subject to additional security considerations". The SHA-3 functions are based on the Keccak sponge function, designed by G. Bertoni, J. Daemen, M. Peeters, G. Van Assche. Keccak was selected for this purpose because it was declared, on October 2, 2012, the winner of the NIST Hash Function Competition held by NIST. The worksheet is an updated version of a previous one which had been published in 2013 with the title "The SHA-3 family of hash functions and their use for message authentication". The new version includes the XOFs following the NIST specification and, at the programming level, the most important change is in the padding procedure.
    [Show full text]
  • Um Esquema De Hash De Senhas Com Maior Segurança Contra Trade-Offs Entre Processamento E Memória
    EWERTON RODRIGUES ANDRADE LYRA2: PASSWORD HASHING SCHEME WITH IMPROVED SECURITY AGAINST TIME-MEMORY TRADE-OFFS LYRA2: UM ESQUEMA DE HASH DE SENHAS COM MAIOR SEGURANÇA CONTRA TRADE-OFFS ENTRE PROCESSAMENTO E MEMÓRIA Tese apresentada à Escola Politécnica da Universidade de São Paulo para obtenção do Título de Doutor em Ciências. São Paulo 2016 EWERTON RODRIGUES ANDRADE LYRA2: PASSWORD HASHING SCHEME WITH IMPROVED SECURITY AGAINST TIME-MEMORY TRADE-OFFS LYRA2: UM ESQUEMA DE HASH DE SENHAS COM MAIOR SEGURANÇA CONTRA TRADE-OFFS ENTRE PROCESSAMENTO E MEMÓRIA Tese apresentada à Escola Politécnica da Universidade de São Paulo para obtenção do Título de Doutor em Ciências. Área de Concentração: Engenharia de Computação Orientador: Prof. Dr. Marcos A. Simplicio Junior São Paulo 2016 Catalogação-na-publicação Andrade, Ewerton Rodrigues Lyra2: Password Hashing Scheme with improved security against time memory trade-offs (Lyra2: Um Esquema de Hash de Senhas com maior segurança contra trade-offs entre processamento e memória) / E. R. Andrade -- São Paulo, 2016. 135 p. Tese (Doutorado) - Escola Politécnica da Universidade de São Paulo. Departamento de Engenharia de Computação e Sistemas Digitais. 1.Metodologia e técnicas de computação 2.Segurança de computadores 3.Criptologia 4.Algoritmos 5.Esquemas de Hash de Senhas I.Universidade de São Paulo. Escola Politécnica. Departamento de Engenharia de Computação e Sistemas Digitais II.t. RESUMO Para proteger-se de ataques de força bruta, sistemas modernos de autentica- ção baseados em senhas geralmente empregam algum Esquema de Hash de Senhas (Password Hashing Scheme - PHS). Basicamente, um PHS é um algoritmo crip- tográfico que gera uma sequência de bits pseudo-aleatórios a partir de uma senha provida pelo usuário, permitindo a este último configurar o custo computacional envolvido no processo e, assim, potencialmente elevar os custos de atacantes tes- tando múltiplas senhas em paralelo.
    [Show full text]
  • SHA-3 and Permutation-Based Cryptography
    SHA-3 and permutation-based cryptography Joan Daemen1 Joint work with Guido Bertoni1, Michaël Peeters2 and Gilles Van Assche1 1STMicroelectronics 2NXP Semiconductors Crypto summer school Šibenik, Croatia, June 1-6, 2014 1 / 49 Outline 1 Prologue 2 The sponge construction 3 Keccak and SHA-3 4 Sponge modes of use 5 Block cipher vs permutation 6 Variations on sponge 2 / 49 Prologue Outline 1 Prologue 2 The sponge construction 3 Keccak and SHA-3 4 Sponge modes of use 5 Block cipher vs permutation 6 Variations on sponge 3 / 49 Prologue Cryptographic hash functions ∗ n Function h from Z2 to Z2 Typical values for n: 128, 160, 256, 512 Pre-image resistant: it shall take 2n effort to given y, find x such that h(x) = y 2nd pre-image resistance: it shall take 2n effort to 0 0 given M and h(M), find another M with h(M ) = h(M) collision resistance: it shall take 2n/2 effort to find x1 6= x2 such that h(x1) = h(x2) 4 / 49 Prologue Classical way to build hash functions Mode of use of a compression function: Fixed-input-length compression function Merkle-Damgård iterating mode Property-preserving paradigm hash function inherits properties of compression function …actually block cipher with feed-forward (Davies-Meyer) Compression function built on arithmetic-rotation-XOR: ARX Instances: MD5, SHA-1, SHA-2 (224, 256, 384, 512) … 5 / 49 The sponge construction Outline 1 Prologue 2 The sponge construction 3 Keccak and SHA-3 4 Sponge modes of use 5 Block cipher vs permutation 6 Variations on sponge 6 / 49 The sponge construction Sponge origin: RadioGatún Initiative
    [Show full text]
  • Appendix K SHA-3
    Appendix K SHA-3 William Stallings K.1 THE ORIGINS OF SHA-3 ............................................................ 2 K.2 EVALUATION CRITERIA FOR SHA-3 ............................................. 4 K.3 THE SPONGE CONSTRUCTION .................................................... 6 K.4 THE SHA-3 ITERATION FUNCTION f .......................................... 13 Structure of f ....................................................................... 14 Theta Step Function .............................................................. 17 Rho Step Function ................................................................. 19 Pi Step Function ................................................................... 21 Chi Step Function ................................................................. 24 Iota Step Function ................................................................ 24 K.5 RECOMMENDED READING AND REFERENCES ............................. 26 References ........................................................................... 26 Copyright 2014 Supplement to Computer Security, Third Edition Pearson 2014 http://williamstallings.com/ComputerSecurity -1 - The winning design for the Secure Hash Algorithm 3 (SHA-3) was announced by NIST (National Institute of Standards and Technology) in October 2012. SHA-3 is a cryptographic hash function that is intended to complement SHA- 2 as the approved standard for a wide range of applications. In this chapter, we first look at the evaluation criteria used by NIST to select a candidate and
    [Show full text]
  • Design of SHA-3 Algorithm Using Compression Box (3200 Bit) for Digital Signature Applications
    International Journal of Emerging Engineering Research and Technology Volume 3, Issue 12, December 2015, PP 146-153 ISSN 2349-4395 (Print) & ISSN 2349-4409 (Online) Design of SHA-3 Algorithm using Compression Box (3200 bit) for Digital Signature Applications 1 2 Avinash Kumar , C.H Pushpalatha 1Department of ECE, GONNA INSTITUTE OF TECHNOLOGY, Vishakhapatnam, India (PG Scholar) 2Department of ECE, GONNA INSTITUTE OF TECHNOLOGY, Vishakhapatnam, India (Associate Professor) ABSTRACT SHA3 algorithm had proposed by five people with five different approaches. In that NIST (National Institute of Standards and Technology) selected one approach, that approach was proposed by Keccak. The Keccak-f permutation is the basic component of Keccak Hash function and supports 224-bit, 256-bit, 384-bit and 512- bit hash variants. It consists of number of rounds and each round is the combination of logical operations and bit permutations. Keccak is generated from sponge function with Keccak [r, c] members. It is categorized by these additional functions i.e. bit rate (r) and capacity (c). The addition of r + c gives width of the Keccak function permutation and is it is further limited to values as indicated 25, 50, 100, 200, 400, 800, 1600. After that Keccak, SHA3 algorithm using with memories but it will take more area. SHA3 have different variants like sha224, sha256, sha512, sha1024. The basic SHA3 using 512 bits converts 128 bits input into 1600 bits in the intermediate stage with using one C-box and performs 24 rounds. In our paper, for improving the security margin with respect to 512-bit, we are designing 128 bit Keccak sequential architecture for SHA- 1024 variant by converting it into 3200 bits in the intermediate stage using two C-boxes and 24 rounds , which is to be implemented using Xilinx 13.2.
    [Show full text]
  • Keccak and the SHA-3 Standardization
    Keccak and the SHA-3 Standardization Guido Bertoni1 Joan Daemen1 Michaël Peeters2 Gilles Van Assche1 1STMicroelectronics 2NXP Semiconductors NIST, Gaithersburg, MD February 6, 2013 1 / 60 Outline 1 The beginning 2 The sponge construction 3 Inside Keccak 4 Analysis underlying Keccak 5 Applications of Keccak, or sponge 6 Some ideas for the SHA-3 standard 2 / 60 The beginning Outline 1 The beginning 2 The sponge construction 3 Inside Keccak 4 Analysis underlying Keccak 5 Applications of Keccak, or sponge 6 Some ideas for the SHA-3 standard 3 / 60 The beginning Cryptographic hash functions * h : f0, 1g ! f0, 1gn Input message Digest MD5: n = 128 (Ron Rivest, 1992) SHA-1: n = 160 (NSA, NIST, 1995) SHA-2: n 2 f224, 256, 384, 512g (NSA, NIST, 2001) 4 / 60 The beginning Our beginning: RadioGatún Initiative to design hash/stream function (late 2005) rumours about NIST call for hash functions forming of Keccak Team starting point: fixing Panama [Daemen, Clapp, FSE 1998] RadioGatún [Keccak team, NIST 2nd hash workshop 2006] more conservative than Panama variable-length output expressing security claim: non-trivial exercise Sponge functions [Keccak team, Ecrypt hash, 2007] closest thing to a random oracle with a finite state Sponge construction calling random permutation 5 / 60 The beginning From RadioGatún to Keccak RadioGatún confidence crisis (2007-2008) own experiments did not inspire confidence in RadioGatún neither did third-party cryptanalysis [Bouillaguet, Fouque, SAC 2008] [Fuhr, Peyrin, FSE 2009] follow-up design Gnoblio went nowhere NIST SHA-3
    [Show full text]