On 8/29/19 12:23 PM, Anton Aylward wrote:
SSH insists on encryption, but there are apparently patches that will allow it to be turned off. Well SSH can be set up so that the login, while a key exchange, is done transparently & automagically for that 'known host'. This sounds simpler and is well documented, plenty of examples in help files. Abut as complicated as the use of .rhosts. I'd choose it over 'munge'.
I think the option you are talking about is the one that lets you choose what encryption protocol to use for the data transfer after the authentication is done. Choose 'plain text'.
I think you want -c cipher_spec Selects the cipher specification for encrypting the session.
see also SSH_CONFIG(5) THEN try and find the patch that lets you select 'plain text'.
Yes, we use pre-placed public ssh keys for logins. I've never mucked with munge. I don't believe that you can use "none" in sshd without enabling it in source and recompiling. There are some patches that do this, but still require recompilation. That's always an option I guess... Regards, Lew -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org