system security crypto
Use this command to modify protocol-specific cryptography settings for HTTPS and SMTPS (SSL/TLS) secure connections. (Other protocols use settings in system global.)
Syntax
config system security crypto
edit http
set custom-ciphers <ciphers_str>
set dh-params {1024 | 2048 | 3072 | 4096}
set ssl-versions {tls1_0 tls1_1 tls1_2 tls1_3}
set strong-crypto {enable | disable}
edit mail
set custom-ciphers <ciphers_str>
set dh-params {1024 | 2048 | 3072 | 4096}
set ssl-versions {tls1_0 tls1_1 tls1_2 tls1_3}
set strong-crypto {enable | disable}
end
|
Variable |
Description |
Default |
|
Select which ciphers FortiMail will accept in HTTPS and SMTPS secure connections from clients. To display a list of cipher options and the current selection, type: set custom-ciphers ? In the To add cipher suites to the list, type +RC4-SHA +CAMELLIA256-SHA To delete cipher suites from the list, type - before the name of each cipher, and separate multiple names with spaces, such as: -RC4-SHA -CAMELLIA256-SHA Alternatively, for FIPS-CC compliance, configure status {disable | fips-ciphers} instead. |
|
|
|
Enter the minimum size of the Diffie-Hellman prime number for secure connections such as SSH, SMTPS, and HTTPS. Larger bit sizes are slower to generate, but generally more secure. Alternatively, you can set the Diffie-Hellman bit size globally. See system global. |
2048 |
|
|
Select which SSL/TLS version(s) FortiMail will accept in secure connections:
Separate multiple versions with a space. Alternatively, you can select SSL/TLS versions globally. See system global. Note: Some old versions of web browsers, email clients (for example, Microsoft Outlook 2007 and older), MTAs only support TLS 1.0. Therefore they cannot connect to FortiMail if you enable strong-crypto {enable | disable} and/or disable TLS 1.0. |
tls1_1 tls1_2 tls1_3 |
|
|
Enable to override the global settings, and apply protocol-specific cryptography settings. Disable to use system-wide settings in system global. |
disable |
|
|
Enable to use strong encryption and only allow strong ciphers (AES-128 or better) and digest (SHA-256 or better) for HTTPS and SSH access. Old SSL/TLS versions with known vulnerabilities such as SSL 3.0 are also disabled, so this setting may partially override ssl-versions {tls1_0 tls1_1 tls1_2 tls1_3}. For additional security, you can also configure custom-ciphers <ciphers_str>. Alternatively, you can enforce strong encryption globally. See system global. Note: Old mail clients and old browser versions such as Microsoft Internet Explorer 6.0 do not support strong encryption. |
enable |