Timeline for After disabling weak ssh ciphers I cannot ssh in at all
Current License: CC BY-SA 4.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 17, 2024 at 18:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 9, 2023 at 18:07 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Apr 22, 2022 at 15:18 | history | edited | Roan Elizondo | CC BY-SA 4.0 |
added 537 characters in body
|
| Apr 22, 2022 at 14:17 | history | edited | Roan Elizondo | CC BY-SA 4.0 |
added 657 characters in body
|
| Apr 22, 2022 at 13:53 | comment | added | Roan Elizondo |
Ah ok, I get it now. It needs to be sudo service ssh restart and then I get output saying that ssh was stopped and started.
|
|
| Apr 22, 2022 at 13:41 | comment | added | Roan Elizondo |
@steeldriver, ah thanks, this output makes more sense now for service ssh restart I think I get a rejected stop and start that were forwarded to upstart stop: Rejected send message, 1 matched rules; type="method_call", sender=":1.56" (uid=1000 pid=4591 comm="stop ssh ") interface="com.ubuntu.Upstart0_6.Job" member="Stop" error name="(unset)" requested_reply="0" destination="com.ubuntu.Upstart" (uid=0 pid=1 comm="/sbin/init"). From what I just read, it seems like I can use upstart directlly with stop ssh or start ssh which both tell me Unknown job: ssh.
|
|
| Apr 22, 2022 at 8:01 | answer | added | Shadur-don't-feed-the-AI | timeline score: 1 | |
| Apr 22, 2022 at 7:55 | comment | added | Shadur-don't-feed-the-AI | "So I just rebooted my machine" -- future advice? Don't do that, especially when you're not sure your remote access will come back up. | |
| Apr 22, 2022 at 0:17 | comment | added | steeldriver |
FWIW flavors of Ubuntu 14.10 would have used upstart rather than systemd - see for example Upstart or Systemd. Even where systemd is the default init, /usr/sbin/service is provided as a wrapper script for backward compatibility I think. It might just be a matter of sshd being the wrong service name - try service ssh restart or service ssh status for example.
|
|
| Apr 21, 2022 at 23:59 | comment | added | dg99 |
Are you sure that your machine is using service and not systemctl? Try typing systemctl and see what it spits out.
|
|
| S Apr 21, 2022 at 22:56 | review | First questions | |||
| Apr 22, 2022 at 17:27 | |||||
| S Apr 21, 2022 at 22:56 | history | asked | Roan Elizondo | CC BY-SA 4.0 |