User's Manual
Table Of Contents
- Table of Contents
- List of Tables
- List of Figures
- Figure1.1 Typical SEL3022 and SEL5810 Virtual Serial Software Application 1.2
- Figure1.2 Encrypted Packet Stream 1.4
- Figure1.3 Typical Connections for the SEL3022 1.6
- Figure1.4 Typical Alarm Output Installation 1.8
- Figure2.1 SEL3022 Dimension Drawing 2.2
- Figure2.2 Windows Run Command 2.3
- Figure2.3 Product Unregistered Prompt 2.4
- Figure2.4 Select a Device Type to Create 2.7
- Figure2.5 Specify New Device Location 2.8
- Figure2.6 Opening Device 2.8
- Figure2.7 Identification Screen 2.9
- Figure2.8 Status: Device 2.10
- Figure2.9 Settings: Wireless 2.10
- Figure2.10 Settings: WEP Keys 2.11
- Figure2.11 Settings: User 2.11
- Figure2.12 Settings: Operator 2.12
- Figure2.13 Settings: Security Officer 2.12
- Figure2.14 Confirm Send Prompt 2.13
- Figure2.15 Send Operation Message 2.13
- Figure2.16 Select Items to Print 2.14
- Figure2.17 Print Window 2.14
- Figure3.1 Remotely Located Recloser Control 3.2
- Figure3.2 Job Done Example SEL-5809 Top Level View 3.3
- Figure3.3 Select a Wireless Session for DNP3 Job Done Example 3.4
- Figure3.4 Settings: DCE Port 3.4
- Figure3.5 Status: Virtual Serial Port With Connection Status Red 3.5
- Figure3.6 Communication Parameters Window in acSELerator 3.6
- Figure3.7 Status: Virtual Serial Port With Connection Status Green 3.6
- Figure3.8 Reading Settings Via the SEL3022 3.7
- Figure3.9 Monitoring SEL651R Meter Data Via the SEL3022 3.8
- Figure3.10 Status: Virtual Serial Port Connection Status Red 3.9
- Figure3.11 Specify Device to Export to SEL5810 Virtual Serial Software 3.10
- Figure3.12 Export Encrypted User Configuration File 3.10
- Figure3.13 Store Encrypted File 3.11
- Figure3.14 Password Prompt in SEL5810 Virtual Serial Software 3.12
- Figure3.15 Communication Parameters Window in acSELerator 3.13
- Figure3.16 Reading SER Report Via acSELerator 3.14
- FigureB.1 PC to SEL3022 Connection B.2
- FigureB.2 SEL3022 and SEL-5809 Connection Parameters B.2
- FigureB.3 SEL5809 Settings Software Connection Method B.3
- FigureB.4 SEL-5809 Opening Connection B.3
- FigureB.5 Status: Device Window B.4
- FigureB.6 Confirmation Prompt B.4
- FigureB.7 Send Operation Prompt B.4
- FigureB.8 Configuring Serial Port Settings in the Terminal Software B.5
- FigureB.9 Send File Prompt B.6
- FigureB.10 Sending Confirmation Window B.6
- FigureB.11 Terminal Invalid Firmware Error Message B.7
- FigureB.12 Terminal Valid Firmware Message B.7
- FigureC.1 Two Independent Layers of Cryptographic Security Protect the SEL3022 Wireless Operato...
- FigureC.2 Operation of the HMAC SHA-1 Keyed Hash Authentication Function C.9
- FigureC.3 Operation of the AES Encryption Function C.10
- FigureC.4 SEL3022 Security Application Overview C.11
- FigureC.5 Wireless Interface Session Authentication Dialog C.15
- Preface
- Introduction & Specifications
- Installation
- Job Done Example
- Settings and Commands
- Testing and Troubleshooting
- Firmware and Manual Versions
- Firmware Upgrade Instructions
- Wireless Operator Interface Security
- Introduction
- Wireless Interface Security Overview
- IEEE 802.11 WEP Security
- The SEL Security Application
- Certificates
- Glossary
SEL-3022 Transceiver Instruction Manual Date Code 20050615
Wireless Operator Interface Security
IEEE 802.11 WEP Security
C.6
Cryptographic Manual—Do Not Copy
WEP Security Flaws Explanation
WEP is based on a two-part encryption algorithm called RC-4. The first stage of the
encryption process, known as the Key Scheduling Algorithm (KSA), takes a string of
key bits as input and forms an output initialization string. The second stage, known as
the Pseudo-Random Generation Algorithm (PRGA), produces a pseudo-random
bitstream of arbitrary length. The value of this string of bits depends on the initializing
permutation the KSA produces. Note that a given KSA input will always produce the
same PRGA output. The designers of the IEEE 802.11 standard wanted the process of
decrypting a single packet to be independent of all previous and future packets.
Because of this requirement, the output of the PRGA function has to be reset at the
beginning of every packet. If this were done without also changing the input to the
KSA function, the encryption stream would be identical for every packet and the
resulting encryption process would be trivially broken. Because of this, the input to the
KSA function is a concatenation of a secret key (104 bits in the case of the SEL-3022
wireless operator interface) with a 24-bit Initialization Vector (IV). By changing the IV
on every packet, the WEP encryption process ensures that the probability of any two,
randomly chosen packets being encrypted with the same PRGA output (known as an
“IV collision”) is sufficiently low.
For each data packet, the concatenation of the key and IV serves as the input to the RC-
4 algorithm, which produces a string of pseudo-random encryption bits (with a length
equal to the length of the original data packet). To perform the encryption operation,
the encryption bit string is added modulo 2 (XOR) to the original contents of the
packet. The IV used during the encryption process is then concatenated with the
resulting ciphertext to form the final message. A major contributor to the relative
weaknesses of the WEP encryption process is the fact that the IV is appended to the
ciphertext and transmitted unencrypted. The following text explains the details of these
weaknesses.
In an August 2001 presentation at the Eighth Annual Workshop on Selected Areas in
Cryptography of an article titled “Weaknesses in the Key Scheduling Algorithm of
RC4,” authors Fluhrer, Mantin, and Shamir published formal proofs of some potential
weaknesses in the RC-4 algorithm. In a later paper, published in the AT&T Labs
Technical Report TD-4ZCPZZ of August 2001 titled “Using the Fluhrer, Mantin, and
Shamir Attack to Break WEP,” authors Stubblefield, Ioannidis, and Rubin
demonstrated that the WEP algorithm was designed in such a way as to contain the
worst of the weaknesses that Fluhrer, Mantin, and Shamir’s paper outlined.
Furthermore, Stubblefield, Ioannidis, and Rubin demonstrated that a passive attack
could be used to successfully determine a 104-bit secret key in just a few hours on a
moderately loaded wireless LAN. Based on these results, Stubblefield, Ioannidis, and
Rubin urged network designers to assume that the IEEE 802.11 link layer offers very
little security and to employ additional security measures in addition to WEP. The
SEL-3022 design incorporates these additional security measures in the form of
cryptographically sound 128-bit AES encryption and HMAC SHA-1 authentication
(see The SEL Security Application on page C.9 for further explanation).
Preliminary Copy