RE: UPDATE: FTP & SSL

OOPS, that should have been Not allow it

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark Allen
Sent: Friday, May 23, 2003 11:26 AM
To: midrange-l@xxxxxxxxxxxx
Subject: UPDATE: FTP & SSL


It was determined that the entire issue was due to the fact that the
server we were attempting to get files from has the control channel
unencrypted with the data channel encrypted.  the OS/400 FTP client only
lets you set the data channel to unencrypted (*CLEAR) or encrypted
(*PRIVATE) and sets the control channel to whatever the data channel is.
 
Since the customer we are connecting to refuses (at least so far) to
change on their end I submitted a PMR to IBM that has since turned into
a DCR to allow controlling the control channel seperately or allowing
you to connect unencrypted and then use the SECDATA P ftp subcommand to
change only the data channel.  Currently if you try the SECDATA P
subcommand while connected unencrypted it will <INSERT> NOT </INSERT>
allow it saying for the data channel to be private the control channel
must be private.
 
 
 
Mark Allen
IS Manager
Wilkes Telephone & Electric
11 W. Court Street
Washington, GA 30673
Phone: (706) 678-9565
Fax: (706) 678-1000
 

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.