A more secure method than using preshared keys is using CA signed X.509 certificates. These certificates must be digitally signed by a Certificate Authority (CA) supported by both the Windows 2000 system and the SunScreen system. Currently, Microsoft supports certificates signed by its own Windows 2000 Server CA as well as a number of public CA authorities (see the Trusted CA Authorities list on Windows 2000, all of these vendors qualify as Root CAs). You can also use non-public CA's like Netscape Certificate server, if you import the CA's root Ccertificate into the Windows 2000 Trusted Root Certificate store. Self signed certificates are not supported by Microsoft
Each side must be able to follow each signed certificate up its certificate chain to the Root CA. They accomplish verification by having the Root CA's certificate in a special certificate store (the IKE root CA certificates GROUP certificate object on the Screen and the Trusted Root Certificate store on the Windows 2000 system). Because both systems must use certificates signed by a CA common to both systems, you cannot use self signed DH certificates to interoperate with Windows 2000.
Certificates are necessary in order to have a Windows 2000 system act as a remote Administration Station managing a Screen.
The following sections describe how you would set up the Screen and the Windows 2000 system to interoperate.
Generate a Certificate Signing Request
From the Common Objects panel, select Generate IKE Certificate
When the IKE Certificate dialog appears, click the Generate CA Request button; see Figure 9-4
Fill in the required fields.
Type in a Distinguished Name and make sure that the Encryption Type and Key Size match the related parameters used by the Windows 2000 system for its own certificate.
Click the Generate button.
SunScreen generates a Certificate Signing Request (CSR) and also creates and stores a private key. The following figure shows the CSR.
You can copy the text or save into a file for use in your signing request.
Present the CSR to the CA.
Have the certificate signed and acquire the new certificate.
Import the CA signed certificate into the Screen
From the common Objects panel, choose Import IKE Certificate. The Import IKE Certificate screen appears
Specify a name and description.
Choose an import method
Click the appropriate button and then either specify a file to import or paste the signed certificate into the text area.
Click the Install Certificate button.
Add the IKE Root CA Certificate to the Screen.
You accomplish this task by adding the Root CA certificate to the IKE root CA Certificates GROUP object.
Acquire the Root CA certificate and import it into the Screen's certificate store.
After you finish the import, in the Common Objects panel, search for the IKE root CA certificates object.
When you find the object, select it and click the edit button. The Certificates object dialog appears. See Figure 9-6.
Select the Root CA certificate you want and add it to the Include List.
Click OK to finish the task.
Edit the Root CA certificate object.
A requirement of Windows 2000 for IKE interoperability is that you must specify the Root CA certificate by its ISSUER Distinguished Name.
The following section describes in general terms how you would set up a Windows 2000 system to interoperate with a Screen. This section only provides general steps. For specific instructions on setting up the Windows 2000 system see the Windows 2000 online help and also refer to these White Papers which are available on the Microsoft web site.
How to Configure IPSec Tunneling in Windows 2000
How to Install a Certificate for Use with IP Security
Step-by-Step Guide to Internet Protocol Security IPSec
Obtain a private key and certificate signed by the same CA used by the Screen with whom you wish to communicate.
Make sure that the CA Root certificate is in the Trusted Root CA Certificate store.
Create an IPSec security policy.
Create an IKE rule that allows communication between the Screen and the Windows 2000 system.
Be aware of the following interoperability requirements:
The Authentication Method should be Certificate Authority and the Root CA list must contain the common Root CA certificate.
The filter action should be Negotiate Security and it should only specify one security method.
To set up a packet filtering rule on the Screen use the same procedure as would be used with any IKE encryption rule. However, you must be aware of the following interoperability requirements:
The ESP and AH values must match those specified in the Filter Action on the Windows 2000 system.
The encryption Algorithm must be either DES or 3DES.
The Authentication Method must be RSA-SIGNATURES
The Oakley group must be consistent with the DH values used by the Windows 2000 system during IKE negotiation. You are restricted to those values supported by the Windows 2000 system. For example, Windows 2000 does not support Oakley group 5. The following table shows the default Oakley Group values used by Windows 2000. If someone on the Windows 2000 side changes these default values (unlikely based on how far down they are buried in the GUI) , you would have to use a value that matches their new value.
Encryption Algorithm |
Hash Algorithm |
Oakley Group Value |
---|---|---|
3DES |
SHA1 |
2 |
3DES |
MD5 |
2 |
DES |
SHA1 |
1 |
DES |
MD5 |
1 |
If the rule permits traffic from the Windows 2000 system to the Screen, the Source Certificate must be the Root CA certificate and the Destination Screen is the Screen object.
If the rule permits traffic from the Screen to the Windows 2000 system, the Destination Certificate must be the Root CA certificate and the Source Screen is the Screen object.