4 ms·
SSH is no different on macOS to Linux. Go and look in the usual places: /etc/ssh/sshd_config and /var/log. If you really are still stuck, disable Remote Login f
by neilalexander 8y ago
SSH is no different on macOS to Linux. Go and look in the usual places: /etc/ssh/sshd_config and /var/log. If you really are still stuck, disable Remote Login from the Sharing panel and start sshd yourself in a Terminal in verbose mode.
- inetknght 8y agoThis is what I'll do when I get home
- neilalexander 8y agoYou might find that running sshd in a Terminal is probably the best way to get a sense of what's really going on if the logging level isn't high enough by default - things like cipher disagreements would probably be visible on the client, whereas authentication errors are more likely to be logged on the target side. Do come back with how you get on!
- inetknght 8y agoSo it turns out that I had deleted my shell, which also explains why iTerm and Terminal would instantly die. Fixed it with `chsh` and now all that good stuff works \o/
- neilalexander 8y agoGlad to hear it!
- PeterMikhailov 8y agoI don't think that's true. You have to screw around with launchctl. The original poster probably has to add the ability for a specific user to ssh to the box in "remote access"
- neilalexander 8y agoThe "Remote Login" checkbox in System Preferences actually does something equivalent to the `systemsetup` command. If you uncheck it, the daemon stops running, and you can then make changes or run it yourself.