Practical State Recovery Attacks Against Legacy RNG Implementations
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
Making Sense of Snowden, Part II: What's Significant in the NSA
web extra Making Sense of Snowden, Part II: What’s Significant in the NSA Revelations Susan Landau, Google hen The Guardian began publishing a widely used cryptographic standard has vastly wider impact, leaked documents from the National especially because industry relies so heavily on secure Inter- Security Agency (NSA) on 6 June 2013, net commerce. Then The Guardian and Der Spiegel revealed each day brought startling news. From extensive, directed US eavesdropping on European leaders7 as the NSA’s collection of metadata re- well as broad surveillance by its fellow members of the “Five cords of all calls made within the US1 Eyes”: Australia, Canada, New Zealand, and the UK. Finally, to programs that collected and stored data of “non-US” per- there were documents showing the NSA targeting Google and W2 8,9 sons to the UK Government Communications Headquarters’ Yahoo’s inter-datacenter communications. (GCHQs’) interception of 200 transatlantic fiberoptic cables I summarized the initial revelations in the July/August is- at the point where they reached Britain3 to the NSA’s pene- sue of IEEE Security & Privacy.10 This installment, written in tration of communications by leaders at the G20 summit, the late December, examines the more recent ones; as a Web ex- pot was boiling over. But by late June, things had slowed to a tra, it offers more details on the teaser I wrote for the January/ simmer. The summer carried news that the NSA was partially February 2014 issue of IEEE Security & Privacy magazine funding the GCHQ’s surveillance efforts,4 and The Guardian (www.computer.org/security). -
NSA's Efforts to Secure Private-Sector Telecommunications Infrastructure
Under the Radar: NSA’s Efforts to Secure Private-Sector Telecommunications Infrastructure Susan Landau* INTRODUCTION When Google discovered that intruders were accessing certain Gmail ac- counts and stealing intellectual property,1 the company turned to the National Security Agency (NSA) for help in securing its systems. For a company that had faced accusations of violating user privacy, to ask for help from the agency that had been wiretapping Americans without warrants appeared decidedly odd, and Google came under a great deal of criticism. Google had approached a number of federal agencies for help on its problem; press reports focused on the company’s approach to the NSA. Google’s was the sensible approach. Not only was NSA the sole government agency with the necessary expertise to aid the company after its systems had been exploited, it was also the right agency to be doing so. That seems especially ironic in light of the recent revelations by Edward Snowden over the extent of NSA surveillance, including, apparently, Google inter-data-center communications.2 The NSA has always had two functions: the well-known one of signals intelligence, known in the trade as SIGINT, and the lesser known one of communications security or COMSEC. The former became the subject of novels, histories of the agency, and legend. The latter has garnered much less attention. One example of the myriad one could pick is David Kahn’s seminal book on cryptography, The Codebreakers: The Comprehensive History of Secret Communication from Ancient Times to the Internet.3 It devotes fifty pages to NSA and SIGINT and only ten pages to NSA and COMSEC. -
The Legacy of Export-Grade Cryptography in the 21St Century
The legacy of export-grade cryptography in the 21st century Nadia Heninger University of Pennsylvania October 6, 2016 International Traffic in Arms Regulations April 1, 1992 version Category XIII--Auxiliary Military Equipment ... (b) Information Security Systems and equipment, cryptographic devices, software, and components specifically designed or modified therefore, including: (1) Cryptographic (including key management) systems, equipment, assemblies, modules, integrated circuits, components or software with the capability of maintaining secrecy or confidentiality of information or information systems, except cryptographic equipment and software as follows: (i) Restricted to decryption functions specifically designed to allow the execution of copy protected software, provided the decryption functions are not user-accessible. (ii) Specially designed, developed or modified for use in machines for banking or money transactions, and restricted to use only in such transactions. Machines for banking or money transactions include automatic teller machines, self-service statement printers, point of sale terminals or equipment for the encryption of interbanking transactions. ... Timeline of US cryptography export control I Pre-1994: Encryption software requires individual export license as a munition. I 1994: US State Department amends ITAR regulations to allow export of approved software to approved countries without individual licenses. 40-bit symmetric cryptography was understood to be approved under this scheme. I 1995: Netscape develops initial SSL protocol. I 1996: Bernstein v. United States; California judge rules ITAR regulations are unconstitutional because \code is speech" I 1996: Cryptography regulation moved to Department of Commerce. I 1999: TLS 1.0 standardized. I 2000: Department of Commerce loosens regulations on mass-market and open source software. Commerce Control List: Category 5 - Info. -
Comments Received on Special Publication 800-90A, B and C
Comments Received on SP 800-90A On 9/11/13 12:06 AM, "Robert Bushman" <[email protected]> wrote: "Draft Special Publication 800-90A, Recommendation for Random Number Generation Using Deterministic Random Bit Generators" cannot be trusted to secure our citizens and corporations from cyber-attack, for reasons that should be quite apparent. Please terminate it or replace the PRNG algorithm without the participation of the NSA. On 9/21/13 1:25 PM, "peter bachman" <[email protected]> wrote: See enclosed random.pdf for comment (A picture was attached) From: Mike Stephens <[email protected]> Date: Friday, October 18, 2013 2:47 PM Remove DUAL_EC_DRBG from SP 800-90. [MS] 1 10.3 Page 60 te Published cryptanalysis shows that Dual EC DRBG outputs are biased. This should disqualify the algorithm from inclusion in the standard.i ii [MS] 2 10.3 Page 60 ge Recent publications regarding Dual EC DRBG have significantly compromised public trust in the algorithm to the extent that correcting any mathematical properties of Remove DUAL_EC_DRBG from SP 800-90. the algorithm would not regenerate confidence in it. Continued inclusion of Dual EC DRBG will harm the credibility of the SP-800 series of standards. [MS] 3 11 Page 72 ge The SP-800 series standardizes algorithms, not implementation aspects. Self-test requirements should come from FIPS 140-2. The current self-test requirements in SP 800-90 do not align with or cooperate with FIPS 140-2 Remove self-test requirements from SP800-90. requirements. Should the self-test requirements remain in SP 800-90; then, harmonize these requirements with those in FIPS 140. -
Crypto Won't Save You Either Sound Advice from The
14/01/2016 Crypto Won’t Save You Either Peter Gutmann University of Auckland Sound Advice from the USG 1 14/01/2016 Saw Something, Said Something Saw Something, Said Something (ctd) You’re not paranoid, they really are out to get you 2 14/01/2016 BULLRUN Funded to the tune of $250-300M/year BULLRUN (ctd) This is fantastic value for money! Compare the BULLRUN cost to the JSF • $60 billion development • $260 billion procurement • $100-200 million each (lots of different cost estimates) • $600-700 million each over operational lifetime BULLRUN is a bargain by comparison 3 14/01/2016 BULLRUN (ctd) “capabilities against TLS/SSL, HTTPS, SSH, VPNs, VoIP, webmail, ...” BULLRUN (ctd) “aggressive effort to defeat network security and privacy” “defeat the encryption used in network communication technologies” 4 14/01/2016 BULLRUN (ctd) The first rule of BULLRUN club… What’s that NSAie? Crypto’s fallen in the well? 5 14/01/2016 I Know, Bigger Keys! We need to get bigger keys. BIG F**ING KEYS! — “Split Second”, 1992 Quick, do something! Cue the stannomillinery 6 14/01/2016 Crypto Won’t Save You Shamir’s Law: Crypto is bypassed, not penetrated Cryptography is usually bypassed. I am not aware of any major world-class security system employing cryptography in which the hackers penetrated the system by actually going through the cryptanalysis […] usually there are much simpler ways of penetrating the security system — Adi Shamir Example: Games Consoles All of the major consoles use fairly extensive amounts of sophisticated cryptography • PS3 • Wii • Xbox -
How to (Pre-)Compute a Ladder
How to (pre-)compute a ladder Improving the performance of X25519 and X448 Thomaz Oliveira1, Julio L´opez2, H¨useyinHı¸sıl3, Armando Faz-Hern´andez2, and Francisco Rodr´ıguez-Henr´ıquez1 1 Computer Science Department, Cinvestav-IPN [email protected], [email protected] 2 Institute of Computing, University of Campinas [email protected], [email protected] 3 Yasar University [email protected] Abstract. In the RFC 7748 memorandum, the Internet Research Task Force specified a Montgomery-ladder scalar multiplication function based on two recently adopted elliptic curves, \curve25519" and \curve448". The purpose of this function is to support the Diffie-Hellman key ex- change algorithm that will be included in the forthcoming version of the Transport Layer Security cryptographic protocol. In this paper, we describe a ladder variant that permits to accelerate the fixed-point mul- tiplication function inherent to the Diffie-Hellman key pair generation phase. Our proposal combines a right-to-left version of the Montgomery ladder along with the pre-computation of constant values directly de- rived from the base-point and its multiples. To our knowledge, this is the first proposal of a Montgomery ladder procedure for prime elliptic curves that admits the extensive use of pre-computation. In exchange of very modest memory resources and a small extra programming effort, the proposed ladder obtains significant speedups for software implemen- tations. Moreover, our proposal fully complies with the RFC 7748 spec- ification. A software implementation of the X25519 and X448 functions using our pre-computable ladder yields an acceleration factor of roughly 1.20, and 1.25 when implemented on the Haswell and the Skylake micro- architectures, respectively. -
Lest We Remember: Cold Boot Attacks on Encryption Keys
Lest We Remember: Cold Boot Attacks on Encryption Keys J. Alex Halderman*, Seth D. Schoen†, Nadia Heninger*, William Clarkson, William Paul‡, Joseph A. Calandrino*, Ariel J. Feldman*, Jacob Appelbaum and Edward W. Felten* *Princeton University †Electronic Frontier Foundation ‡Wind River Systems USENIX Security Symposium, 2008 Presented by: Andra-Maria Ilieș Seminar in Computer Architecture 1 Executive summary ■ Problem: DRAMs lose their data gradually after the power is cut ■ Goal: Present a new type of attack which exploits remanence effect ■ Method: ■ Acquire usable full-system memory image ■ Extract cryptographic key ■ Gain access to secret data ■ Evaluation: succeeded on most popular disk encryption systems 2 Background, Problem & Goal 3 DRAM ■ A DRAM cell consists of a capacitor and an access transistor. ■ It stores data in terms of change in the capacitor. wordline access transistor bitline bitline storage bitline capacitor 4 DRAM refresh ■ DRAM capacitor charge leaks over time ■ Each DRAM row is refreshed periodically to restore charge ■ Period usually is 64 ms ■ Retention time: maximum time a cell can go without being refreshed while maintaining its stored data ■ Decay: bit flips caused by charge leak ■ Cell leak = cell decays to ground state ■ When powered off DRAM loses its data completely 5 Retention time and temperature ■ Contents survive at some extent even at room temperature ■ LINK, W., AND MAY, H. Eigenschaften von MOS - Ein Transistorspeicherzellen bei tiefen Temperaturen. Archiv fur Elekotronik und Ubertragungstechnik 33 (June 1979), 229–235 ■ DRAM showed no data loss for a full week without refresh when cooled with liquid nitrogen ■ Retention time can be increased by cooling 6 Retention time and booting ■ Chow, Jim & Pfaff, Ben & Garfinkel, Tal & Rosenblum, Mendel. -
Case 2:16-Cv-06287-PD Document 8 Filed 12/06/16 Page 1 of 74
Case 2:16-cv-06287-PD Document 8 Filed 12/06/16 Page 1 of 74 Case 2:16-cv-06287-PD Document 8 Filed 12/06/16 Page 2 of 74 Case 2:16-cv-06287-PD Document 8 Filed 12/06/16 Page 3 of 74 Case 2:16-cv-06287-PD Document 8 Filed 12/06/16 Page 4 of 74 Case 2:16-cv-06287-PD Document 8 Filed 12/06/16 Page 5 of 74 Case 2:16-cv-06287-PD Document 8 Filed 12/06/16 Page 6 of 74 Case 2:16-cv-06287-PD Document 8 Filed 12/06/16 Page 7 of 74 Case 2:16-cv-06287-PD Document 8 Filed 12/06/16 Page 8 of 74 Case 2:16-cv-06287-PD Document 8 Filed 12/06/16 Page 9 of 74 Case 2:16-cv-06287-PD Document 8 Filed 12/06/16 Page 10 of 74 Case 2:16-cv-06287-PD Document 8 Filed 12/06/16 Page 11 of 74 Case 2:16-cv-06287-PD Document 8 Filed 12/06/16 Page 12 of 74 Case 2:16-cv-06287-PD Document 8 Filed 12/06/16 Page 13 of 74 Case 2:16-cv-06287-PD Document 8 Filed 12/06/16 Page 14 of 74 Case 2:16-cv-06287-PD Document 8 Filed 12/06/16 Page 15 of 74 Case 2:16-cv-06287-PD Document 8 Filed 12/06/16 Page 16 of 74 Exhibit A Case 2:16-cv-06287-PD Document 8 Filed 12/06/16 Page 17 of 74 J. -
ACLU V. Clapper
Case 1:13-cv-03994-WHP Document 27 Filed 08/26/13 Page 1 of 35 UNITED STATES DISTRICT COURT SOUTHERN DISTRICT OF NEW YORK AMERICAN CIVIL LIBERTIES UNION; AMERICAN CIVIL LIBERTIES UNION FOUNDATION; NEW YORK CIVIL LIBERTIES UNION; and NEW YORK CIVIL LIBERTIES UNION FOUNDATION, Plaintiffs, DECLARATION OF PROFESSOR v. EDWARD W. FELTEN JAMES R. CLAPPER, in his official capacity as Director of National Intelligence; KEITH B. Case No. 13-cv-03994 (WHP) ALEXANDER, in his official capacity as Director of the National Security Agency and Chief of the ECF CASE Central Security Service; CHARLES T. HAGEL, in his official capacity as Secretary of Defense; ERIC H. HOLDER, in his official capacity as Attorney General of the United States; and ROBERT S. MUELLER III, in his official capacity as Director of the Federal Bureau of Investigation, Defendants. DECLARATION OF PROFESSOR EDWARD W. FELTEN I, Edward W. Felten, declare under penalty of perjury, pursuant to 28 U.S.C. § 1746, that the following is true and correct: 1. The plaintiffs in this lawsuit have challenged what they term the “mass call-tracking” program of the National Security Agency, and they have asked me to explain the sensitive nature of metadata, particularly when obtained in the aggregate. Below, I discuss how advances in technology and the proliferation of metadata-producing devices, such as phones, have produced rich metadata trails. Many details of our lives can be gleaned by examining those trails, which often yield information more easily than do the actual content of our communications. Case 1:13-cv-03994-WHP Document 27 Filed 08/26/13 Page 2 of 35 Superimposing our metadata trails onto the trails of everyone within our social group and those of everyone within our contacts’ social groups, paints a picture that can be startlingly detailed. -
Chacha20-Poly1305 の実装性能調査
ChaCha20-Poly1305 の実装性能調査 株式会社レピダム 2017 年 10 月 目 次 第 1 章 エグゼクティブサマリー 3 第 2 章 ChaCha20-Poly1305 について 4 2.1 概要 :::::::::::::::::::::::::::::: 4 2.2 歴史的背景 :::::::::::::::::::::::::: 5 2.3 アルゴリズムの構造 ::::::::::::::::::::: 5 2.3.1 ChaCha20 ::::::::::::::::::::::: 5 2.3.2 Poly1305 ::::::::::::::::::::::: 7 2.3.3 ChaCha20-Poly1305 ::::::::::::::::: 8 第 3 章 ChaCha20-Poly1305 の採用状況 11 3.1 標準化動向 :::::::::::::::::::::::::: 11 3.1.1 IETF ::::::::::::::::::::::::: 11 3.1.2 その他の標準化団体 ::::::::::::::::: 14 3.2 OSS コミュニティ動向 :::::::::::::::::::: 14 第 4 章 ChaCha20-Poly1305 の実装性能評価に関する既存文献調 査 17 4.1 論文調査 :::::::::::::::::::::::::::: 17 4.2 ベンチマーク実装評価調査 :::::::::::::::::: 18 4.2.1 Cloudflare 版 OpenSSL ::::::::::::::: 19 4.2.2 Edge Security の WireGuard :::::::::::: 20 4.2.3 Barco Silex の BA417 と Inside Secure の ChaCha- IP-13 / EIP-13, POLY-IP-53 / EIP-53 ::::::: 22 第 5 章 認証暗号方式の性能比較調査 24 5.1 性能比較調査方法 ::::::::::::::::::::::: 24 5.1.1 比較対象アルゴリズム :::::::::::::::: 24 5.1.2 実行環境 :::::::::::::::::::::::: 32 5.1.3 暗号ライブラリ :::::::::::::::::::: 34 5.2 実行コマンド ::::::::::::::::::::::::: 35 5.3 性能比較結果 ::::::::::::::::::::::::: 37 5.3.1 AES-NI 有効の場合 ::::::::::::::::: 37 1 5.3.2 AES-NI 無効の場合 ::::::::::::::::: 46 5.3.3 性能測定における注意点 ::::::::::::::: 51 5.4 考察 :::::::::::::::::::::::::::::: 52 5.4.1 Poly1305 によるオーバーヘッド ::::::::::: 52 5.4.2 AES-NI の影響 :::::::::::::::::::: 53 5.4.3 ChaCha20-Poly1305 と AES-GCM の比較 ::::: 53 第 6 章 まとめ 54 Arm, Cortex, mbed は Arm Limited の登録商標です。 Cloudflare は Cloudflare, Inc の登録商標です。 Google は Google LLC の登録商標です。 Inside Secure は Inside Secure またはその子会社の登録商標です。 Intel は Intel Corporation またはその子会社の登録商標です。 WireGuard は Jason A. Donenfeld の登録商標です。 AVR は Microchip Technology Incorporated の登録商標です。 OpenSSL は OpenSSL Software Foundation の登録商標です。 OpenVPN は OpenVPN Inc. -
Cryptgenrandom()
(Pseudo)Random Data PA193 – Secure coding Petr Švenda Zdeněk Říha Faculty of Informatics, Masaryk University, Brno, CZ Need for “random” data • Games • Simulations, … • Crypto – Symmetric keys – Asymmetric keys – Padding/salt – Initialization vectors – Challenges (for challenge – response protocols) – … “Random” data • Sometimes (games, simulations) we only need data with some statistical properties – Evenly distributed numbers (from an interval) – Long and complete cycle • Large number of different values • All values can be generated • In crypto we also need unpredictability – Even if you have seen all the “random” data generated until now you have no idea what will be the random data generated next “Random” data generators • Insecure random number generators – noncryptographic pseudo-random number generators – Often leak information about their internal state with each output • Cryptographic pseudo-random number generators (PRNGs) – Based on seed deterministically generate pseudorandom data • “True” random data generators – Entropy harvesters – gather entropy from other sources and present it directly What (pseudo)random data to use? • Avoid using noncryptographic random number generators • For many purposes the right way is to get the seed from the true random number generator and then use it in the pseudorandom number generator (PRNG) – PRNG are deterministic, with the same seed they produce the same pseudorandom sequence • There are situations, where PRNG are not enough – E.g. one time pad Noncryptographic generators • Standard rand()/srand(), random ()/srandom() functions – libc • “Mersenne Twister” • linear feedback shift registers • Anything else not labeled as cryptographic PRNG… • Not to be used for most purposes…. Noncryptographic generators Source: Writing secure code, 2nd edition Source: http://xkcd.com/ PRNG • Cryptographic pseudo-random number generators are still predictable if you somehow know their internal state. -
Cold Boot Attacks on Encryption Keys
Lest We Remember: Cold Boot Attacks on Encryption Keys † ‡ J. Alex Halderman∗, Seth D. Schoen , Nadia Heninger∗, William Clarkson∗, William Paul , Joseph A. Calandrino∗, Ariel J. Feldman∗, Jacob Appelbaum, and Edward W. Felten∗ † ‡ ∗ Princeton University Electronic Frontier Foundation Wind River Systems jhalderm, nadiah, wclarkso, jcalandr, ajfeldma, felten @cs.princeton.edu { } [email protected], [email protected], [email protected] Abstract memory. They pose a particular threat to laptop users who rely on disk encryption products, since an adversary who Contrary to popular assumption, DRAMs used in most steals a laptop while an encrypted disk is mounted could modern computers retain their contents for several sec- employ our attacks to access the contents, even if the com- onds after power is lost, even at room temperature and puter is screen-locked or suspended. We demonstrate this even if removed from a motherboard. Although DRAMs risk by defeating several popular disk encryption systems, become less reliable when they are not refreshed, they including BitLocker, TrueCrypt, and FileVault, and we are not immediately erased, and their contents persist expect many similar products are also vulnerable. sufficiently for malicious (or forensic) acquisition of us- able full-system memory images. We show that this phe- While our principal focus is disk encryption, any sen- nomenon limits the ability of an operating system to pro- sitive data present in memory when an attacker gains tect cryptographic key material from an attacker with physical access to the system could be subject to attack. physical access. We use cold reboots to mount successful Many other security systems are probably vulnerable.