2005
DOI: 10.17487/rfc4106
|View full text |Cite
|
Sign up to set email alerts
|

The Use of Galois/Counter Mode (GCM) in IPsec Encapsulating Security Payload (ESP)

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
52
0

Year Published

2013
2013
2023
2023

Publication Types

Select...
6
1

Relationship

0
7

Authors

Journals

citations
Cited by 65 publications
(52 citation statements)
references
References 7 publications
0
52
0
Order By: Relevance
“…This makes it vulnerable to an IV replacement attack. AES-GCM for IPsec is described in [49]. It involves an 8 byte IV which is transmitted for every packet.…”
Section: Defeating Asasmentioning
confidence: 99%
See 1 more Smart Citation
“…This makes it vulnerable to an IV replacement attack. AES-GCM for IPsec is described in [49]. It involves an 8 byte IV which is transmitted for every packet.…”
Section: Defeating Asasmentioning
confidence: 99%
“…It involves an 8 byte IV which is transmitted for every packet. According to [49], the only requirement is that the IV be unique, though using a counter is mentioned as the most natural way to achieve this property. This flexibility means that an implementation of AES-GCM in IPsec can be RFC-compliant but still vulnerable to an IV replacement attack.…”
Section: Defeating Asasmentioning
confidence: 99%
“…It relies on non-repeating IV (or nonce), e.g. CCM [16], EAX [4], GCM [36], CHM [17], CWC [22], Sarkar's generic construction [35] and dedicated Stream Ciphers like Grain [15], Helix [10], Zuc [2] etc. All these constructions combine counter type encryption and a Mac.…”
Section: Examples Of Authenticated Encryptionsmentioning
confidence: 99%
“…That characterization now applies to AES GCM [RFC4106], which provides both encryption and integrity protection in a single cryptographic When IPsec is used, the receipt of an IKEv1 Phase 2 delete message or an IKEv2 INFORMATIONAL exchange that deletes the SA SHOULD NOT be interpreted as a reason for tearing down the block storage protocol connection (e.g., TCP-based). If additional traffic is sent, a new SA will be created to protect that traffic.…”
Section: Esp Requirementsmentioning
confidence: 99%
“…If both IPsec v2 and v3 are supported by both endpoints of a block storage protocol connection, the use of IPsec v3 is RECOMMENDED. Of particular interest are the security considerations concerning the use of AES GCM [RFC4106] and AES GMAC [RFC4543]; both modes are vulnerable to catastrophic forgery attacks if a nonce is ever repeated with a given key.…”
Section: Esp Requirementsmentioning
confidence: 99%