SSH: How to disable weak ciphers?

Clash Royale CLAN TAG#URR8PPP
up vote
34
down vote
favorite
Security team of my organization told us to disable weak ciphers due to they issue weak keys.
arcfour
arcfour128
arcfour256
But I tried looking for these ciphers in ssh_config and sshd_config file but found them commented.
grep arcfour *
ssh_config:# Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc
Where else I should check to disable these ciphers from SSH?
ssh encryption
add a comment |Â
up vote
34
down vote
favorite
Security team of my organization told us to disable weak ciphers due to they issue weak keys.
arcfour
arcfour128
arcfour256
But I tried looking for these ciphers in ssh_config and sshd_config file but found them commented.
grep arcfour *
ssh_config:# Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc
Where else I should check to disable these ciphers from SSH?
ssh encryption
add a comment |Â
up vote
34
down vote
favorite
up vote
34
down vote
favorite
Security team of my organization told us to disable weak ciphers due to they issue weak keys.
arcfour
arcfour128
arcfour256
But I tried looking for these ciphers in ssh_config and sshd_config file but found them commented.
grep arcfour *
ssh_config:# Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc
Where else I should check to disable these ciphers from SSH?
ssh encryption
Security team of my organization told us to disable weak ciphers due to they issue weak keys.
arcfour
arcfour128
arcfour256
But I tried looking for these ciphers in ssh_config and sshd_config file but found them commented.
grep arcfour *
ssh_config:# Ciphers aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-cbc,3des-cbc
Where else I should check to disable these ciphers from SSH?
ssh encryption
ssh encryption
edited Dec 30 '16 at 12:06
Jeff Schaller
33.8k851113
33.8k851113
asked Dec 30 '16 at 9:29
rÃÂÃÂdÃÂÃÂ
2,43472551
2,43472551
add a comment |Â
add a comment |Â
4 Answers
4
active
oldest
votes
up vote
27
down vote
accepted
If you have no explicit setting, the default value, according to man 5 ssh_config (client-side) and man 5 sshd_config (server-side), is:
aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,
aes128-gcm@openssh.com,aes256-gcm@openssh.com,
chacha20-poly1305@openssh.com,
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,
aes256-cbc,arcfour
Note the presence of the arcfour ciphers. So you may have to explicitly set a more restrictive value for Ciphers.
ssh -Q cipher from the client will tell you which schemes your client supports.
nmap --script ssh2-enum-algos -sV -p <port> <host> will tell you which schemes your server supports.
Hi , I mentioned specific ciphers in ssh_config and restarted ssh service but when I did ssh -Q cipher <hostname> I am still getting all ciphers that I am getting earlier irrespective of my configuration.
â rÃÂÃÂdÃÂÃÂ
Dec 30 '16 at 10:30
1
I'm sorry,ssh_configis the client-side config, the server-side config issshd_config, please try that. (It's also calledCiphersthere.)
â Ulrich Schwarz
Dec 30 '16 at 10:42
Yeah I know but when I grep for ciphers I found them at ssh_config so I did changes there. As production server I am not doing anything I am not sure
â rÃÂÃÂdÃÂÃÂ
Dec 30 '16 at 10:46
Note that the defaults may differ between distributions.
â Jonas Schäfer
Dec 30 '16 at 13:33
add a comment |Â
up vote
22
down vote
To disable RC4 and use secure ciphers on SSH server, hard-code the following in /etc/ssh/sshd_config
ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
OR if you prefer not to dictate ciphers but merely want to strip out insecure ciphers, run this on the command line instead (in sudo mode):
sshd -T | grep ciphers | sed -e "s/(3des-cbc|aes128-cbc|aes192-cbc|aes256-cbc|arcfour|arcfour128|arcfour256|blowfish-cbc|cast128-cbc|rijndael-cbc@lysator.liu.se),?//g" >> /etc/ssh/sshd_config
You can check ciphers currently used by your server with:
sudo sshd -T |grep ciphers
Make sure your ssh client can use these ciphers, run ssh -Q cipher to see the list.
You can also instruct your SSH client to negotiate only secure ciphers with remote servers. In /etc/ssh/ssh_config set:
Host *
ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
Above snippets come from here
To test your server's settings you can use ssh-audit
add a comment |Â
up vote
8
down vote
The problem with explicitly specifying a cipher list is that you must manually add new ciphers as they come out. Instead, simply list the ciphers you want to remove, prepending the list (not each individual cipher) with a '-' character. So in this case, the Ciphers line should read:
Ciphers -arcfour*
Or if you prefer:
Ciphers -arcfour,arcfour128,arcfour256
From the sshd_config man page on the Ciphers option (since OpenSSH 7.5, released 2017-03-20):
If the specified value begins with a âÂÂ+â character, then the specified ciphers will be appended to the default set instead of replacing them. If the specified value begins with a âÂÂ-â character, then the specified ciphers (including wildcards) will be removed from the default set instead of replacing them.
This also applies to the KexAlgorithms and MACs options.
add a comment |Â
up vote
0
down vote
enable/disable cipher need to add/remove in file /etc/ssh/sshd_config
ssh -Q cipher from the client will tell you which schemes support
ssh localhost -c arcfour check arcfour cipher enable or not on the server
ssh localhost -c arcfour128 check arcfour128 cipher enable or not on the server
New contributor
Kumar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
27
down vote
accepted
If you have no explicit setting, the default value, according to man 5 ssh_config (client-side) and man 5 sshd_config (server-side), is:
aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,
aes128-gcm@openssh.com,aes256-gcm@openssh.com,
chacha20-poly1305@openssh.com,
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,
aes256-cbc,arcfour
Note the presence of the arcfour ciphers. So you may have to explicitly set a more restrictive value for Ciphers.
ssh -Q cipher from the client will tell you which schemes your client supports.
nmap --script ssh2-enum-algos -sV -p <port> <host> will tell you which schemes your server supports.
Hi , I mentioned specific ciphers in ssh_config and restarted ssh service but when I did ssh -Q cipher <hostname> I am still getting all ciphers that I am getting earlier irrespective of my configuration.
â rÃÂÃÂdÃÂÃÂ
Dec 30 '16 at 10:30
1
I'm sorry,ssh_configis the client-side config, the server-side config issshd_config, please try that. (It's also calledCiphersthere.)
â Ulrich Schwarz
Dec 30 '16 at 10:42
Yeah I know but when I grep for ciphers I found them at ssh_config so I did changes there. As production server I am not doing anything I am not sure
â rÃÂÃÂdÃÂÃÂ
Dec 30 '16 at 10:46
Note that the defaults may differ between distributions.
â Jonas Schäfer
Dec 30 '16 at 13:33
add a comment |Â
up vote
27
down vote
accepted
If you have no explicit setting, the default value, according to man 5 ssh_config (client-side) and man 5 sshd_config (server-side), is:
aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,
aes128-gcm@openssh.com,aes256-gcm@openssh.com,
chacha20-poly1305@openssh.com,
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,
aes256-cbc,arcfour
Note the presence of the arcfour ciphers. So you may have to explicitly set a more restrictive value for Ciphers.
ssh -Q cipher from the client will tell you which schemes your client supports.
nmap --script ssh2-enum-algos -sV -p <port> <host> will tell you which schemes your server supports.
Hi , I mentioned specific ciphers in ssh_config and restarted ssh service but when I did ssh -Q cipher <hostname> I am still getting all ciphers that I am getting earlier irrespective of my configuration.
â rÃÂÃÂdÃÂÃÂ
Dec 30 '16 at 10:30
1
I'm sorry,ssh_configis the client-side config, the server-side config issshd_config, please try that. (It's also calledCiphersthere.)
â Ulrich Schwarz
Dec 30 '16 at 10:42
Yeah I know but when I grep for ciphers I found them at ssh_config so I did changes there. As production server I am not doing anything I am not sure
â rÃÂÃÂdÃÂÃÂ
Dec 30 '16 at 10:46
Note that the defaults may differ between distributions.
â Jonas Schäfer
Dec 30 '16 at 13:33
add a comment |Â
up vote
27
down vote
accepted
up vote
27
down vote
accepted
If you have no explicit setting, the default value, according to man 5 ssh_config (client-side) and man 5 sshd_config (server-side), is:
aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,
aes128-gcm@openssh.com,aes256-gcm@openssh.com,
chacha20-poly1305@openssh.com,
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,
aes256-cbc,arcfour
Note the presence of the arcfour ciphers. So you may have to explicitly set a more restrictive value for Ciphers.
ssh -Q cipher from the client will tell you which schemes your client supports.
nmap --script ssh2-enum-algos -sV -p <port> <host> will tell you which schemes your server supports.
If you have no explicit setting, the default value, according to man 5 ssh_config (client-side) and man 5 sshd_config (server-side), is:
aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,
aes128-gcm@openssh.com,aes256-gcm@openssh.com,
chacha20-poly1305@openssh.com,
aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,
aes256-cbc,arcfour
Note the presence of the arcfour ciphers. So you may have to explicitly set a more restrictive value for Ciphers.
ssh -Q cipher from the client will tell you which schemes your client supports.
nmap --script ssh2-enum-algos -sV -p <port> <host> will tell you which schemes your server supports.
edited Jul 10 '17 at 3:48
jarfil
54
54
answered Dec 30 '16 at 9:35
Ulrich Schwarz
9,09512743
9,09512743
Hi , I mentioned specific ciphers in ssh_config and restarted ssh service but when I did ssh -Q cipher <hostname> I am still getting all ciphers that I am getting earlier irrespective of my configuration.
â rÃÂÃÂdÃÂÃÂ
Dec 30 '16 at 10:30
1
I'm sorry,ssh_configis the client-side config, the server-side config issshd_config, please try that. (It's also calledCiphersthere.)
â Ulrich Schwarz
Dec 30 '16 at 10:42
Yeah I know but when I grep for ciphers I found them at ssh_config so I did changes there. As production server I am not doing anything I am not sure
â rÃÂÃÂdÃÂÃÂ
Dec 30 '16 at 10:46
Note that the defaults may differ between distributions.
â Jonas Schäfer
Dec 30 '16 at 13:33
add a comment |Â
Hi , I mentioned specific ciphers in ssh_config and restarted ssh service but when I did ssh -Q cipher <hostname> I am still getting all ciphers that I am getting earlier irrespective of my configuration.
â rÃÂÃÂdÃÂÃÂ
Dec 30 '16 at 10:30
1
I'm sorry,ssh_configis the client-side config, the server-side config issshd_config, please try that. (It's also calledCiphersthere.)
â Ulrich Schwarz
Dec 30 '16 at 10:42
Yeah I know but when I grep for ciphers I found them at ssh_config so I did changes there. As production server I am not doing anything I am not sure
â rÃÂÃÂdÃÂÃÂ
Dec 30 '16 at 10:46
Note that the defaults may differ between distributions.
â Jonas Schäfer
Dec 30 '16 at 13:33
Hi , I mentioned specific ciphers in ssh_config and restarted ssh service but when I did ssh -Q cipher <hostname> I am still getting all ciphers that I am getting earlier irrespective of my configuration.
â rÃÂÃÂdÃÂÃÂ
Dec 30 '16 at 10:30
Hi , I mentioned specific ciphers in ssh_config and restarted ssh service but when I did ssh -Q cipher <hostname> I am still getting all ciphers that I am getting earlier irrespective of my configuration.
â rÃÂÃÂdÃÂÃÂ
Dec 30 '16 at 10:30
1
1
I'm sorry,
ssh_config is the client-side config, the server-side config is sshd_config, please try that. (It's also called Ciphers there.)â Ulrich Schwarz
Dec 30 '16 at 10:42
I'm sorry,
ssh_config is the client-side config, the server-side config is sshd_config, please try that. (It's also called Ciphers there.)â Ulrich Schwarz
Dec 30 '16 at 10:42
Yeah I know but when I grep for ciphers I found them at ssh_config so I did changes there. As production server I am not doing anything I am not sure
â rÃÂÃÂdÃÂÃÂ
Dec 30 '16 at 10:46
Yeah I know but when I grep for ciphers I found them at ssh_config so I did changes there. As production server I am not doing anything I am not sure
â rÃÂÃÂdÃÂÃÂ
Dec 30 '16 at 10:46
Note that the defaults may differ between distributions.
â Jonas Schäfer
Dec 30 '16 at 13:33
Note that the defaults may differ between distributions.
â Jonas Schäfer
Dec 30 '16 at 13:33
add a comment |Â
up vote
22
down vote
To disable RC4 and use secure ciphers on SSH server, hard-code the following in /etc/ssh/sshd_config
ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
OR if you prefer not to dictate ciphers but merely want to strip out insecure ciphers, run this on the command line instead (in sudo mode):
sshd -T | grep ciphers | sed -e "s/(3des-cbc|aes128-cbc|aes192-cbc|aes256-cbc|arcfour|arcfour128|arcfour256|blowfish-cbc|cast128-cbc|rijndael-cbc@lysator.liu.se),?//g" >> /etc/ssh/sshd_config
You can check ciphers currently used by your server with:
sudo sshd -T |grep ciphers
Make sure your ssh client can use these ciphers, run ssh -Q cipher to see the list.
You can also instruct your SSH client to negotiate only secure ciphers with remote servers. In /etc/ssh/ssh_config set:
Host *
ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
Above snippets come from here
To test your server's settings you can use ssh-audit
add a comment |Â
up vote
22
down vote
To disable RC4 and use secure ciphers on SSH server, hard-code the following in /etc/ssh/sshd_config
ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
OR if you prefer not to dictate ciphers but merely want to strip out insecure ciphers, run this on the command line instead (in sudo mode):
sshd -T | grep ciphers | sed -e "s/(3des-cbc|aes128-cbc|aes192-cbc|aes256-cbc|arcfour|arcfour128|arcfour256|blowfish-cbc|cast128-cbc|rijndael-cbc@lysator.liu.se),?//g" >> /etc/ssh/sshd_config
You can check ciphers currently used by your server with:
sudo sshd -T |grep ciphers
Make sure your ssh client can use these ciphers, run ssh -Q cipher to see the list.
You can also instruct your SSH client to negotiate only secure ciphers with remote servers. In /etc/ssh/ssh_config set:
Host *
ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
Above snippets come from here
To test your server's settings you can use ssh-audit
add a comment |Â
up vote
22
down vote
up vote
22
down vote
To disable RC4 and use secure ciphers on SSH server, hard-code the following in /etc/ssh/sshd_config
ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
OR if you prefer not to dictate ciphers but merely want to strip out insecure ciphers, run this on the command line instead (in sudo mode):
sshd -T | grep ciphers | sed -e "s/(3des-cbc|aes128-cbc|aes192-cbc|aes256-cbc|arcfour|arcfour128|arcfour256|blowfish-cbc|cast128-cbc|rijndael-cbc@lysator.liu.se),?//g" >> /etc/ssh/sshd_config
You can check ciphers currently used by your server with:
sudo sshd -T |grep ciphers
Make sure your ssh client can use these ciphers, run ssh -Q cipher to see the list.
You can also instruct your SSH client to negotiate only secure ciphers with remote servers. In /etc/ssh/ssh_config set:
Host *
ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
Above snippets come from here
To test your server's settings you can use ssh-audit
To disable RC4 and use secure ciphers on SSH server, hard-code the following in /etc/ssh/sshd_config
ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
OR if you prefer not to dictate ciphers but merely want to strip out insecure ciphers, run this on the command line instead (in sudo mode):
sshd -T | grep ciphers | sed -e "s/(3des-cbc|aes128-cbc|aes192-cbc|aes256-cbc|arcfour|arcfour128|arcfour256|blowfish-cbc|cast128-cbc|rijndael-cbc@lysator.liu.se),?//g" >> /etc/ssh/sshd_config
You can check ciphers currently used by your server with:
sudo sshd -T |grep ciphers
Make sure your ssh client can use these ciphers, run ssh -Q cipher to see the list.
You can also instruct your SSH client to negotiate only secure ciphers with remote servers. In /etc/ssh/ssh_config set:
Host *
ciphers chacha20-poly1305@openssh.com,aes256-gcm@openssh.com,aes128-gcm@openssh.com,aes256-ctr,aes192-ctr,aes128-ctr
Above snippets come from here
To test your server's settings you can use ssh-audit
edited Apr 6 at 7:40
Adam Friedman
1032
1032
answered Dec 30 '16 at 12:59
savageBum
32115
32115
add a comment |Â
add a comment |Â
up vote
8
down vote
The problem with explicitly specifying a cipher list is that you must manually add new ciphers as they come out. Instead, simply list the ciphers you want to remove, prepending the list (not each individual cipher) with a '-' character. So in this case, the Ciphers line should read:
Ciphers -arcfour*
Or if you prefer:
Ciphers -arcfour,arcfour128,arcfour256
From the sshd_config man page on the Ciphers option (since OpenSSH 7.5, released 2017-03-20):
If the specified value begins with a âÂÂ+â character, then the specified ciphers will be appended to the default set instead of replacing them. If the specified value begins with a âÂÂ-â character, then the specified ciphers (including wildcards) will be removed from the default set instead of replacing them.
This also applies to the KexAlgorithms and MACs options.
add a comment |Â
up vote
8
down vote
The problem with explicitly specifying a cipher list is that you must manually add new ciphers as they come out. Instead, simply list the ciphers you want to remove, prepending the list (not each individual cipher) with a '-' character. So in this case, the Ciphers line should read:
Ciphers -arcfour*
Or if you prefer:
Ciphers -arcfour,arcfour128,arcfour256
From the sshd_config man page on the Ciphers option (since OpenSSH 7.5, released 2017-03-20):
If the specified value begins with a âÂÂ+â character, then the specified ciphers will be appended to the default set instead of replacing them. If the specified value begins with a âÂÂ-â character, then the specified ciphers (including wildcards) will be removed from the default set instead of replacing them.
This also applies to the KexAlgorithms and MACs options.
add a comment |Â
up vote
8
down vote
up vote
8
down vote
The problem with explicitly specifying a cipher list is that you must manually add new ciphers as they come out. Instead, simply list the ciphers you want to remove, prepending the list (not each individual cipher) with a '-' character. So in this case, the Ciphers line should read:
Ciphers -arcfour*
Or if you prefer:
Ciphers -arcfour,arcfour128,arcfour256
From the sshd_config man page on the Ciphers option (since OpenSSH 7.5, released 2017-03-20):
If the specified value begins with a âÂÂ+â character, then the specified ciphers will be appended to the default set instead of replacing them. If the specified value begins with a âÂÂ-â character, then the specified ciphers (including wildcards) will be removed from the default set instead of replacing them.
This also applies to the KexAlgorithms and MACs options.
The problem with explicitly specifying a cipher list is that you must manually add new ciphers as they come out. Instead, simply list the ciphers you want to remove, prepending the list (not each individual cipher) with a '-' character. So in this case, the Ciphers line should read:
Ciphers -arcfour*
Or if you prefer:
Ciphers -arcfour,arcfour128,arcfour256
From the sshd_config man page on the Ciphers option (since OpenSSH 7.5, released 2017-03-20):
If the specified value begins with a âÂÂ+â character, then the specified ciphers will be appended to the default set instead of replacing them. If the specified value begins with a âÂÂ-â character, then the specified ciphers (including wildcards) will be removed from the default set instead of replacing them.
This also applies to the KexAlgorithms and MACs options.
edited Dec 12 '17 at 14:26
answered Dec 11 '17 at 17:38
Spacedog
13612
13612
add a comment |Â
add a comment |Â
up vote
0
down vote
enable/disable cipher need to add/remove in file /etc/ssh/sshd_config
ssh -Q cipher from the client will tell you which schemes support
ssh localhost -c arcfour check arcfour cipher enable or not on the server
ssh localhost -c arcfour128 check arcfour128 cipher enable or not on the server
New contributor
Kumar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
0
down vote
enable/disable cipher need to add/remove in file /etc/ssh/sshd_config
ssh -Q cipher from the client will tell you which schemes support
ssh localhost -c arcfour check arcfour cipher enable or not on the server
ssh localhost -c arcfour128 check arcfour128 cipher enable or not on the server
New contributor
Kumar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
0
down vote
up vote
0
down vote
enable/disable cipher need to add/remove in file /etc/ssh/sshd_config
ssh -Q cipher from the client will tell you which schemes support
ssh localhost -c arcfour check arcfour cipher enable or not on the server
ssh localhost -c arcfour128 check arcfour128 cipher enable or not on the server
New contributor
Kumar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
enable/disable cipher need to add/remove in file /etc/ssh/sshd_config
ssh -Q cipher from the client will tell you which schemes support
ssh localhost -c arcfour check arcfour cipher enable or not on the server
ssh localhost -c arcfour128 check arcfour128 cipher enable or not on the server
New contributor
Kumar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 11 hours ago
Goro
7,94153877
7,94153877
New contributor
Kumar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 11 hours ago
Kumar
1
1
New contributor
Kumar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Kumar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Kumar is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f333728%2fssh-how-to-disable-weak-ciphers%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password