×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On Wed, Oct 2, 2019 at 9:37 AM Rob Berendt <rob@xxxxxxxxx> wrote:
We are communicating from IBM i to Windows. This would make Windows the
server.
Ok
they download the .pub file from IBM i to Windows.
That's correct. You would then make that download the authorized_keys file
or append it to an extant authorized_keys file.
The only Windows *sshd server* I have used is Cygwin's, so I don't know
what silliness any other Windows product might exhibit.
That said, your server, whatever it is, is clearly running.
Things that can go wrong:
- no matching key (seems ruled out)
- wrong perms on server .ssh dir (seems ruled out)
- wrong perms on home dir (some ssh implementation also want the home
dir above .ssh to be unreadable by outsiders
- formatting flaws in authorized_keys file (line breaks inside key)
- no matching cyphers
- bad directives in sshd_config
That's pretty much the list.
Did you run the ssh command from the IBM i with -v -v -v yet?
More -v's make more debug info. 90% of the time you can find it there.
midrange.com
