Actually, removing the ClientAliveInterval has no effect on a stock Ubuntu ssh client. Sessions stay alive for hours with no input. I'm going to propose a patch to pull out that change. The password authentication portion seems to be valid (or even required) for Azure (as you can still create instances without ssh keys.) I need to investigate how ubuntu-server does this differently from ubuntu-desktop (as I see a different default in a desktop.)
No package seems to "own" /etc/ssh/sshd_config ("dpkg -S /etc/ssh/sshd_config" returns nothing and "grep sshd_config Contents-amd64" doesn't return /etc/ssh/sshd_config. Does this mean it will still be an issue on upgrade?
Actually, removing the ClientAliveInterval has no effect on a stock Ubuntu ssh client. Sessions stay alive for hours with no input. I'm going to propose a patch to pull out that change. The password authentication portion seems to be valid (or even required) for Azure (as you can still create instances without ssh keys.) I need to investigate how ubuntu-server does this differently from ubuntu-desktop (as I see a different default in a desktop.)
No package seems to "own" /etc/ssh/ sshd_config ("dpkg -S /etc/ssh/ sshd_config" returns nothing and "grep sshd_config Contents-amd64" doesn't return /etc/ssh/ sshd_config. Does this mean it will still be an issue on upgrade?