92 lines
6.9 KiB
HTML
92 lines
6.9 KiB
HTML
|
<?xml version="1.0" encoding="UTF-8"?>
|
||
|
|
<!DOCTYPE html
|
||
|
|
PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||
|
|
<html lang="en-us" xml:lang="en-us">
|
||
|
|
<head>
|
||
|
|
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
|
||
|
|
<meta name="security" content="public" />
|
||
|
|
<meta name="Robots" content="index,follow" />
|
||
|
|
<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' />
|
||
|
|
<meta name="DC.Type" content="concept" />
|
||
|
|
<meta name="DC.Title" content="Use Secure Sockets Layer to secure the File Transfer Protocol server" />
|
||
|
|
<meta name="abstract" content="With Secure Sockets Layer (SSL) you can eliminate the exposure of transmitting passwords and data in the clear when using the i5/OS File Transfer Protocol (FTP) server with an FTP client that also uses SSL." />
|
||
|
|
<meta name="description" content="With Secure Sockets Layer (SSL) you can eliminate the exposure of transmitting passwords and data in the clear when using the i5/OS File Transfer Protocol (FTP) server with an FTP client that also uses SSL." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqrzaiqimplement.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqsslcertauth.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqsslassoccert.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqsslenableclient.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqsslenablessl.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzain/rzainoverview.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzain/rzainconcepts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzain/rzainplanssl.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzahu/rzahudcmfirsttime.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzahu/rzahurzahu437completenewstore.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaiqtlsssl.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 2004, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzaiqsslparent" />
|
||
|
|
<meta name="DC.Language" content="en-us" />
|
||
|
|
<!-- All rights reserved. Licensed Materials Property of IBM -->
|
||
|
|
<!-- US Government Users Restricted Rights -->
|
||
|
|
<!-- Use, duplication or disclosure restricted by -->
|
||
|
|
<!-- GSA ADP Schedule Contract with IBM Corp. -->
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ibmdita.css" />
|
||
|
|
<link rel="stylesheet" type="text/css" href="./ic.css" />
|
||
|
|
<title>Use Secure Sockets Layer to secure the File Transfer Protocol server</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaiqsslparent"><a name="rzaiqsslparent"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">Use Secure Sockets Layer to secure the File Transfer Protocol server</h1>
|
||
|
|
<div><p>With Secure Sockets Layer (SSL) you can eliminate the exposure
|
||
|
|
of transmitting passwords and data in the clear when using the <span>i5/OS™</span> File
|
||
|
|
Transfer Protocol (FTP) server with an FTP client that also uses SSL.</p>
|
||
|
|
<p>The FTP server provides enhanced security while sending and receiving files
|
||
|
|
over a untrusted network. FTP server uses SSL to secure passwords and other
|
||
|
|
sensitive data during an information exchange. The FTP server supports either
|
||
|
|
SSL or TLS protected sessions, including client authentication and automatic
|
||
|
|
sign-on.</p>
|
||
|
|
<p>Most SSL-enabled applications connect a client to separate TCP ports, one
|
||
|
|
port for "unprotected" sessions and the other for secure sessions. However,
|
||
|
|
secure FTP is a bit more flexible. A client can connect to a non-encrypted
|
||
|
|
TCP port (typically TCP port 21), and then negotiate authentication and encryption
|
||
|
|
options. A client can also choose a secure FTP port (typically TCP port 990),
|
||
|
|
where connections are assumed to be SSL. The iSeries™ FTP server provides for both
|
||
|
|
of these options.</p>
|
||
|
|
<p>Before you can configure the FTP server to use SSL, you must have installed
|
||
|
|
the prerequisite programs and set up digital certificates on your iSeries.</p>
|
||
|
|
<div class="note"><span class="notetitle">Note:</span> Create a local Certificate Authority or use DCM to configure the FTP
|
||
|
|
server to use a public certificate for SSL.</div>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<ol>
|
||
|
|
<li class="olchildlink"><a href="rzaiqsslcertauth.htm">Create a local Certificate Authority</a><br />
|
||
|
|
You can use the IBM<sup>®</sup> Digital Certificate Manager (DCM) to create and operate
|
||
|
|
a local Certificate Authority (CA) on your iSeries server. A local CA enables you
|
||
|
|
to issue private certificates for applications that run on your iSeries server.</li>
|
||
|
|
<li class="olchildlink"><a href="rzaiqsslassoccert.htm">Associate a certificate with the File Transfer Protocol server</a><br />
|
||
|
|
Perform this task if you did not assign a certificate to the File Transfer Protocol (FTP) server application during the creation of the local Certificate Authority (CA), or if you have configured your system to request a certificate from a public CA.</li>
|
||
|
|
<li class="olchildlink"><a href="rzaiqsslenableclient.htm">Require client authentication for the File Transfer Protocol server</a><br />
|
||
|
|
If you need the File Transfer Protocol (FTP) server to authenticate
|
||
|
|
clients, you can change the application specifications in IBM<sup>®</sup> Digital Certificate
|
||
|
|
Manager (DCM). This step is optional.</li>
|
||
|
|
<li class="olchildlink"><a href="rzaiqsslenablessl.htm">Enable Secure Socket Layer on the File Transfer Protocol server</a><br />
|
||
|
|
In order to use Secure Socket Layer (SSL) to secure your File Transfer Protocol (FTP) server, you need to complete the configuration steps first.</li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaiqrzaiqimplement.htm" title="You can protect your data by securing File Transfer Protocol (FTP) with Secure Sockets Layer (SSL), monitoring FTP users, and managing user access to FTP functions.">Secure File Transfer Protocol</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="../rzain/rzainoverview.htm">Secure Sockets Layer (SSL)</a></div>
|
||
|
|
<div><a href="../rzain/rzainconcepts.htm">SSL concepts</a></div>
|
||
|
|
<div><a href="../rzain/rzainplanssl.htm">Prerequisite programs</a></div>
|
||
|
|
<div><a href="rzaiqtlsssl.htm" title="You can use Transport Layer Security (TLS) or Secure Sockets Layer (SSL) connections to encrypt data transferred over File Transfer Protocol (FTP) control and data connections.">Secure the FTP client with Transport Layer Security or Secure Socket Layer</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="reltasks"><strong>Related tasks</strong><br />
|
||
|
|
<div><a href="../rzahu/rzahudcmfirsttime.htm">Set up digital certificates</a></div>
|
||
|
|
<div><a href="../rzahu/rzahurzahu437completenewstore.htm">Use a public certificate</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|