SNS version 4.3.31 LTSB bug fixes

System

SMC - Encryption suites that can be used with an SNS firewall

Communications between an SNS firewall and its SMC administration server can now use only these encryption suites:

• TLS_AES_128_GCM_SHA256,
• TLS_CHACHA20_POLY1305_SHA256,
• TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,
• TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,
• TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256,
• TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256,
• TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,
• TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,
• TLS_EMPTY_RENEGOTIATION_INFO_SCSV.

These encryption suites have been removed:

• TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,
• TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,
• TLS_DHE_RSA_WITH_AES_128_CBC_SHA256,
• TLS_DHE_RSA_WITH_AES_256_GCM_SHA384,
• TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384,
• TLS_DHE_RSA_WITH_AES_256_CBC_SHA256.

Certificates and PKI

The firewall now correctly verifies the content of the basicConstraints extension in a certification authority's (CA) certificate.

You can configure whether to import a CA for which this extension does not have a value, by using the StrictCACheck configuration token found in the ConfigFiles > system file. When the value of this token is set to 0, this means that such CAs can be imported.