A setting that doesnt add much security value it should simply be disabled. This setting specifies whether SSH should perform a lookup and check that a resolved remote hostname maps to the same IP address.In high concurrency environments having too low of a value causes SSH connection errors. This setting determines the maximum number of unauthenticated SSH connection attempts.This setting determines the maximum number of open shell sessions allowed per network connection.
MAC SSH SERVER CONFIG CODE
This setting specifies the allowed message authentication code (Mac) algorithms.These are the recommended secure ciphers. This setting specifies the allowed ciphers for SSH.The algorithms set here are among the most secure particularly diffie-hellman-SHA1. This setting specifies the Key Exchange algorithms SSH can use.
MAC SSH SERVER CONFIG MAC
On some systems such as El Capitan on Mac this setting is required for SSH authentication to work on Aspera servers. This setting is appropriate if you have users that will not be using public key authentication and need to authenticate themselves with passwords.Protocol 1 is a less secure SSH protocol therefore protocol 2 should be used.Port 33001 is Asperas standard port that all Aspera products know to look for. This is a best practice because port 22 is a well known SSH port and therefore a target for attacks. Leaving Port 22 commented and adding Port 33001 disables port 22 for the use of SSH and enables port 33001.
The above values are best practices to use for the following reasons (note that not all these values are necessarily appropriate for your system-if you are unsure contact Aspera Support):
#Port 22Port 33001Protocol 2PasswordAuthentication yesKexAlgorithms ecdh-sha2-nistp521ecdh-sha2-nistp384ecdh-sha2-nistp256diffie-hellman-group-exchange-sha256diffie-hellman-group-exchange-sha1Ĭiphers aes128-ctraes192-ctraes256-ctraes128-cbcaes192-cbcaes256-cbcMacs hmac-sha1hmac-sha2-256hmac-sha2-512MaxSessions 100MaxStartups 100UseDNS NoX11Forwarding No
0 kommentar(er)
