[Info-vax] stumped by SSH

[Neil Rieck]

IMHO we are all just groping in the dark. If we are convinced that this issue has been isolated to SSH/SSH2 subsystem, then the only way forward is to enable verbose logging of the SSH2 daemon (server process), restart the daemon, then attempt a connection. 

If the daemon is seeing problems then they will be logged. (includes issues related to file protection bits, file ownership, etc.)

You can also enable verbose messaging from the client side but they will not always tell your about server-side problem-details. 

Beware that setting the logging level too high (like greater than 6) can provide you with too much information.

Neil Rieck
Waterloo, Ontario, Canada.
http://bellics.com/ovms/docs/openvms_notes_ssh2.html