Your browser does not allow storing cookies. We recommend enabling them.

SSH

Configuring MACs

The MAC (Message Authentication Code) algorithm(s) used for data integrity verification can be selected in the sshd2_config file:

MACs                hmac-sha1,hmac-md5

The supported MAC names are the following:

hmac-md5hmac-sha2-256hmac-sha384@ssh.com
hmac-md5-96hmac-sha256-2@ssh.comhmac-sha2-512
hmac-sha1hmac-sha224@ssh.comhmac-sha512@ssh.com
hmac-sha1-96hmac-sha256@ssh.com

Special values for this option are the following:

  • Any: includes all supported MACs plus none.

  • AnyStd: includes MACs from the IETF SSH standards (hmac-md5, hmac-md5-96, hmac-sha1, hmac-sha1-96, hmac-sha2-256, hmac-sha2-512) and none.

  • none: means that no cryptographic data integrity method is used.

  • AnyMac: the same as Any but excludes none.

  • AnyStdMac: the same as AnyStd but exludes none.

The default MAC algorithms are: hmac-sha1, hmac-sha1-96, hmac-sha2-256, hmac-sha256-2@ssh.com, hmac-sha224@ssh.com, hmac-sha256@ssh.com, hmac-sha384@ssh.com, hmac-sha2-512, and hmac-sha512@ssh.com.


 

 
Highlights from the SSH.COM blog:

  • Cryptomining with the SSH protocol: what big enterprises need to know about it

    Cryptomining malware is primarily thought of as targeting desktops and laptops and is used to hijack system resources to mine cryptocurrency.
    Read more
  • SLAM the door shut on traditional privileged access management

    Did you know that something as trivial-sounding as granting access for your developers or third parties to a product development environment can throw a gorilla-sized monkey wrench into your operations and productivity?
    Read more
  • We broke the IT security perimeter

    Everyone understands the concept of a security perimeter. You only gain access if you are identified and authorized to do so.
    Read more