A note on the fragility of the "Michael" message integrity code

Avishai Wool*

*Corresponding author for this work

Research output: Contribution to journalArticlepeer-review

17 Scopus citations

Abstract

The IEEE 802.11 wireless local area network standard did not incorporate a cryptographic message integrity code into its wired equivalent privacy (WEP) protocol, and relied upon CRC-32 for message integrity. This was shown to be completely insecure since WEP uses a stream cipher (RC4) for encryption. The latest IEEE 802.11i draft addresses this, and other, weaknesses discovered in WEP. IEEE 802.11i suggests three new modes of operation: two based on the Advanced Encryption Standard cipher and one [temporal key integrity protocol (TKIP)] still based on RC4. The TKIP mode is intended for use on legacy hardware, which is computationally weak. TKIP uses a new, keyed, 64-b, message integrity code called Michael. In this letter, we highlight a weakness in Michael and suggest a simple fix.

Original languageEnglish
Pages (from-to)1459-1462
Number of pages4
JournalIEEE Transactions on Wireless Communications
Volume3
Issue number5
DOIs
StatePublished - Sep 2004

Keywords

  • Message authentication code
  • Wireless security

Fingerprint

Dive into the research topics of 'A note on the fragility of the "Michael" message integrity code'. Together they form a unique fingerprint.

Cite this