Timeline for Login remote webserver without ssh password
Current License: CC BY-SA 4.0
21 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 22, 2019 at 12:36 | history | edited | fra-san | CC BY-SA 4.0 | Fixed numbered list formatting, harmonized code formatting (backticks were shown in code snippets instead of being parsed as markdown) |
| Dec 4, 2018 at 12:33 | comment | added | dave_thompson_085 | In step 2 adding pubkey to authorized_keys should be on the remote (note the apple.SX Q you link explicitly says this) | |
| Dec 4, 2018 at 9:19 | comment | added | Jenny D | Look at the sshd logs on the server. It's highly probable that the answer can be found there, even without running the sshd in debug mode. The log can be named /var/log/messages, /var/log/auth.log, /var/log/security or /var/log/syslog - if you can't find it, you can just do grep sshd /var/log/* and it should show up. | |
| Dec 4, 2018 at 8:13 | answer | added | BowlOfRed | timeline score: 0 | |
| Dec 1, 2018 at 16:28 | answer | added | Michael Prokopec | timeline score: 0 | |
| Dec 1, 2018 at 15:13 | comment | added | RubberStamp | Try... on the server, as root user, ls -l /etc/ssh/*key if there are no keys generate them using ssh-keygen -A ... if there are keys, check their fingerprints with ssh-keygen -l -f /etc/ssh/ssh_host_rsa_key and any others that are present. And then check if any of those fingerprints match what is in your local machine's ~/.ssh/known_hosts file... it may also be useful to know what format the server's host keys are in... as root on the server, cat /etc/ssh/*key |grep BEGIN | |
| Dec 1, 2018 at 6:56 | comment | added | BowlOfRed | Go ahead and paste the output. You're looking for something where it tries to authenticate the client. If its denied, the client won't be told why (so the ssh -v output may not have the details). But the sshd debug will have more details (like file permission issues or key issues). | |
| Dec 1, 2018 at 3:03 | history | edited | user10726006 | CC BY-SA 4.0 | added 332 characters in body |
| Dec 1, 2018 at 3:03 | comment | added | user10726006 | it report the same result. @grifferz | |
| Dec 1, 2018 at 2:52 | comment | added | grifferz | You need to run the debug sshd as root in order for it to be able to read the host keys. | |
| Dec 1, 2018 at 2:49 | comment | added | user10726006 | I test to append the result. Honestly I cannot really read the report. It seems that I have to learn the complete ssh theory to solve a problem. @BowlOfRed | |
| Dec 1, 2018 at 2:47 | history | edited | user10726006 | CC BY-SA 4.0 | added 328 characters in body |
| Dec 1, 2018 at 0:17 | comment | added | BowlOfRed | Run the ssh server in debug mode and see the output. Often easier to run a separate debug server on another port (like /usr/sbin/sshd -d -p 2222). Then watch as you connect to that server from your client. | |
| Nov 30, 2018 at 23:46 | history | edited | user10726006 | CC BY-SA 4.0 | added 8263 characters in body |
| Nov 30, 2018 at 16:43 | comment | added | user10726006 | yes, and I also want to have more secure so to use pub and private key. @StephenHarris | |
| Nov 30, 2018 at 16:35 | history | edited | user10726006 | CC BY-SA 4.0 | added 784 characters in body |
| Nov 30, 2018 at 16:28 | comment | added | Stephen Harris | Also check the PermitRootLogin setting in sshd_config | |
| Nov 30, 2018 at 16:27 | answer | added | ryekayo | timeline score: 2 | |
| Nov 30, 2018 at 16:25 | comment | added | ryekayo | Your permissions are wrong. Change your key perms to 600 instead of 700 | |
| Nov 30, 2018 at 16:25 | review | First posts | |||
| Nov 30, 2018 at 16:39 | |||||
| Nov 30, 2018 at 16:23 | history | asked | user10726006 | CC BY-SA 4.0 |