|
> Nope, service is correct. For example, I can set up SSL in Client > Access for the entire connection. Then I can go into the 5250 session > and select NO for encryption. That service (telnet) is then not > secured. In other words you can secure one service and not another > between the same two devices. > [Tim McCarthy] That's the part I was agreeing with! (Perhaps up to and including should have been stated) I disagree with the original statement and your response that the initial SSL session handshake is somehow open to attack. Whether you use client side authentication or not the session key is negotiated using the server's public key. If we're challenging public key crypto systems then that's a whole other debate. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.