Linux - Security This forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
06-05-2006, 03:59 PM
|
#1
|
Member
Registered: Aug 2003
Location: Omaha, Nebraska
Distribution: Red Hat, Fedora, Debian
Posts: 65
Rep:
|
sshd minimum encryption
Where do I define the minimum level of encryption accepted by my sshd server?
I want clients to only be able to connect at AES. Can't I specify this on the server side?
Still new to all this.
Thanks!
|
|
|
06-05-2006, 04:27 PM
|
#2
|
Moderator
Registered: Mar 2003
Location: Scotland
Distribution: Slackware, RedHat, Debian
Posts: 12,047
Rep:
|
From "man sshd_config":
Code:
Ciphers
Specifies the ciphers allowed for protocol version 2. Multiple
ciphers must be comma-separated. The supported ciphers are
``3des-cbc'', ``aes128-cbc'', ``aes192-cbc'', ``aes256-cbc'',
``aes128-ctr'', ``aes192-ctr'', ``aes256-ctr'', ``arcfour128'',
``arcfour256'', ``arcfour'', ``blowfish-cbc'', and
``cast128-cbc''. The default is
``aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour128,
arcfour256,arcfour,aes192-cbc,aes256-cbc,aes128-ctr,
aes192-ctr,aes256-ctr''
|
|
|
06-05-2006, 11:58 PM
|
#3
|
Member
Registered: Jan 2004
Location: the abyss
Posts: 209
Rep:
|
As far as I know you cannot use the sshd server to force clients to use a certain encryption algorithm. Arguably, there is no "minimum" encryption, since all of the cyphers scrable the data in a different way. Luckily, all of the algorithms ssh (i would always use the 2nd protocol version) uses are pretty widely trusted. Blowfish is decent, and that is what most ssh connection default to (if cypher is unspecified). AES and blowfish are both considered some of the strongest encryption algorithms out there.
|
|
|
06-06-2006, 07:57 AM
|
#4
|
Member
Registered: Aug 2003
Location: Omaha, Nebraska
Distribution: Red Hat, Fedora, Debian
Posts: 65
Original Poster
Rep:
|
Perfect guys!
Thanks!
|
|
|
All times are GMT -5. The time now is 08:35 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|