www.geekybob.com

IIS 5: Setting up SSL - Appendix B: Obtaining a Root Certificate

21 September 2001 • by Bob • IIS, SSL, Windows

Obtaining a root certificate is one of the most important steps for servers or clients that will use certificates that you issue. While this step is not necessary on the server where you installed Certificate Services, it is absolutely essential on your other servers or clients because it allows those computers to trust you as a Certificate Authority. Without that trust in place, you will either receive error messages or SSL simply won't work.

This process is broken into two steps:

• Downloading the Root Certificate
• Installing the Root Certificate

Downloading the Root Certificate

1. Browse to your certificate server's address, (e.g. http://<server-name>/certsrv/), and choose to retrieve the CA certificate:

   

2. Click the link to download the CA certificate:

   

3. Choose to save the certificate file to disk:

   

4. Save the file to your desktop:

   

Installing the Root Certificate

Before using any certificates that you issue on a computer, you need to install the Root Certificate. (This includes web servers and clients.)

1. Double-click the file on your desktop:

   

2. Click the "Install Certificate" button:

   

3. Click "Next" to start the Certificate Import Wizard:

   

4. Choose to automatically choose the store:

   

5. Click the "Finish" button:

   

6. Click "Yes" when asked if you want to add the certificate:

   

   NOTE: This step is very important. If you do not see this dialog, something went wrong.
7. Click "OK" when informed that the import was successful.

   

IIS 5: Setting up SSL - Appendix A: Installing Certificate Services

21 September 2001 • by Bob • IIS, SSL, Windows

In this blog post I'll discuss installing Certificate Services for Windows 2000 in order to test SSL in your environment. To install Certificate Services, use the following steps:

1. Run the "Windows Component Wizard" in "Add/Remove Programs", choose "Certificate Services", and click "Next":

   

2. Choose "Stand-alone root CA", then click "Next":

   

3. Enter all requested information, then click "Next":

   

4. Accept the defaults for the data locations and click "Next":

   

5. The wizard will step through installing the services:

   

6. When the wizard has completed, click "Finish" to exit the wizard:

   

IIS 5: Setting up SSL - Part 3: Installing a Certificate

21 September 2001 • by Bob • IIS, SSL

Installing Your Certificate

1. Bring up the properties for a web site:

   

2. Switch to the "Directory Security" tab and click "Server Certificate:"

   

3. Click "Next" to bypass the first page:

   

4. Choose to process the request and click "Next":

   

5. Browse to the location of your certificate and click "Next":

   

6. Review the information to make sure it is correct and click "Next":

   

7. Click "Finish" to close the wizard:

   

8. Notice that you now have all the buttons available for SSL.

   

Verifying Your Certificate

1. Bring up the properties for a web site:

   

2. Switch to the "Directory Security" tab and click "View Certificate":



3. On the "General" tab, if the certificate is good you will see a normal certificate icon. (If not, you will see a warning or error icon.)

   

4. On the "Certification Path" tab you will see your certificate hierarchy:

   

IIS 5: Setting up SSL - Part 2: Obtaining a Certificate

21 September 2001 • by Bob • IIS, SSL

Typically you would submit your certificate request to any one of several Certificate Authorities (CA). There are several that are available, but here are just a few:

• Thawte Digital Certificates
  http://www.thawte.com/
• VeriSign Digital Certificates
  http://www.verisign.com/

The steps to obtain a certificate differ for each CA, and it would be way outside the scope of my limited blogspace to include the steps for every CA on the Internet. So for my blog series I'm going to show how to use Certificate Services on Windows 2000 to obtain a certificate. This process is broken into three steps:

1. Submit the Certificate Request
2. Certificate Processing
3. Obtain the Certificate

Step 1 - Submit the Certificate Request

1. Browse to the "Certificate Services" web site, choose to "Request a Certificate", then click "Next":

   

2. Choose "Advanced request", then click "Next":

   

3. Choose the option to submit a request using a base64 encoded file, then click "Next":

   

4. Copy the text from your certificate request file and paste it into the "Base64 Encoded Certificate Request" text box, then click "Submit":

   

5. By default, Certificate Services will return a message stating that your certificate is pending. You will need to notify your Certificate Services administrator that your certificate needs to be approved.

   

Step 2 - Certificate Processing

At this point the Certificate Authority (CA) will consider your request. (See processing a Certificate Request for details on issuing your own requests.)

Step 3 - Obtain the Certificate

1. Browse to the "Certificate Services" web site, choose to "Check on a Pending Certificate", then click "Next":

   

2. Highlight your approved request, then click "Next":

   

3. Click the link to "Download CA certificate":

   

4. When prompted, choose to save the file to disk, then click "OK":

   

5. Save the file to somewhere convenient, like your desktop:

   

6. When you have saved the file to your computer, Windows Explorer will display the file with an icon that indicates that it contains a certificate:

   

IIS 5: Setting up SSL - Part 1: Making a Request

21 September 2001 • by Bob • IIS, SSL

1. Bring up the properties for a web site:

   

2. Switch to the "Directory Security" tab and click "Server Certificate:"

   

3. Click "Next" to bypass the first page:

   

4. Choose to "Create a new certificate" and click "Next":

   

5. Choose to "Prepare the request now, but send later" and click "Next":

   

6. Enter a friendly "Name" for the request, and your desired "Bit length". (SGC certificates are only necessary for overseas customers.) Click "Next":

   

7. Enter your "Organization" and "Organization unit", then click "Next":

   

8. Enter the "Common name" for your site then click "Next":
   
   Note: This must be the actual web address that users will browse to when they hit your site.

   

9. Enter your "Country", "State", and "City", then click "Next":

   

10. Enter the "File name" for your request, then click Next:

    

11. Review the information for your request, then click Next:

    

12. Click "Finish" to exit the wizard.

    

FYI: If you were to open your request file in Notepad, it will look something like the following:

IIS 5: Setting up SSL - Overview

21 September 2001 • by Bob • IIS

I wrote a series of instructions for my coworkers some time ago in order to show how to set up and enable Secure Sockets Layer (SSL) communications in IIS. I've had to troubleshoot a bunch of SSL issues over the years, so I thought that it would be a good idea to turn my notes into a blog series.

By way of explanation, setting up SSL on IIS is pretty simple. SSL is a Public Key/Private Key technology, and setting up SSL is essentially obtaining a Public Key from a trusted organization. The basic process for working with SSL is reduced to the following actions:

1. Creating a Certificate Request
2. Obtaining a Certificate from a Certificate Authority
3. Installing the Certificate

While not necessary, installing certificate services on your computer is helpful when troubleshooting SSL issues, and I'll discuss that later in this blog series.

Creating a Certificate Request

This is a series of steps that need to be performed on the web server, and they differ widely depending on the server and version. A web administrator is required to enter information about their organization, their locality, etc. This information will be used to validate the requester.

Obtaining a Certificate from a Certificate Authority

This is when a web administrator submits their request for a certificate to a Certificate Authority (CA), which is a trusted organization like VeriSign or Thawte. For a list of trusted organizations, see the following section in Internet Explorer.

You can choose to trust a new CA by obtaining the Root Certificate from the CA. (I'll post an Obtaining a Root Certificate blog with more information later.)

Installing the Certificate

After a request has been processed by a CA, the web administrator needs to install the certificate on the web server. Once again, this series of steps needs to be performed on the web server, and the steps differ depending on the web server and version.

For the Future...

In future blogs I'll go through the steps for creating certificate requests, obtaining certificates from a CA, and installing certificates. Following that, I'll discuss setting up a CA for testing SSL in your environment.

216-Color Safe Web Palette

23 July 2001 • by Bob • Internet Explorer

In the early days of the Internet, some computers had video capabilities that were limited to 256-color palettes. Since HTML's 24-bit RGB palette supports 16,777,216 colors, someone very smart figured out an algorithm that reduced the full 24-bit color palette into a much smaller 216-color palette that computers with limited color support could utilize.

Today most operating systems don't have a problem with full 24-bit or 32-bit color palettes, but I tend to stick to the 216-color palette in most circumstances just because it's pretty easy to do the math in my head. When you think about the hexadecimal 00-33-66-99-CC-FF progression, it's pretty easy to figure out which colors you need. That said, every once in a while I need to see the subtle differences between colors that are close to each other. With that in mind, it's pretty handy to keep a color palette around, and the following table lists the original 216-color safe web palette that all browsers should support.

Update #1

I should also mention that sometime back in 1998 I wrote a classic ASP page that automatically generates the HTML for the table that I listed, and here's the code for that:

<%
        Response.Write "<center><table border=""1"" cellspacing=0 cellpadding=5 style=""color: #000000; border-collapse: collapse; border: 1px solid #000000; padding: 5px; background-color: #FFFFFF"">" & vbCrLf
        
        Const intFactor = 51

        For X = 255 to 0 Step -intFactor
            For Y = 255 to 0 Step -intFactor
                Response.Write "<tr>" & vbCrLf
                For Z = 255 to 0 Step -intFactor
                    If X < 153 And Y < 153 And Z < 153 Then
                        strFgcolor = "ffffff"
                    Else
                        strFgcolor = "000000"
                    End If
                    strBgcolor = Right("00" & Hex(X),2)
                    strBgcolor = strBgcolor & Right("00" & Hex(Y),2)
                    strBgcolor = strBgcolor & Right("00" & Hex(Z),2)
                    Response.Write "<td style=""border:1px solid #000000;background-color:#" & strBgcolor & ";color:#" & strFgcolor & """>"
                    Response.Write "<tt>" & strBgcolor & "</tt>"
                    Response.Write "</td>"
                Next
                Response.Write "</tr>" & vbCrLf
            Next
        Next

        Response.Write "</table></center>" & vbCrLf
%>

Update #2

A lot of web programmers started out with classic ASP like I did, but like most of those programmers I eventually moved on to ASP.NET. And with that in mind, here's the C# code to create the table that I listed:

<%
        Response.Write("<center><table border=1 cellspacing=0 cellpadding=5 style=\"color: #000000; border-collapse: collapse; border: 1px solid #000000; padding: 5px; background-color: #FFFFFF\">");

        const int intFactor = 51;
        string strFgcolor = "";
        string strBgcolor = "";

        for (int X = 255; X > 0; X -= intFactor)
        {
            for (int Y = 255; Y > 0; Y -= intFactor)
            {
                Response.Write("<tr>");
                for (int Z = 255; Z > 0; Z -= intFactor)
                {
                    if ((X < 153) && (Y < 153) && (Z < 153))
                    {
                        strFgcolor = "ffffff";
                    }
                    else
                    {
                        strFgcolor = "000000";
                    }
                    strBgcolor = String.Format("{0:X2}{1:X2}{2:X2}", X, Y, Z);
                    Response.Write("<td style=\"border:1px solid #000000;font-size: 11pt;padding: 2px; background-color:#" + strBgcolor + ";color:#" + strFgcolor + "\">");
                    Response.Write("<tt>" + strBgcolor + "</tt>");
                    Response.Write("</td>");

                }
                Response.Write("</tr>");
            }
        }

        Response.Write("</table></center>");
%>

History of the FrontPage Personal Web Server

03 May 2001 • by Bob • FrontPage

A Short History of Windows Personal Web Servers

1994 - Bob Denny makes the first NCSA-based web server for Windows:
1995 - Vermeer makes the FrontPage 1.0 Personal Web Server:
1995 - Vermeer also licenses FrontPage to FTP software, which re-brands the Personal Web Server:
1996 - Microsoft releases the FrontPage 1.1 Personal Web Server:
1997 - Microsoft releases the FrontPage 97 Personal Web Server:
1998 - Microsoft releases the FrontPage 98 Personal Web Server:
2000 - Microsoft releases FrontPage 2000 and ceases making a FrontPage Personal Web Server.

The Early FrontPage History

24 October 2000 • by Bob • FrontPage

I have a long history with Microsoft FrontPage, but not many people know where it originally came from. FrontPage started its life as a product from a little startup company from Massachusettes that was named Vermeer Technologies, Inc. To tell the story in detail, I've included Randy Forgaard's foreword from the book Introducing Microsoft FrontPage, by Microsoft Press.

IIS: Notes on Server-Side Includes (SSI) syntax

29 October 1998 • by Bob • IIS

A few years ago I put together a bunch of notes about using Server-Side-Include (SSI) files with IIS 4. These notes eventually became Microsoft KB article Q203064, and I updated that information a couple of years later to incorporate IIS 5. This information is no longer available from Microsoft's support website, so I thought that it would make a good blog post.

SUMMARY

This article details some features that are available in the Microsoft implementation of Server-Side Include (SSI) files for Internet Information Server (IIS) and provides general syntax and examples for SSI directives.

APPLIES TO

• Microsoft Internet Information Services 5.0
• Microsoft Internet Information Server 4.0

MORE INFORMATION

SSI files are most commonly used with IIS to allow content authors to include the contents of one file inside another file, allowing the easy creation of script libraries or page headers and footers.

SSI files, like Active Server Pages (ASP) and Internet Data Connector (IDC) files, are script-mapped by file extension to a preprocessor dynamic-link library (DLL). In the case of SSI, the handler is Ssiinc.dll. SSI files are usually named with .stm file extensions, although extensions of .shtm and .shtml are also supported.

SSI is employed by the use of special preprocessing directives in SSI documents. These directives are parsed by the SSI DLL and processed. All directives are contained in HTML comment tokens and take the following general form:

<!--#<DIRECTIVE> [<ADDITIONAL DATA>]-->

Supported Directives

• #config - Configures how variables and commands are displayed.
  • The general syntax for the #config directive is as follows:

    <!-- #CONFIG <ERRMSG/TIMEFMT/SIZEFMT>="<format>" -->

  • The following is an example of a simple page that uses the #config directive:

    <html>
    <body>
    <!-- #CONFIG TIMEFMT="%m/%d/%y" -->
    <p>Today's Date = <!--#ECHO VAR = "DATE_LOCAL" --></p>
    <!-- #CONFIG TIMEFMT="%A, %B %d, %Y" -->
    <p>Today's Date = <!--#ECHO VAR = "DATE_LOCAL" --></p>
    </body>
    </html>

• #echo - Inserts the value of various Common Gateway Interface (CGI) system environment variables.
  • The general syntax for the #echo directive is as follows:

    <!--#ECHO VAR = "<CGI_VARIABLE_NAME>"-->

  • The following is an example of a simple page that uses the #echo directive:

    <html>
    <body>
    <p>Server Name = <!--#ECHO VAR = "SERVER_NAME"--></p>
    <p>Date = <!--#ECHO VAR = "DATE_LOCAL" --></p>
    <p>Page URL = <!--#ECHO VAR = "URL" --></p>
    </body>
    </html>

• #exec - Executes CGI or Internet Server API (ISAPI) command scripts and inserts output into an HTML document.
  • The general syntax for the #exec directive is as follows:

    <!-- #EXEC <CGI/CMD>="<command>" -->

  • The CMD command for the #exec directive is disabled by default on IIS 5.0. For more information, see the following Microsoft Knowledge Base article:

    233969 SSIEnableCmdDirective is set to FALSE by default

  • The following is an example of a simple page that uses the #exec directive:

    <html>
    <body>
    <p>Root Directory of C:</p>
    <pre><!--#EXEC CMD="cmd /c dir c:\ /b"--></pre>
    </body>
    </html>

• #flastmod - Retrieves the last modification time of a specified file.
  • The general syntax for the #flastmod directive is as follows:

    <!--#FLASTMOD <FILE/VIRTUAL> = "filename.ext"-->

  • The following is an example of a simple page that uses the #flastmod and #config directives:

    <html>
    <body>
    <!-- #CONFIG TIMEFMT="%m/%d/%y" -->
    <p>Modified Date = <!--#FLASTMOD FILE="filename.ext"--></p>
    <!-- #CONFIG TIMEFMT="%B %d, %Y" -->
    <p>Modified Date = <!--#FLASTMOD FILE="filename.ext"--></p>
    </body>
    </html>

• #fsize - Retrieves the size of a specified file.
  • The general syntax for the #fsize directive is as follows:

    <!--#FSIZE <FILE/VIRTUAL> = "filename.ext"-->

  • The following is an example of a simple page that uses the #fsize and #config directives:

    <html>
    <body>
    <!-- #CONFIG SIZEFMT="BYTES" -->
    <p>File Size = <!--#FSIZE FILE="filename.ext"--> bytes</p>
    <!-- #CONFIG SIZEFMT="ABBREV" -->
    <p>File Size = <!--#FSIZE FILE="filename.ext"--> KB</p>
    </body>
    </html>

• #include - Includes the contents of one specified file inside another.
  • The general syntax for the #include directive is as follows:

    <!--#INCLUDE <FILE/VIRTUAL> = "filename.ext"-->

  • The following is an example of a simple page that uses the #include directive:

    <html>
    <body>
    <!--#INCLUDE FILE = "header.inc"-->
    <p>Hello World!</p>
    <!--#INCLUDE VIRTUAL = "/includes/footer.inc"-->
    </body>
    </html>

More Information on File and Virtual Syntax

• The file element is used with files that are relative to the folder of the current document. The following example includes a file in the current folder:

  <!--#include file="myfile.txt"-->

• The virtual element represents paths that are relative to the base folder of the Web server. The following example includes a file in the /scripts virtual folder:

  <!--#include virtual="/scripts/myfile.txt"-->

REFERENCES

For additional information on using SSI with IIS, click the following article numbers to view the articles in the Microsoft Knowledge Base:

• 169996 To run an ISAPI DLL with #exec, use the CGI statement
• 166491 Secure batch files return access denied error message
• 195291 How to disable #exec in Server-Side Include files

Blog Navigation

You are on page 70 of 70 pages.