Symantec 14541094 User Guide - Page 210

Configuring pcAnywhere to use public-key encryption

Page 210 highlights

210 Securing your computer and sessions Using encryption to protect data This option is not applicable for pcAnywhere encoding. 6 Click OK. Configuring pcAnywhere to use public-key encryption In public-key encryption, pcAnywhere uses a digital certificate to verify the identity of the person who is attempting to connect and send data. It then uses symmetric encryption algorithms to secure the session. Some configuration is required to ensure that both the host and remote users have access to the appropriate key pairs. To use public-key encryption in pcAnywhere, the host and remote users must do the following: ■ Provide each other with copies of their digital certificates. ■ Set up a certificate store that contains the certificates of those users who will connect to their computers. ■ Locate certificates and private keys when the host computer is running as a service. ■ Configure a connection item to use public-key encryption. When you select public-key encryption, pcAnywhere only allows connections with computers that are also using public-key encryption. Connections with computers that are set to any other encryption level are denied. Creating a certificate file to send to another user Certificates are data documents that contain identification information that includes the user's name, public key, issuing authority, and data signature. Symantec pcAnywhere requires that you use Microsoft-compatible certificates. You can obtain these from a commercial certificate authority (for example, VeriSign or Entrust) or from an internal certificate server. You can create a certificate file by exporting your certificate in Microsoft Internet Explorer. Use any export format that does not include the private key (for example, PKCS#7 with a .p7b file extension). Send the file to the computer to which you want to connect using a secure method. Alternatively, the other user can download your certificate from the certificate authority. Follow the certificate authority's instructions for finding and downloading another user's certificate.

  • 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
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313

This option is not applicable for pcAnywhere encoding.
6
Click
OK
.
Configuring pcAnywhere to use public-key encryption
In public-key encryption, pcAnywhere uses a digital certificate to verify the identity
of the person who is attempting to connect and send data. It then uses symmetric
encryption algorithms to secure the session.
Some configuration is required to ensure that both the host and remote users
have access to the appropriate key pairs. To use public-key encryption in
pcAnywhere, the host and remote users must do the following:
Provide each other with copies of their digital certificates.
Set up a certificate store that contains the certificates of those users who will
connect to their computers.
Locate certificates and private keys when the host computer is running as a
service.
Configure a connection item to use public-key encryption.
When you select public-key encryption, pcAnywhere only allows connections with
computers that are also using public-key encryption. Connections with computers
that are set to any other encryption level are denied.
Creating a certificate file to send to another user
Certificates are data documents that contain identification information that
includes the user's name, public key, issuing authority, and data signature.
Symantec pcAnywhere requires that you use Microsoft-compatible certificates.
You can obtain these from a commercial certificate authority (for example,
VeriSign or Entrust) or from an internal certificate server.
You can create a certificate file by exporting your certificate in Microsoft Internet
Explorer. Use any export format that does not include the private key (for example,
PKCS#7 with a .p7b file extension). Send the file to the computer to which you
want to connect using a secure method.
Alternatively, the other user can download your certificate from the certificate
authority. Follow the certificate authority's instructions for finding and
downloading another user's certificate.
Securing your computer and sessions
Using encryption to protect data
210