FP97: How to Use Secure Sockets Layer to Help Protect Pages in Your Web This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
This article was previously published under Q174424 For a Microsoft FrontPage 2002 version of this
article, see
292633 (http://support.microsoft.com/kb/292633/EN-US/). For a Microsoft FrontPage 2000 version of this article, see 205698 (http://support.microsoft.com/kb/205698/EN-US/). For a Microsoft FrontPage 98 version of this article, see 194072 (http://support.microsoft.com/kb/194072/EN-US/). On This PageSUMMARY When you create a new FrontPage Web, you can select the
Secure Connection Required option. When you select this option, the entire Web
will use the Secure Socket Layer (SSL) port to encrypt all data sent to or from
FrontPage. This is called secure authoring. You can also specify whether you
want to use the SSL port for links to specific pages within a normal, unsecured
Web. This is called secure browsing. This article describes how to accomplish
both secure authoring and secure browsing. MORE INFORMATIONSecure AuthoringTo use SSL for secure authoring, follow these steps:
To guarantee authenticity, a certificate accompanies the public key. A certificate is a digital signature on a digest of the friendly (human readable) name of the participant, together with the participant's public key. The certificate is encrypted with the private key of the certifying authority. To check the authenticity of the public key of the participant, anyone can compute the digest of the friendly name and public key for that participant and can decrypt the certificate for that public key using the public key of the certifying authority, and check that the same digest results. NOTE: FrontPage 97 does not support 128-bit encryption; only 40-bit encryption. For additional information about the use of security certificates with FrontPage, please see the following article in the Microsoft Knowledge Base: 171675 (http://support.microsoft.com/kb/171675/EN-US/) FP: Socket Code 13101 Error Opening, Creating New Web
Secure BrowsingIf you want to require that SSL be used to browse some of your pages, you can mix ports on a single Web by using a fully qualified Uniform Resource Locator (URL), such as http://microsoft.com/default.htm.Web servers use a separate port for SSL connections. For example, instead of linking to
default.htm
they link to
https://microsoft.com/default.htm
and go from the default port (usually 80) to the SSL port
(usually 443). To go from the SSL port to port 80, link to http://microsoft.com/default.htm To create a SSL link from a page in your Web for secure browsing,
follow these steps:
| Article Translations
|


Back to the top
