70 lines
5.1 KiB
HTML
70 lines
5.1 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="SSL for secure Telnet access" />
|
||
|
|
<meta name="abstract" content="You can configure your Telnet server to use the Secure Sockets Layer (SSL) to secure Telnet communications sessions." />
|
||
|
|
<meta name="description" content="You can configure your Telnet server to use the Secure Sockets Layer (SSL) to secure Telnet communications sessions." />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="rzaj45bydigitalcerts.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzaiw/rzaiwscenariossl.htm" />
|
||
|
|
<meta name="DC.Relation" scheme="URI" content="../rzahu/rzahurzahu4aagetstarteddcm.htm" />
|
||
|
|
<meta name="copyright" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Rights.Owner" content="(C) Copyright IBM Corporation 1999, 2006" />
|
||
|
|
<meta name="DC.Format" content="XHTML" />
|
||
|
|
<meta name="DC.Identifier" content="rzaj45raddingtelnet" />
|
||
|
|
<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>SSL for secure Telnet access</title>
|
||
|
|
</head>
|
||
|
|
<body id="rzaj45raddingtelnet"><a name="rzaj45raddingtelnet"><!-- --></a>
|
||
|
|
<!-- Java sync-link --><script language="Javascript" src="../rzahg/synch.js" type="text/javascript"></script>
|
||
|
|
<h1 class="topictitle1">SSL for secure Telnet access</h1>
|
||
|
|
<div><p>You can configure your Telnet server to use the Secure Sockets
|
||
|
|
Layer (SSL) to secure Telnet communications sessions. </p>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" />To configure your Telnet server to use SSL, you must use Digital
|
||
|
|
Certificate Manager (DCM) to configure the certificate for the
|
||
|
|
Telnet server to use. By default the Telnet server handles both secure and
|
||
|
|
non-secure connections. However, you can configure Telnet so that it allows
|
||
|
|
only secure Telnet sessions. Additionally, you can configure the Telnet server
|
||
|
|
to use digital certificates for stronger client authentication.<img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" />When you choose to use SSL with Telnet, you gain some strong
|
||
|
|
security benefits. For Telnet, besides server authentication, the data is
|
||
|
|
encrypted before any Telnet protocol data flows. Once the SSL session is established,
|
||
|
|
all Telnet protocols including user ID and password exchange, are encrypted.<img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
<p>The most important factor to consider when using the Telnet server is the
|
||
|
|
sensitivity of the information that you use in a client session. If the information
|
||
|
|
is sensitive or private, then you may find it beneficial to set up your iSeries™ Telnet
|
||
|
|
server using SSL. When you configure a digital certificate for the Telnet
|
||
|
|
application, the Telnet server is able to operate with both SSL and non-SSL
|
||
|
|
clients. If your security policy requires that you always encrypt your Telnet
|
||
|
|
sessions, you can disable all non-SSL Telnet sessions. When there is no need
|
||
|
|
for you to use the SSL Telnet server, you can turn off the SSL port. You can
|
||
|
|
disable the ports using the ADDTCPPORT command. Once you have turned off the
|
||
|
|
port, the server provides non-SSL Telnet for the clients, and the SSL Telnet
|
||
|
|
sessions are disabled.</p>
|
||
|
|
<p><img src="./delta.gif" alt="Start of change" /> To learn more about Telnet and about
|
||
|
|
security tips for Telnet with and without SSL, The <span class="keyword"><img src="./delta.gif" alt="Start of change" />IBM<sup>®</sup> Systems Software Information Center<img src="./deltaend.gif" alt="End of change" /></span> topic on <a href="../rzaiw/rzaiwgetstart.htm">Telnet</a> provides the information that you need to use
|
||
|
|
Telnet on your iSeries server.<img src="./deltaend.gif" alt="End of change" /></p>
|
||
|
|
</div>
|
||
|
|
<div>
|
||
|
|
<div class="familylinks">
|
||
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="rzaj45bydigitalcerts.htm" title="Digital certificates provide the foundation for using the Secure Sockets Layer (SSL) for secure communications and as a stronger means of authentication.">Using digital certificates for SSL</a></div>
|
||
|
|
</div>
|
||
|
|
<div class="relconcepts"><strong>Related concepts</strong><br />
|
||
|
|
<div><a href="../rzaiw/rzaiwscenariossl.htm">Secure Telnet</a></div>
|
||
|
|
<div><a href="../rzahu/rzahurzahu4aagetstarteddcm.htm">Digital certificate</a></div>
|
||
|
|
</div>
|
||
|
|
</div>
|
||
|
|
</body>
|
||
|
|
</html>
|