How Not to Combine RC4 States

Subhadeep Banik, Sonu Jha

Research output: Chapter in Book/Report/Conference proceedingArticle in proceedingsResearchpeer-review

Abstract

Over the past few years, an attractive design paradigm has emerged, that aims to produce new stream cipher designs, by combining one or more independently produced RC4 states. The ciphers so produced turn out to be faster than RC4 on any software platform, mainly because the average number of internal operations used in the cipher per byte of keystream produced is usually lesser than RC4. One of the main efforts of the designers is to ensure that the existing weaknesses of RC4 are not carried over to the new ciphers so designed. In this work we will look at two such ciphers RC4B (proposed by Zhang et. al.) and Quad-RC4/m-RC4 (proposed by Maitra et. al.). We will propose distinguishing attacks against all these ciphers, and look at certain design flaws that made these ciphers vulnerable.
Original languageEnglish
Title of host publicationProceedings of the 5th International Conference on Security, Privacy, and Applied Cryptography Engineering (SPACE 2015)
EditorsRajat Subhra Chakraborty, Peter Schwabe, Jon Solworth
PublisherSpringer
Publication date2015
Pages95-112
ISBN (Print)978-3-319-24125-8
ISBN (Electronic)978-3-319-24126-5
DOIs
Publication statusPublished - 2015
Event5th International Conference on Security, Privacy, and Applied Cryptography Engineering (SPACE 2015) - Jaipur, Rajasthan, India
Duration: 3 Oct 20157 Oct 2015
Conference number: 5
http://cse.iitkgp.ac.in/conf/SPACE2015/

Conference

Conference5th International Conference on Security, Privacy, and Applied Cryptography Engineering (SPACE 2015)
Number5
CountryIndia
CityJaipur, Rajasthan
Period03/10/201507/10/2015
Internet address
SeriesLecture Notes in Computer Science
Volume9354
ISSN0302-9743

Keywords

  • RC4
  • RC4B
  • Quad-RC4
  • m-RC4
  • Distinguishing Attacks
  • Stream Cipher

Fingerprint

Dive into the research topics of 'How Not to Combine RC4 States'. Together they form a unique fingerprint.

Cite this