RE: PC5250 Telnet - security and setup

Not so much on the network but on the servers.  SSL setup is very CPU
intensive.  What it boils down to is you have to trust people in my
position to keep your network and data secure.  Some one has to have the
keys to the Kingdom, hopefully someone else has the key to the journals.


Christopher Bipes
Information Services Director
CrossCheck, Inc.

707.586.0551, ext. 1102
707.585.5700 FAX

Chris.Bipes@xxxxxxxxxxxxxxx
www.Cross-Check.com

Notice of Confidentiality: This e-mail, and any attachments thereto, is
intended only for use by the addressee(s) named herein and may contain
legally privileged and/or confidential information.  If you are not the
intended recipient of this e-mail, you are hereby notified that any
dissemination, distribution or copying of this e-mail, and any
attachments thereto, is strictly prohibited.  If you have received this
e-mail in error, please immediately notify me by e-mail (by replying to
this message) or telephone (noted above) and permanently delete the
original and any copy of any e-mail and any printout thereof.  Thank you
for your cooperation with respect to this matter.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Colin Williams
Sent: Tuesday, December 06, 2005 9:40 AM
To: Midrange Systems Technical Discussion
Subject: Re: PC5250 Telnet - security and setup

Chris,

fair enough, makes sense.

Just never seen SSL used on an internal network. From what you say from
a
security point of view, that would mean that all network traffic would
have
to be encrypted, to protect the CEOs password, now how much additional
load
is that on a network?