DOCSLIB.ORG

FIPS 140-2 Non-Proprietary Security Policy

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
FIPS 140-2 Non-Proprietary Security Policy Amazon Linux 2 Libgcrypt Cryptographic Module Module Version 1.0 FIPS 140-2 Non-Proprietary Security Policy Document Version 1.1 Last update: 2020-Jan-27 Prepared by: atsec information security corporation 9130 Jollyville Road, Suite 260 Austin, TX 78759 www.atsec.com © 2020 Amazon Web Services, Inc./atsec information security. This document can be reproduced and distributed only whole and intact, including this copyright notice. Amazon Linux 2 Libgcrypt Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy Table of Contents 1 Introduction ....................................................................................................... 6 1.1 Purpose of the Security Policy ............................................................................................. 6 1.2 Target Audience ................................................................................................................... 6 2 Cryptographic Module Specification ..................................................................... 7 2.1 Module Overview ................................................................................................................. 7 2.2 FIPS 140-2 Validation Scope ................................................................................................ 7 2.3 Definition of the Cryptographic Module ............................................................................... 7 2.4 Definition of the Physical Cryptographic Boundary ............................................................. 8 2.5 Tested Environments ........................................................................................................... 9 2.6 Modes of Operation.............................................................................................................. 9 3 Module Ports and Interfaces .............................................................................. 11 4 Roles, Services and Authentication .................................................................... 12 4.1 Roles .................................................................................................................................. 12 4.2 Services ............................................................................................................................. 12 4.2.1 Services in the FIPS-Approved Mode of Operation ........................................................ 12 4.2.2 Services in the Non-FIPS-Approved Mode of Operation ................................................. 13 4.3 Algorithms .......................................................................................................................... 14 4.3.1 FIPS-Approved Algorithms.............................................................................................. 15 4.3.2 Non-Approved-but-Allowed Algorithms .......................................................................... 16 4.3.3 Non-Approved Algorithms .............................................................................................. 16 4.4 Operator Authentication .................................................................................................... 17 5 Physical Security .............................................................................................. 18 6 Operational Environment .................................................................................. 19 6.1 Applicability ....................................................................................................................... 19 6.2 Policy .................................................................................................................................. 19 7 Cryptographic Key Management ........................................................................ 20 7.1 Random Number Generation ............................................................................................. 21 7.2 Key Generation .................................................................................................................. 21 7.3 Key Entry and Output ........................................................................................................ 21 7.4 Key/CSP Storage ................................................................................................................ 21 7.5 Key/CSP Zeroization ........................................................................................................... 21 7.6 Key Establishment ............................................................................................................. 21 7.7 Handling of Keys and CSPs between Modes of Operation ................................................. 22 8 Electromagnetic Interference/Electromagnetic Compatibility (EMI/EMC) ............... 23 9 Self-Tests......................................................................................................... 24 9.1 Power-on Self-Tests ........................................................................................................... 24 © 2020 Amazon Web Services, Inc.; atsec information security. This document can be reproduced and distributed only whole and intact, including this copyright notice. 2 of 33 Amazon Linux 2 Libgcrypt Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy 9.2 Conditional Self-Tests ........................................................................................................ 25 9.3 On-Demand Self-tests ........................................................................................................ 25 9.4 Error States ........................................................................................................................ 25 10 Guidance ......................................................................................................... 26 10.1 Crypto-Officer Guidance .................................................................................................... 26 10.2 User Guidance.................................................................................................................... 27 10.2.1 Triple-DES Data Encryption ............................................................................................ 27 10.2.2 Key Usage and Management ......................................................................................... 27 11 Mitigation of Other Attacks ............................................................................... 28 12 Acronyms, Terms and Abbreviations .................................................................. 30 13 References ....................................................................................................... 31 © 2020 Amazon Web Services, Inc.; atsec information security. This document can be reproduced and distributed only whole and intact, including this copyright notice. 3 of 33 Amazon Linux 2 Libgcrypt Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy List of Tables Table 1: FIPS 140-2 Security Requirements. ........................................................................................... 7 Table 2: Components of the module. ...................................................................................................... 7 Table 3: Tested operational environment. .............................................................................................. 9 Table 4: Ports and interfaces. ............................................................................................................... 11 Table 5: Services in the FIPS-approved mode of operation. ................................................................. 12 Table 6: Services in the non-FIPS approved mode of operation. .......................................................... 14 Table 7: FIPS-approved cryptographic algorithms. ............................................................................... 15 Table 8: Non-Approved-but-allowed cryptographic algorithms. ........................................................... 16 Table 9: Non-FIPS approved cryptographic algorithms. ....................................................................... 17 Table 10: Lifecycle of keys and other Critical Security Parameters (CSPs). ......................................... 20 Table 11: Self-tests. .............................................................................................................................. 24 Table 12: Conditional self-tests............................................................................................................. 25 List of Figures Figure 1: Logical cryptographic boundary. ............................................................................................. 8 Figure 2: Hardware block diagram. ......................................................................................................... 9 © 2020 Amazon Web Services, Inc.; atsec information security. This document can be reproduced and distributed only whole and intact, including this copyright notice. 4 of 33 Amazon Linux 2 Libgcrypt Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy Copyrights and Trademarks Amazon is a registered trademark of Amazon Web Services, Inc. or its affiliates. © 2020 Amazon Web Services, Inc.; atsec information security. This document can be reproduced and distributed only whole and intact, including this copyright notice. 5 of 33 Amazon Linux 2 Libgcrypt Cryptographic Module FIPS 140-2 Non-Proprietary Security Policy 1 Introduction This document is the non-proprietary
Load more

Recommended publications
  • State of the Art in Lightweight Symmetric Cryptography
    State of the Art in Lightweight Symmetric Cryptography Alex Biryukov1 and Léo Perrin2 1 SnT, CSC, University of Luxembourg, [email protected] 2 SnT, University of Luxembourg, [email protected] Abstract. Lightweight cryptography has been one of the “hot topics” in symmetric cryptography in the recent years. A huge number of lightweight algorithms have been published, standardized and/or used in commercial products. In this paper, we discuss the different implementation constraints that a “lightweight” algorithm is usually designed to satisfy. We also present an extensive survey of all lightweight symmetric primitives we are aware of. It covers designs from the academic community, from government agencies and proprietary algorithms which were reverse-engineered or leaked. Relevant national (nist...) and international (iso/iec...) standards are listed. We then discuss some trends we identified in the design of lightweight algorithms, namely the designers’ preference for arx-based and bitsliced-S-Box-based designs and simple key schedules. Finally, we argue that lightweight cryptography is too large a field and that it should be split into two related but distinct areas: ultra-lightweight and IoT cryptography. The former deals only with the smallest of devices for which a lower security level may be justified by the very harsh design constraints. The latter corresponds to low-power embedded processors for which the Aes and modern hash function are costly but which have to provide a high level security due to their greater connectivity. Keywords: Lightweight cryptography · Ultra-Lightweight · IoT · Internet of Things · SoK · Survey · Standards · Industry 1 Introduction The Internet of Things (IoT) is one of the foremost buzzwords in computer science and information technology at the time of writing.
    [Show full text]
  • Exponential S-Boxes: a Link Between the S-Boxes of Belt and Kuznyechik/Streebog
    Exponential S-Boxes: a Link Between the S-Boxes of BelT and Kuznyechik/Streebog Léo Perrin and Aleksei Udovenko SnT, University of Luxembourg {leo.perrin,aleksei.udovenko}@uni.lu Abstract. The block cipher Kuznyechik and the hash function Streebog were recently standardized by the Russian Federation. These primitives use a common 8-bit S-Box, denoted 휋, which is given only as a look-up table. The rationale behind its design is, for all practical purposes, kept secret by its authors. In a paper presented at Eurocrypt 2016, Biryukov et al. reverse-engineered this S-Box and recovered an unusual Feistel-like structure relying on finite field multiplications. In this paper, we provide a new decomposition of this S-Box and describe how we obtained it. The first step was the analysis of the 8-bit S-Box of the current standard block cipher of Belarus, BelT. This S-Box is a variant of a so-called exponential substitution, a concept we generalize into pseudo-exponential substitution. We derive distinguishers for such permutations based on properties of their linear approximation tables and notice that 휋 shares some of them. We then show that 휋 indeed has a decomposition based on a pseudo-exponential substitution. More precisely, we obtain a simpler structure based on an 8-bit finite field exponentiation, one 4-bit S-Box, a linear layer and a few modular arithmetic operations. We also make several observations which may help cryptanalysts attempting to reverse-engineer other S-Boxes. For example, the visual pattern used in the previous work as a starting point to decompose 휋 is mathematically formalized and the use of differential patterns involving operations other than exclusive-or is explored.
    [Show full text]
  • Streebog and Kuznyechik Inconsistencies in the Claims of Their Designers
    Streebog and Kuznyechik Inconsistencies in the Claims of their Designers Léo Perrin [email protected] @lpp_crypto IETF Workshop, Montréal Standards and S-boxes On the S-box of RFC 6986 and 7801 The Core Issue: the S-Box Generation Process Conclusion Partitions in the S-Box of Streebog and Kuznyechik Transactions in Symmetric Léo Perrin Inria, France [email protected] Cryptology, Volume 2019, No. 1, pp. Abstract. Streebog and Kuznyechik are the latest symmetric cryptographic primitives standardized by the Russian GOST. They share the same S-Box, 휋, whose design process was not described by its authors. In previous works, Biryukov, Perrin and 302-329. Best paper award! Udovenko recovered two completely different decompositions of this S-Box. We revisit their results and identify a third decomposition of 휋. It is an instance of a fairly small family of permutations operating on 2푚 bits which we call TKlog and which is closely related tofnitefeld logarithms. Its simplicity and the small number of components it uses lead us to claim that it has to be the structure intentionally used by the designers of Streebog and Kuznyechik. The 2푚-bit permutations of this type have a very strong algebraic structure: they 푚 푚 map multiplicative cosets of the subfield GF(2 )* to additive cosets of GF(2 )*. Furthermore, the function relating each multiplicative coset to the corresponding additive coset is always essentially the same. To the best of our knowledge, we are thefrst to expose this very strong algebraic structure. We also investigate other properties of the TKlog and show in particular that it can always be decomposed in a fashion similar to thefrst decomposition of Biryukov et al., thus explaining the relation between the two previous decompositions.
    [Show full text]
  • Performance Analysis of Cryptographic Hash Functions Suitable for Use in Blockchain
    I. J. Computer Network and Information Security, 2021, 2, 1-15 Published Online April 2021 in MECS (http://www.mecs-press.org/) DOI: 10.5815/ijcnis.2021.02.01 Performance Analysis of Cryptographic Hash Functions Suitable for Use in Blockchain Alexandr Kuznetsov1 , Inna Oleshko2, Vladyslav Tymchenko3, Konstantin Lisitsky4, Mariia Rodinko5 and Andrii Kolhatin6 1,3,4,5,6 V. N. Karazin Kharkiv National University, Svobody sq., 4, Kharkiv, 61022, Ukraine E-mail: [email protected], [email protected], [email protected], [email protected], [email protected] 2 Kharkiv National University of Radio Electronics, Nauky Ave. 14, Kharkiv, 61166, Ukraine E-mail: [email protected] Received: 30 June 2020; Accepted: 21 October 2020; Published: 08 April 2021 Abstract: A blockchain, or in other words a chain of transaction blocks, is a distributed database that maintains an ordered chain of blocks that reliably connect the information contained in them. Copies of chain blocks are usually stored on multiple computers and synchronized in accordance with the rules of building a chain of blocks, which provides secure and change-resistant storage of information. To build linked lists of blocks hashing is used. Hashing is a special cryptographic primitive that provides one-way, resistance to collisions and search for prototypes computation of hash value (hash or message digest). In this paper a comparative analysis of the performance of hashing algorithms that can be used in modern decentralized blockchain networks are conducted. Specifically, the hash performance on different desktop systems, the number of cycles per byte (Cycles/byte), the amount of hashed message per second (MB/s) and the hash rate (KHash/s) are investigated.
    [Show full text]
  • Improved Generic Attacks Against Hash-Based Macs and HAIFA⋆
    Improved Generic Attacks Against Hash-based MACs and HAIFA? Itai Dinur1 and Ga¨etanLeurent2 1 D´epartement d'Informatique, Ecole´ Normale Sup´erieure,Paris, France [email protected] 2 Inria, EPI SECRET, France [email protected] Abstract. The security of HMAC (and more general hash-based MACs) against state-recovery and universal forgery attacks was very recently shown to be suboptimal, following a series of surprising results by Leurent et al. and Peyrin et al.. These results have shown that such powerful attacks require much less than 2` computations, contradicting the common belief (where ` denotes the internal state size). In this work, we revisit and extend these results, with a focus on properties of concrete hash functions such as a limited message length, and special iteration modes. We begin by devising the first state-recovery attack on HMAC with a HAIFA hash function (using a block counter in every compression function call), with complexity 24`=5. Then, we describe improved trade- offs between the message length and the complexity of a state-recovery attack on HMAC. Consequently, we obtain improved attacks on several HMAC constructions used in practice, in which the hash functions limit the maximal message length (e.g., SHA-1 and SHA-2). Finally, we present the first universal forgery attacks, which can be applied with short message queries to the MAC oracle. In particular, we devise the first universal forgery attacks applicable to SHA-1 and SHA-2. Keywords: Hash functions, MAC, HMAC, Merkle-Damg˚ard,HAIFA, state-recovery attack, universal forgery attack, GOST, Streebog, SHA family.
    [Show full text]
  • SPHINCS $^+ $ Post-Quantum Digital Signature Scheme with Streebog
    SPHINCS+ post-quantum digital signature scheme with Streebog hash function E.O. Kiktenko1,2, A.A. Bulychev1, P.A. Karagodin1,2, N.O. Pozhar1,2, M.N. Anufriev1,2 and A.K. Fedorov1,2 a)Corresponding author: [email protected] (E.O.K.) b)Corresponding author: [email protected] (A.K.F.) 1Russian Quantum Center, Skolkovo, Moscow 143025, Russia 2QApp, Skolkovo, Moscow 143025, Russia Abstract. Many commonly used public-key cryptosystems will become insecure once a scalable quantum computer is built. New cryptographic schemes that can guarantee protection against attacks with quantum computers, so-called post-quantum algorithms, have emerged in recent decades. One of the most promising candidates for a post-quantum signature scheme is SPHINCS+, which is based on cryptographic hash functions. In this contribution, we analyze the use of the new Russian standardized hash function, known as Streebog, for the implementation of the SPHINCS+ signature scheme. We provide a performance comparison with SHA-256-based instantiation and give benchmarks for various sets of parameters. Introduction Public-key cryptography is a cornerstone of internet security. Quantum computers possess a threat to the widely deployed public-key cryptography schemes, whose security is based on the computational complexity of certain tasks, such as integer factorization and discrete logarithm. Shor’s quantum algorithm [1] and variational quantum factor- ing [2] would allow one to solve these tasks with a significant boost [3]. Quantum computers have less of an effect on symmetric cryptography since Shor’s algorithm does not apply for their cryptoanalysis. Nevertheless, Grover’s algorithm [4] would allow quantum computers a quadratic speedup in brute force attacks.
    [Show full text]
  • General Classification of the Authenticated Encryption Schemes
    Computer Science Review ( ) – Contents lists available at ScienceDirect Computer Science Review journal homepage: www.elsevier.com/locate/cosrev Survey General classification of the authenticated encryption schemes for the CAESAR competition Farzaneh Abed ∗, Christian Forler, Stefan Lucks Bauhaus-Universität Weimar, Germany article info a b s t r a c t Article history: An authenticated encryption scheme is a scheme which provides privacy and integrity by using a Received 25 August 2015 secret key. In 2013, CAESAR (the ``Competition for Authenticated Encryption: Security, Applicability, Received in revised form and Robustness'') was co-founded by NIST and Dan Bernstein with the aim of finding authenticated 11 July 2016 encryption schemes that offer advantages over AES-GCM and are suitable for widespread adoption. The Accepted 25 July 2016 first round started with 57 candidates in March 2014; and nine of these first-round candidates were Available online xxxx broken and withdrawn from the competition. The remaining 48 candidates went through an intense process of review, analysis and comparison. While the cryptographic community benefits greatly from the Keywords: Authenticated encryption manifold different submission designs, their sheer number implies a challenging amount of study. This CAESAR competition paper provides an easy-to-grasp overview over functional aspects, security parameters, and robustness Symmetric cryptography offerings by the CAESAR candidates, clustered by their underlying designs (block-cipher-, stream-cipher- , permutation-/sponge-, compression-function-based, dedicated). After intensive review and analysis of all 48 candidates by the community, the CAESAR committee selected only 30 candidates for the second round. The announcement for the third round candidates was made on 15th August 2016 and 15 candidates were chosen for the third round.
    [Show full text]
  • Improved Generic Attacks Against Hash-Based Macs and HAIFA
    Introduction State-recovery for HMAC-HAIFA Short message attacks Improved Generic Attacks Against Hash-based MACs and HAIFA Itai Dinur1 Gaëtan Leurent2 1ENS, France 2Inria, France Crypto 2014 I. Dinur & G. Leurent (ENS & Inria) Improved Generic Attacks Against Hash-based MACs and HAIFA Crypto 2014 1 / 21 Introduction State-recovery for HMAC-HAIFA Short message attacks HMAC with GOST HMAC GOST R 34.11-94 I Very common MAC algorithm I Russian hash funct. standard H(K ⊕ opad k H(K ⊕ ipad k M)) I Uses an internal checksum HMAC-GOST K ⊕ ipad M0 M1 M2 jMj K ⊕ opad h IV h h h h g IV h h g t I Expect ` bit security for key-recovery (`-bit state, key, tag) ` I Key recovery attack in 23 /4 [LPW, AC 2013] I. Dinur & G. Leurent (ENS & Inria) Improved Generic Attacks Against Hash-based MACs and HAIFA Crypto 2014 2 / 21 Introduction State-recovery for HMAC-HAIFA Short message attacks HMAC with GOST HMAC GOST R 34.11-94 I Very common MAC algorithm I Russian hash funct. standard H(K ⊕ opad k H(K ⊕ ipad k M)) I Uses an internal checksum HMAC-GOST K ⊕ ipad M0 M1 M2 jMj K ⊕ opad h IV h h h h g IV h h g t I Expect ` bit security for key-recovery (`-bit state, key, tag) ` I Key recovery attack in 23 /4 [LPW, AC 2013] I. Dinur & G. Leurent (ENS & Inria) Improved Generic Attacks Against Hash-based MACs and HAIFA Crypto 2014 2 / 21 Introduction State-recovery for HMAC-HAIFA Short message attacks HMAC with GOST HMAC GOST R 34.11-94 I Very common MAC algorithm I Russian hash funct.
    [Show full text]
  • Simple AEAD Hardware Interface (SÆHI) in a Soc: Implementing an On-Chip Keyak/Whirlbob Coprocessor
    Simple AEAD Hardware Interface (SÆHI) in a SoC: Implementing an On-Chip Keyak/WhirlBob Coprocessor Markku-Juhani O. Saarinen Norwegian University of Science and Technology Department of Telematics, O.S. Bragstads plass 2a N-7491 Trondheim, NORWAY [email protected] ABSTRACT 1. INTRODUCTION Simple AEAD Hardware Interface (SÆHI) is a hardware An Authenticated Encryption with Associated Data algo- cryptographic interface aimed at CAESAR Authenticated rithm (AEAD) provides both confidentiality and integrity Encryption with Associated Data (AEAD) algorithms. Cryp- protection in a single operation. AEADs are often more ef- tographic acceleration is typically achieved either with a co- fective alternatives to traditional encryption methods such processor or via instruction set extensions. ISA modifica- as block cipher modes [11] or stream ciphers (e.g. RC4 [26]), tions require re-engineering the CPU core, making the ap- which had to be paired with suitable Message Authentica- proach inapplicable outside the realm of open source proces- tion Codes (typically HMAC [21]) in transport layers of se- sor cores. At minimum, we suggest implementing CAESAR curity protocols such as TLS [10], IPSec [16], and SSH [36]. AEADs as universal memory-mapped cryptographic copro- A basic AEAD algorithm C =Æ(K; N; A; P ) produces an cessors, synthesizable even on low end FPGA platforms. authenticated ciphertext message C from following inputs: AEADs complying to SÆHI must also include C language K Secret key shared between the sender and recipient. API drivers targeting low-end MCUs that directly utilize the memory mapping in a \bare metal" fashion. This can also N Initialization vector, nonce, or message sequence num- be accommodated on MMU-equipped mid-range CPUs.
    [Show full text]
  • Stribobr2: “WHIRLBOB”
    STRIBOBr2: “WHIRLBOB” Second Round CAESAR Algorithm Tweak Specification Pricipal Submitter Markku-Juhani O. Saarinen [email protected] Queen’s University Belfast, UK Billy B. Brumley [email protected] Tampere University of Technology, Finland August 28, 2015 For updates and further information: http://www.stribob.com Contents Preface and Introduction 1 1 Specification 2 1.1 Structure of the π Permutation .................................. 2 1.1.1 Substitution S or SubBytes ................................ 2 1.1.2 Permutation P or ShiftColumns ............................. 2 1.1.3 Linear operation L or MixRows .............................. 3 1.1.4 Constants Cr or AddRoundKey ............................... 3 1.1.5 Code for π Computation .................................. 4 1.2 BLNK Sponge Mode and Padding ................................ 5 1.2.1 BLNK Block Operations .................................. 5 1.2.2 The CAESAR encrypt() and decrypt() AEAD API .................... 6 1.3 Test Vectors ............................................. 7 1.3.1 The 12-round π transform ................................. 7 1.3.2 Authenticated Encryption ................................. 8 2 Security Goals 9 2.1 Specific Goals ............................................ 9 2.2 Nonce Re-Use ............................................ 9 2.3 General Goals ............................................ 9 3 Security Analysis 10 3.1 Attacks on the Sponge AEAD Mode BLNK ........................... 10 3.2 The π Permutation ........................................
    [Show full text]
  • Reverse-Engineering the S-Box of Streebog, Kuznyechik and Stribobr1 (Full Version)⋆
    Reverse-Engineering the S-Box of Streebog, Kuznyechik and STRIBOBr1 (Full Version)? Alex Biryukov1, L´eoPerrin2, and Aleksei Udovenko3 1 [email protected], University of Luxembourg 2 [email protected], SnT,University of Luxembourg 3 [email protected], SnT,University of Luxembourg Abstract. The Russian Federation's standardization agency has recently published a hash function called Streebog and a 128-bit block cipher called Kuznyechik. Both of these algorithms use the same 8-bit S-Box but its design rationale was never made public. In this paper, we reverse-engineer this S-Box and reveal its hidden struc- ture. It is based on a sort of 2-round Feistel Network where exclusive-or is replaced by a finite field multiplication. This structure is hidden by two different linear layers applied before and after. In total, five differ- ent 4-bit S-Boxes, a multiplexer, two 8-bit linear permutations and two finite field multiplications in a field4 ofsize2 are needed to compute the S-Box. The knowledge of this decomposition allows a much more efficient hard- ware implementation by dividing the area and the delay by 2.5 and 8 respectively. However, the small 4-bit S-Boxes do not have very good cryptographic properties. In fact, one of them has a probability 1 differ- ential. We then generalize the method we used to partially recover the linear layers used to whiten the core of this S-Box and illustrate it with a generic decomposition attack against 4-round Feistel Networks whitened with unknown linear layers. Our attack exploits a particular pattern arising in the Linear Approximations Table of such functions.
    [Show full text]
  • Arxiv:2001.00515V1 [Cs.CR] 2 Jan 2020 – Use of Backdoor Techniques, Whether Software Or Hardware, Equipment Trapping Or Bugging [8,16,17,20]
    Key-dependent Security of Stream Ciphers? Eric Filiol ENSIBS, Vannes, France CNAM, Paris, France [email protected] Keywords: Cryptography, Encryption Algorithms, Backdoor, Cryptanalysis, Stream Cipher, Cryptographic control, Cryptology History Abstract. The control of the cryptography is more than ever a recurrent issue. As the current international regulation does not apply in the signatory countries, the concept of enforcing backdoors in encryption system is reborn with more strength. This paper deals with a particular class of stream cipher backdoors. This class, under a different form, has been widely used by the industry in the 80s and 90s in the context of the export control rules imposed by the US to the Western countries. We propose here a new system – called BSEA-2, with a 128-bit secret key – which is a seemingly minor modification of BSEA-1, a system proposed in [11]. BSEA-2 illustrates, in a simple and didactic — it has been also designed for a MSc cryptanalysis course — but efficient way the concept of key-dependent cryptographic security. The aim is to keep control on encryption means that a country/provider could provide to another country/client for which the secret key are also provided. With such systems, changing the key class results in downgrading the cryptographic security. 1 Introduction The use of cryptography must be done with confidence in those technologies. However since the end of the Second World War cryptography and the wider field of SIGINT have become an extremely sensitive subject. Since the end of the 1940s, encryption means have been considered as military or dual-use technologies — and still are — and are therefore subject to increased control mainly by the USA and a very limited circle of allies (ANZUS and UKUSA).
    [Show full text]