AES-Based Authenticated Encryption Modes in Parallel High-Performance Software
Total Page:16
File Type:pdf, Size:1020Kb
Load more
Recommended publications
-
SILC-A SECURED INTERNET CHAT PROTOCOL Anindita Sinha1, Saugata Sinha2 Asst
ISSN (Print) : 2320 – 3765 ISSN (Online): 2278 – 8875 International Journal of Advanced Research in Electrical, Electronics and Instrumentation Engineering Vol. 2, Issue 5, May 2013 SILC-A SECURED INTERNET CHAT PROTOCOL Anindita Sinha1, Saugata Sinha2 Asst. Prof, Dept. of ECE, Siliguri Institute of Technology, Sukna, Siliguri, West Bengal, India 1 Network Engineer, Network Dept, Ericsson Global India Ltd, India2 Abstract:-. The Secure Internet Live Conferencing (SILC) protocol, a new generation chat protocol provides full featured conferencing services, compared to any other chat protocol. Its main interesting point is security which has been described all through the paper. We have studied how encryption and authentication of the messages in the network achieves security. The security has been the primary goal of the SILC protocol and the protocol has been designed from the day one security in mind. In this paper we have studied about different keys which have been used to achieve security in the SILC protocol. The main function of SILC is to achieve SECURITY which is most important in any chat protocol. We also have studied different command for communication in chat protocols. Keywords: SILC protocol, IM, MIME, security I.INTRODUCTION SILC stands for “SECURE INTERNET LIVE CONFERENCING”. SILC is a secure communication platform, looks similar to IRC, first protocol & quickly gained the status of being the most popular chat on the net. The security is important feature in applications & protocols in contemporary network environment. It is not anymore enough to just provide services; they need to be secure services. The SILC protocol is a new generation chat protocol which provides full featured conferencing services; additionally it provides security by encrypting & authenticating the messages in the network. -
Secure Internet Live Conferencing
Einführung SILC vs. IRC vs. XMPP Architektur Nachrichten Protokoll Secure Internet Live Conferencing Frank Benkstein <[email protected]> 26.10.2007, 19:12:23h Frank Benkstein <[email protected]> Secure Internet Live Conferencing Einführung SILC vs. IRC vs. XMPP Architektur Nachrichten Protokoll Übersicht I Einführung I SILC vs. IRC vs. XMPP I Architektur I Protokoll Frank Benkstein <[email protected]> Secure Internet Live Conferencing Einführung SILC vs. IRC vs. XMPP Architektur Nachrichten Protokoll Geschichte Geschichte 1996 Idee und Entwurf durch Pekka Riikonen 1997 erster Code 1998 Rewrite in C++ 1999 Rewrite in C 2000 erste Veröffentlichung der Quelltexte Einreichung der Spezifikationen bei der IETF 2003 SILC-Client 1.0 Frank Benkstein <[email protected]> Secure Internet Live Conferencing Einführung SILC vs. IRC vs. XMPP Architektur Nachrichten Protokoll Design Ziele I Echtzeit-Text-Kommunikation I Viele-Zu-Viele (ähnlich IRC) I Eins-Zu-Eins (Instant Messaging) I Multimedia-Fähigkeit I Datei-Transfer I Sicherheit I Modularität Frank Benkstein <[email protected]> Secure Internet Live Conferencing Einführung SILC vs. IRC vs. XMPP Architektur Nachrichten Protokoll Protokoll-Eigenschaften Protokoll-Eigenschaften I Verschlüsselung I gesamte Kommunikation verschüsselt und authentifiziert I unverschlüsselte Kommunikation unmöglich* I Signatur von Nachrichten I Unicode (UTF-8) statt ASCII I Nicknames I Channel-Namen I Nachrichten I Peer-to-Peer für Dateitransfer I alles andere über Server Frank Benkstein <[email protected]> Secure Internet Live Conferencing Einführung SILC vs. IRC vs. XMPP Architektur Nachrichten Protokoll Protokoll-Eigenschaften Clients I eindeutige Client-ID I Nicknamen I nicht eindeutig* I UTF-8 I bis zu 128 Bytes (!) lang I gleicher Public-Key möglich Frank Benkstein <[email protected]> Secure Internet Live Conferencing Einführung SILC vs. -
Security Policy: Informacast Java Crypto Library
FIPS 140-2 Non-Proprietary Security Policy: InformaCast Java Crypto Library FIPS 140-2 Non-Proprietary Security Policy InformaCast Java Crypto Library Software Version 3.0 Document Version 1.2 June 26, 2017 Prepared For: Prepared By: Singlewire Software SafeLogic Inc. 1002 Deming Way 530 Lytton Ave, Suite 200 Madison, WI 53717 Palo Alto, CA 94301 www.singlewire.com www.safelogic.com Document Version 1.2 © Singlewire Software Page 1 of 35 FIPS 140-2 Non-Proprietary Security Policy: InformaCast Java Crypto Library Abstract This document provides a non-proprietary FIPS 140-2 Security Policy for InformaCast Java Crypto Library. Document Version 1.2 © Singlewire Software Page 2 of 35 FIPS 140-2 Non-Proprietary Security Policy: InformaCast Java Crypto Library Table of Contents 1 Introduction .................................................................................................................................................. 5 1.1 About FIPS 140 ............................................................................................................................................. 5 1.2 About this Document.................................................................................................................................... 5 1.3 External Resources ....................................................................................................................................... 5 1.4 Notices ......................................................................................................................................................... -
How to Enhance the Security of the 3GPP Confidentiality and Integrity
How to Enhance the Security of the 3GPP Confidentiality and Integrity Algorithms Tetsu Iwata and Kaoru Kurosawa Dept. of Computer and Information Sciences, Ibaraki University 4–12–1 Nakanarusawa, Hitachi, Ibaraki 316-8511, Japan {iwata, kurosawa}@cis.ibaraki.ac.jp Abstract. We consider the 3GPP confidentiality and integrity schemes that were adopted by Universal Mobile Telecommunication System, an emerging standard for third generation wireless communications. The schemes, known as f8 and f9, are based on the block cipher KASUMI. Although previous works claim security proofs for f8 and f9, where f9 is a generalized version of f9, it was shown that these proofs are incorrect; it is impossible to prove f8 and f9 secure under the standard PRP assumption on the underlying block cipher. Following the results, it was shown that it is possible to prove f8 and f9 secure if we make the assumption that the underlying block cipher is a secure PRP-RKA against a certain class of related-key attacks; here f8 is a generalized version of f8. Needless to say, the assumptions here are stronger than the standard PRP assumptions, and it is natural to seek a practical way to modify f8 and f9 to establish security proofs under the standard PRP assumption. In this paper, we propose f8+ and f9+, slightly mod- ified versions of f8 and f9, but they allow proofs of security under the standard PRP assumption. Our results are practical in the sense that we insist on the minimal modifications; f8+ is obtained from f8 by setting the key modifier to all-zero, and f9+ is obtained from f9 by setting the key modifier to all-zero, and using the encryptions of two constants in the CBC MAC computation. -
CLOUD & Cyber-Security Driven Inflection Point
CLOUD & Cyber-Security Driven Inflection Point November 14, 2017 Safe Harbor Guidelines & Legal Notes The information presented today contains forward-looking statements as defined in the Private Securities Litigation Reform Act of 1995. Such statements may include, but are not limited to, anticipated future financial and operating results and Silicom’s outlook and prospects. Those statements are based on management’s current beliefs, expectations and assumptions, which may be affected by subsequent business, political, environmental, regulatory, economic and other conditions, and necessarily involve known and unknown risks and uncertainties, which include, but are not limited to, Silicom’s increasing dependence for substantial revenue growth on a limited number of customers in the evolving cloud-based market, the speed and extent to which cloud-based and cloud-focused solutions are adopted by the market, likelihood that Silicom will rely increasingly on customers which provide cloud-based and cloud-focused solutions in this evolving market, resulting in an increasing dependence on a smaller number of larger customers, difficulty in commercializing and marketing of Silicom’s products and services, maintaining and protecting brand recognition, protection of intellectual property, competition and other factors which Silicom discusses in its public filings. Therefore, there can be no assurance that actual future results will not differ significantly from anticipated results. Therefore, you are cautioned not to rely on these forward-looking statements. Silicom does not undertake to update any forward-looking statements as a result of new information or future events or developments except as may be required by law. Financial information as of 2010, as presented herein, may be considered "non- GAAP financial measures" under Regulation G and related reporting requirements promulgated by the Securities and Exchange Commission ("SEC") as they apply to Silicom. -
Optimizing Authenticated Encryption Algorithms
Masaryk University Faculty of Informatics Optimizing authenticated encryption algorithms Master’s Thesis Ondrej Mosnáček Brno, Fall 2017 Masaryk University Faculty of Informatics Optimizing authenticated encryption algorithms Master’s Thesis Ondrej Mosnáček Brno, Fall 2017 This is where a copy of the official signed thesis assignment and a copy ofthe Statement of an Author is located in the printed version of the document. Declaration Hereby I declare that this paper is my original authorial work, which I have worked out on my own. All sources, references, and literature used or excerpted during elaboration of this work are properly cited and listed in complete reference to the due source. Ondrej Mosnáček Advisor: Ing. Milan Brož i Acknowledgement I would like to thank my advisor, Milan Brož, for his guidance, pa- tience, and helpful feedback and advice. Also, I would like to thank my girlfriend Ludmila, my family, and my friends for their support and kind words of encouragement. If I had more time, I would have written a shorter letter. — Blaise Pascal iii Abstract In this thesis, we look at authenticated encryption with associated data (AEAD), which is a cryptographic scheme that provides both confidentiality and integrity of messages within a single operation. We look at various existing and proposed AEAD algorithms and compare them both in terms of security and performance. We take a closer look at three selected candidate families of algorithms from the CAESAR competition. Then we discuss common facilities provided by the two most com- mon CPU architectures – x86 and ARM – that can be used to implement cryptographic algorithms efficiently. -
On the Security of CTR + CBC-MAC NIST Modes of Operation – Additional CCM Documentation
On the Security of CTR + CBC-MAC NIST Modes of Operation { Additional CCM Documentation Jakob Jonsson? jakob [email protected] Abstract. We analyze the security of the CTR + CBC-MAC (CCM) encryption mode. This mode, proposed by Doug Whiting, Russ Housley, and Niels Ferguson, combines the CTR (“counter”) encryption mode with CBC-MAC message authentication and is based on a block cipher such as AES. We present concrete lower bounds for the security of CCM in terms of the security of the underlying block cipher. The conclusion is that CCM provides a level of privacy and authenticity that is in line with other proposed modes such as OCB. Keywords: AES, authenticated encryption, modes of operation. Note: A slightly different version of this paper will appear in the Proceedings from Selected Areas of Cryptography (SAC) 2002. 1 Introduction Background. Block ciphers are popular building blocks in cryptographic algo rithms intended to provide information services such as privacy and authenticity. Such block-cipher based algorithms are referred to as modes of operation. Exam ples of encryption modes of operation are Cipher Block Chaining Mode (CBC) [23], Electronic Codebook Mode (ECB) [23], and Counter Mode (CTR) [9]. Since each of these modes provides privacy only and not authenticity, most applica tions require that the mode be combined with an authentication mechanism, typically a MAC algorithm [21] based on a hash function such as SHA-1 [24]. For example, a popular cipher suite in SSL/TLS [8] combines CBC mode based on Triple-DES [22] with the MAC algorithm HMAC [26] based on SHA-1. -
Instant Messaging Service Reference
IceWarp Unified Communications Instant Messaging Service Reference Version 10.4 Printed on 16 April, 2012 Contents Instant Messaging 1 Reference ....................................................................................................................................................................... 2 General .............................................................................................................................................................. 2 Services .............................................................................................................................................................. 2 Trusted Hosts ..................................................................................................................................................... 8 Archive/History .................................................................................................................................................. 9 File Transfers between Clients ..................................................................................................................................... 10 Monitoring via IM ......................................................................................................................................................... 12 Monitor Services and Get Your GW Events, Tasks and Notes via IM .................................................. 12 Usage .................................................................................................................................................. -
AES-CCM Brief
FEATURES AES-CCM Encrypts and decrypts using the AES Rijndael Block Cipher Algorithm AES-CCM Authenticated Encrypt/Decrypt Engine Implemented according to the National Institute of Standards and Technology (NIST) Special The AES-CCM encryption IP core implements hardware Rijndael encoding and decoding in Publication 800-38D compliance with the NIST Advanced Encryption Standard. It processes 128-bit blocks, and is NIST Certified programmable for 128-, 192-, and 256-bit key lengths. Employs Counter with CBC- MAC CCM stands for Counter with CBC- MAC mode. CCM is a generic authenticate-and-encrypt mode (CCM) block cipher mode. CBC-MAC is utilized to generate an authentication string while CTR mode Processes 128-bit data in 32-bit is used to encrypt. blocks Two architectural versions are available to suit system requirements. The Standard version Employs user-programmable key size of 128, 192, or 256 bits (AES-CCM-S) is more compact, using a 32-bit datapath and requiring 44/52/60 clock cycles Two architectural versions: for each data block (128/192/256-bit cipher key, respectively). The Fast version (AES-CCM-F) o achieves higher throughput, using a 128-bit datapath and requiring 11/13/15 clock cycles for Standard is more compact: 32-bit data path size each data block. Processes each 128-bit data block The AES-CCM cores are fully synchronous designs, have been evaluated in a variety of in 44/52/60 clock cycles for 128/192/256-bit cipher keys, technologies, and are available optimized for ASICs or FPGAs. respectively Applications o Fast yields higher transmission rates: The AES-CCM can be utilized for a variety of encryption applications including protected 128-bit data path network routers, electronic financial transactions, secure wireless communications, secure Processes each 128-bit block in video surveillance systems, and encrypted data storage. -
Multi-IP-Based Soc Design Including CCM Security Mode of Operation
Master Thesis ICT/ECS-2006-71 Multi-IP-Based SoC Design Including CCM Security Mode of Operation By Solmaz Ghaznavi A thesis presented to the University of Waterloo and KTH University in the fulfillment of the thesis requirement for the degree of Master of Science in System on-Chip Design Waterloo, Ontario, Canada, 2006 © Solmaz Ghaznavi, 2006 Supervisor: Professor Cathy Gebotys Examiner: Professor Axel Jantsch I hereby declare that I am the sole author of this thesis. I authorize the University of Waterloo and KTH University to lend this thesis to other institutions or individuals for the purpose of scholarly research. I further authorize the University of Waterloo and KTH University to reproduce this thesis by photocopying or by other means, in total or in print, at the request of other institutions is individuals for the purpose of scholarly research. ii Abstract Embedding security in many mobile electronic devices is of great importance. With the emergence of powerful self-contained FPGAs which include microprocessors, memory etc. for SoC designs, it has shifted focus to these programmable platforms. A co-design approach can be used to optimize speed, area and power consumption by partitioning function onto the on-chip microprocessor and programmable logic blocks. FPGAs typically provide higher efficiency compared to software. On the other hand they offer more flexibility and much lower design and debug costs compared to specifically-built hardware. This thesis mainly implements CCM security mode of operation on a FPGA platform by using the AES encryption algorithm, it then builds a complete SoC that is based on multi IP cores including CCM. -
The Helion Basic Guide to AES Encryption in Hardware
The Helion basic guide to AES encryption in hardware What is AES? During September 1997, the National Institute of Standards and Technology (NIST), the main standards body in the US, issued an open request for submissions for a new Advanced Encryption Standard (AES). The idea was that AES would be a new encryption standard to replace the existing Data Encryption Standard (DES), which had been in place for more than two decades. In August 1998, a number of potential candidates were selected from the submissions, and then in August 1999, these were further selected to become a shortlist of five finalists. In October 2000, one of these five algorithms, “Rijndael”, was chosen as the new AES. This decision was then fully ratified by the NIST in November 2001, at which point AES became the encryption algorithm of choice for all new commercial developments requiring a high degree of data security. What is AES like from the outside? Rijndael is what is known as a “Block Cipher” with multiple options for its block and key size. The NIST approved AES is a subset of these options; the block size is fixed at 128-bits, but the key may be either 128, 192 or 256-bits in length. As their name suggests, Block Ciphers only process data in blocks. In the case of AES this means that it is capable of encrypting plaintext data in blocks of 128-bits using any of the specified key sizes; in broad terms, the bigger the keysize, the higher the security. It is generally accepted that 128-bit keys will provide a sufficient level of security for most commercial applications, though longer keys seem to be specified more and more for the latest applications. -
An Analysis of Instant Messaging and E- Mail Access Protocol Behavior in Wireless Environment
An Analysis of Instant Messaging and E- mail Access Protocol Behavior in Wireless Environment IIP Mixture Project Simone Leggio Tuomas Kulve Oriana Riva Jarno Saarto Markku Kojo March 26, 2004 University of Helsinki - Department of Computer Science i TABLE OF CONTENTS 1 Introduction ..................................................................................................................................... 1 PART I: BACKGROUND AND PROTOCOL ANALYSIS ............................................................. 1 2 Instant Messaging............................................................................................................................ 1 3 ICQ.................................................................................................................................................. 3 3.1 Overview ................................................................................................................................. 3 3.2 Protocol Operation .................................................................................................................. 4 3.2.1 Client to Server................................................................................................................4 3.2.2 Client to Client ................................................................................................................5 3.2.3 Normal Operation............................................................................................................ 5 3.2.4 Abnormal Operation.......................................................................................................