Timeline for How to disable weak ciphers in SSH?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 29, 2023 at 14:13 | comment | added | rudolfbyker | Newer ssh-audit: github.com/jtesta/ssh-audit | |
| May 8, 2020 at 23:12 | comment | added | rubo77 |
onleine to check if all ciphers are in your system: for i in $(sudo sshd -T -C user=root | grep ciphers |cut -d " " -f2- | perl -pe 's/,/ /g'); do echo '##'check $i; ssh -Q cipher | grep $i; done
|
|
| May 8, 2020 at 23:05 | comment | added | rubo77 |
I had to use sshd -T -C user=root instead of just sshd -T, also cut out the initial word with sudo sshd -T -C user=root | grep ciphers |cut -d " " -f2- | perl -pe 's/,/\n/g' | sort -u
|
|
| Nov 19, 2018 at 20:13 | history | edited | Mark Stosberg | CC BY-SA 4.0 |
Format both server and client lists as line-based and sorted for easier comparison.
|
| S Apr 6, 2018 at 7:40 | history | suggested | Adam Friedman | CC BY-SA 3.0 |
added a solution that seems more future-proofed and less prescriptive.
|
| Apr 6, 2018 at 1:48 | review | Suggested edits | |||
| S Apr 6, 2018 at 7:40 | |||||
| Dec 30, 2016 at 13:07 | history | edited | savageBum | CC BY-SA 3.0 |
added config verification instructions
|
| Dec 30, 2016 at 13:01 | review | First posts | |||
| Dec 30, 2016 at 13:12 | |||||
| Dec 30, 2016 at 12:59 | history | answered | savageBum | CC BY-SA 3.0 |