Re: Inbound SSH allowed to be used with Code for i and other tools?

Spurious. You obviously don't understand the statement.

Apparently you've never programmed using jt400. Not a significant undertaking at all. Just time and effort and desire.

A custom protocol is not needed since the code for I server is Java. Using connectivity that's already available and monitorable over the standard connectivity ports being used by jt400, ODBC, etc you now have something controllable. And it can be SSL enabled.

Anyway this is off the path of "sell me on why I should use SSH".

You've still not provided your version of a useful pitch for why a CIO should allow SSH to be enabled 😊

Let's see what you can provide.

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
------------------------------

message: 4
date: Thu, 31 Oct 2024 08:51:32 -0400
from: John Yeung <gallium.arsenide@xxxxxxxxx>
subject: Re: Inbound SSH allowed to be used with Code for i and other
tools ?

On Wed, Oct 30, 2024 at 2:51?PM Richard Schoen <richard@xxxxxxxxxxxxxxxxx> wrote:

Would be interesting to see Mapepire and/or codefori server morphed into an appropriate server that wouldn't require an SSH connect.

That would be a significant undertaking. You're essentially proposing to create a brand-new, completely custom connection protocol. Not worth the effort over simply understanding SSH better and setting it up appropriately.

I've done connectivity via jt400 in Java and .Net for years before we had SSH.

This is a completely spurious argument. JDBC is no more secure than ODBC, and neither of them is as secure as SSH. It's like saying "I"ve done telnet connectivity for years before we had JDBC." Yeah, OK, so what?

John Y.


------------------------------