RE: Telnet concerns from auditors

You only need to create one certificate for your Telnet Server. It can
be self signed or you can purchase one for the FQDN you use to connect
to your iSeries telnet server. I went with the self signed route and
had to import it into all the CA stores on the PC's using Client Access.
However using a program such as Mochasoft does not verify the server
certificate and it works with no client side certificate. It just
encrypts your data, does not protect you from man in the middle attacks
or validate client side certificates. (Client side certificates to
validate a user has access to the server is the real pain.)

DCM is used to create the self signed certificate and assign it, or a
purchased certificate, to the application. Does not take much to do and
does not have to be running once the certificate has been assigned.



Chris Bipes
Director of Information Services
CrossCheck, Inc.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Ketzes, Larry
Sent: Thursday, October 02, 2008 12:29 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Telnet concerns from auditors

Setting up SSL Telnet would mean using the Digital Certificate Manager,
correct? Is that an administrative nightmare for hundreds of users, or
is there a method of using a 'blanket' cert that would cover an entire
box?