varia/homebrewserver.club
14
0
Fork 0
Code Issues 1 Pull Requests Releases Activity

Just include questions as hints

Browse Source
This commit is contained in:
Luke Murphy 2019-07-01 12:41:36 +02:00
parent 62ae34527e
commit c15a3140e8
No known key found for this signature in database
GPG Key ID: 5E2EF5A63E3718CC
1 changed files with 4 additions and 24 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
content/fundamentals/ssh.md
View File

@ -326,40 +326,20 @@ tips can help you in this process.
Here are some questions to ask yourself:
* Is your public key registered on the server in the `$HOME/.ssh/authorized_keys` folder?
* Are the `$HOME/.ssh` permissions correct? (see this [SO thread](https://superuser.com/questions/215504/permissions-on-private-key-in-ssh-folder))
* Is the SSH server running? (`sudo systemctl status sshd`)
* Are the `$HOME/.ssh` permissions correct? (see [here](https://superuser.com/questions/215504/permissions-on-private-key-in-ssh-folder))
* Is the SSH server running?
* Is the `/etc/ssh/ssd_config` correct?
* Use the [sshd_config](https://man.openbsd.org/sshd_config) as a
reference. Don't forget to run `sudo sshd -t` to validate your
changes. After validating, always restart the SSH server after
making configuration changes
* What does `sudo tail -f /var/log/auth.log` say?
* Every time an SSH client attempts to connect, a log
entry will be put into this file. Some hint as to why
it is failing should be here.
### On the client
Here are some questions to ask yourself:
* What does `ssh -vvvvv myhomebrewserver` tell you?
* Are the `$HOME/.ssh` folder permissions correct? (see this [SO thread](https://superuser.com/questions/215504/permissions-on-private-key-in-ssh-folder))
* Is the SSH server available at the port you expect? (`sudo nmap -p 22 myhomebrewserver`)
* Are the `$HOME/.ssh` folder permissions correct? (see [here](https://superuser.com/questions/215504/permissions-on-private-key-in-ssh-folder))
* Is the SSH server available at the port you expect?
* Is your `$HOME/.ssh/config` correct?
* What is registered with the local `ssh-agent`?
* Check which keys are registered with `ssh-add -L`. If you
see unrecognised keys, you can kill and restart the agent:
* `sudo pkill ssh-agent`
* ` eval "$(ssh-agent -s)"`
* `ssh-add ~/.ssh/id_ed25519`
## Conclusions