|
port blocking and forcing telnet to use obscure ports sounds an awful lot like "security by obscurity", the hackers will figure it out by port scanning faster than your users will adapt to the change. However I believe that telnet ssl will use some obscure port, and will make it dang rough to scan the network traffic and sniff passwords and such. Like regular telnet, some client side software is involved. Joe Pluta is supposed to have some software that will have the look and feel of 5250 over the web but no client side software is needed other than MSIE. Now, if you're in the "Bill is the AntiChrist" camp and love thwarting your users productivity by not having the keyboard work exactly like it would if they were local, you might find some other solution that doesn't require MSIE. Don't know your reasons for must be 5250. Could be productivity. Could be ease of implementing change. Don't know how much complexity to changes Joe's software adds. I'm sure Joe feels it adds little to none. :-) Other solutions, such as IBM's iSeries Access for the Web might be worth looking into. I am hopeful that both Joe's solution, and IBM's solution, both allow you to SSL your connection. Probably need to take this discussion over to the web400 list now though. Rob Berendt
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.