It is detectable on the non-z/OS side as the non-z/OS side still need to do SSL/TLS. It's only transparent on the z/OS side and for FTP (client or server) it is only "semi-transparent." For FTP the z/OS server/client knows that that SSL/TSL is being used, it is just not using SystemSSL directly. AT-TLS is making all of the SystemSSL calls and z/OS server/client code see plain text.
For some z/OS applications AT-TLS is truly transparent on the z/OS side. The remote side still has to support SSL/TLS so it know. Unless of course the other side is also z/OS running AT-TLS. On Tue, 17 Sep 2024 10:59:39 -0500, Paul Gilmartin <[email protected]> wrote: >On Tue, 17 Sep 2024 05:15:13 +0000, Timothy Sipples wrote: > >> ... >>A very long while. z/OS 1.2 (Generally Available on October 26, 2001) >>introduced support for TLS/SSL FTP (a.k.a. FTPS) along with related security >>enhancements. That was for both the FTP client and server. Of course there >>have been many FTPS-related improvements in z/OS releases since then. >> . >Is it evident in the client terminal window that the connection >is not/is encrypted? (I'm envisioning something like the lock >favicon in a browser window.) Alas, if the mechanism is fully >transparent the encryption condition might not be dectable >by that client. > >-- >gil > >---------------------------------------------------------------------- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
