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

IKE Authentication: Pre-shared Key

Page 35 highlights

Diffie-Hellman doesn't really work this way, but in principle, this is how you would accomplish something similar. The point of the example is only to take a little mystery out of the process. Again, the different Diffie-Hellman groups, or DH groups, refer to different "strengths" of security. You can think of a bigger, more secure lock as being the same as a larger DH Group number. Well, at this point, IKE has selected the format of the SA and has secret keying material available to it. Now the only thing left to do is authenticate the computer system it is speaking to. Unfortunately, this can be pretty complex. There are three different authentication algorithms to verify that the computer system you are talking to is really the one you think you are talking to. They are Pre-Shared Key, Kerberos, and Certificates. IKE Authentication: Pre-shared Key The simplest way IKE can mutually authenticate two computer systems is through a shared secret passphrase, or as IKE refers to it as a Pre-shared Key. This value must be the same on both computer systems. The Authentication exchange uses the shared DH secret and hashes of the pass-phrase to determine if both computer systems know the pass-phrase without actually transmitting it over the network. To configure IKE Pre-Shared Key Authentication, you'll need to enter the exact same passphrase on both computer systems. Figure 27 shows a screen shot from Microsoft's IPsec Wizard. Figure 27 - Windows Authentication Method This next screen shot is from HP Jetdirect. Notice the pass phrases are the same and have to be the same for Pre-Shared Key authentication to work. 35

  • 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

35
Diffie-Hellman doesn’t really work this way, but in principle, this is how you would accomplish
something similar.
The point of the example is only to take a little mystery out of the process.
Again,
the different Diffie-Hellman groups, or DH groups, refer to different “strengths” of security.
You can
think of a bigger, more secure lock as being the same as a larger DH Group number.
Well, at this point, IKE has selected the format of the SA and has secret keying material available to
it.
Now the only thing left to do is authenticate the computer system it is speaking to.
Unfortunately,
this can be pretty complex.
There are three different authentication algorithms to verify that the
computer system you are talking to is really the one you think you are talking to.
They are Pre-Shared
Key, Kerberos, and Certificates.
IKE Authentication: Pre-shared Key
The simplest way IKE can mutually authenticate two computer systems is through a shared secret pass-
phrase, or as IKE refers to it as a Pre-shared Key.
This value must be the same on both computer
systems.
The Authentication exchange uses the shared DH secret and hashes of the pass-phrase to
determine if both computer systems know the pass-phrase without actually transmitting it over the
network.
To configure IKE Pre-Shared Key Authentication, you’ll need to enter the exact same passphrase on
both computer systems. Figure 27 shows a screen shot from Microsoft’s IPsec Wizard.
Figure 27 – Windows Authentication Method
This next screen shot is from HP Jetdirect.
Notice the pass phrases are the same and have to be the
same for Pre-Shared Key authentication to work.