On Aug 4, 2006, at 9:47 AM, Alan Altmark wrote:
If no one opens a PMR, it doesn't get fixed. (Stop me if I start
repeating myself.) If no one calls it in, and the problem has been in
existence for multiple releases, then the pressure to fix it in the
"next"
release is non-existent. It is frowned upon for us to open an APAR
without a customer PMR.
Fair enough. I am, of course, reluctant to open a PMR until I am
pretty sure that it's the fault of the VM side o' things. And from
what I can see...it may be the fault of the client not attempting SSL
on the data.
Right, and to initiate an SSL handshake on the data connection.
Yeah, that's what:
Thread Client_Socket_Address Server_Socket_Address Connection
Cipher
1 192.168.253.18:50429 192.168.131.1:1075 1012 NONE
Makes me suspicious of.
Your trace indicates that your client is tried to use in-band FTP
security
techniques. Have you confirmed that it is performing an SSL
handshake on
the data connection?
This is the bit that I'm suspecting. So, let's try a different
tactic: what FTP clients are known to do implicit SSL the *right* way
for the VM stack? If I can get one of *those* working, then it's
clear that the problem is in my client, not in the SSL implementation
or VM's handling of it.
Adam
