HP 635n Practical IPsec Deployment for Printing and Imaging Devices - Page 33

Refer to Publicly Exchanging

Page 33 highlights

Lifetime in bytes: null Transform 7 Confidentiality Algorithm: AES256 Authentication/Integrity Algorithm: SHA-1 Authentication Type: Pre-share Key DH-Group #: 2 Lifetime in sections: 3600 Lifetime in bytes: null Transform 8 Confidentiality Algorithm: AES256 Authentication/Integrity Algorithm: AES-XCBC Authentication Type: Pre-share Key DH-Group #: 2 Lifetime in sections: 3600 Lifetime in bytes: null If the responder doesn't like any of the proposals and their various transforms, it will respond back with an error NO PROPOSAL CHOSEN. Because IKE cannot establish an SA, no IPsec communication will take place in this scenario (like the builders/suppliers unable to establish a contract in our analogy). If the responder does like a proposal, then its response may look something like this: SA Payload Proposal 1 Transform 8 Confidentiality Algorithm: AES256 Authentication/Integrity Algorithm: AES-XCBC Authentication Type: Pre-share Key DH-Group #: 2 Lifetime in sections: 3600 Lifetime in bytes: null IKE can now begin the establishment of the shared secret. This shared secret is done via a DiffieHellman exchange, an exchange named after its inventors. The main question is "How does one publicly exchange information and still be able to have a shared secret known only to the Initiator and Responder?" Well, Diffie-Hellman figured it out. Rather than going into the mathematics behind it, we look at another quick analogy in graphical form. Refer to Figure 26 - Publicly Exchanging a Secret. 33

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193

33
Lifetime in bytes: null
Transform 7
Confidentiality Algorithm: AES256
Authentication/Integrity Algorithm: SHA-1
Authentication Type: Pre-share Key
DH-Group #: 2
Lifetime in sections: 3600
Lifetime in bytes: null
Transform 8
Confidentiality Algorithm: AES256
Authentication/Integrity Algorithm: AES-XCBC
Authentication Type: Pre-share Key
DH-Group #: 2
Lifetime in sections: 3600
Lifetime in bytes: null
If the responder doesn’t like any of the proposals and their various transforms, it will respond back
with an error NO PROPOSAL CHOSEN.
Because IKE cannot establish an SA, no IPsec
communication will take place in this scenario (like the builders/suppliers unable to establish a
contract in our analogy).
If the responder does like a proposal, then its response may look something
like this:
SA Payload
Proposal 1
Transform 8
Confidentiality Algorithm: AES256
Authentication/Integrity Algorithm: AES-XCBC
Authentication Type: Pre-share Key
DH-Group #: 2
Lifetime in sections: 3600
Lifetime in bytes: null
IKE can now begin the establishment of the shared secret.
This shared secret is done via a Diffie-
Hellman exchange, an exchange named after its inventors.
The main question is “How does one
publicly exchange information and still be able to have a shared secret known only to the Initiator
and Responder?”
Well, Diffie-Hellman figured it out.
Rather than going into the mathematics behind
it, we look at another quick analogy in graphical form.
Refer to Figure 26 – Publicly Exchanging a
Secret.