infoblox_nios:certificates
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| infoblox_nios:certificates [2023/06/07 08:49] – [Certificates] bstafford | infoblox_nios:certificates [2025/05/19 09:56] (current) – [WARNING] bstafford | ||
|---|---|---|---|
| Line 6: | Line 6: | ||
| Infoblox has articles on hardening SSL/TLS and SSH ciphers [[https:// | Infoblox has articles on hardening SSL/TLS and SSH ciphers [[https:// | ||
| - | The NIOS 8.5 admin guide page is [[https:// | + | The NIOS 9.0 admin guide page is [[https:// |
| - | + | The set command | |
| - | The NIOS 9.0 admin guide page is [[https:// | + | |
| For Reporting and Analytics to function properly, ensure that you DO NOT create a SHA-256 4096 SSL key for the HTTPS certificate in your Grid because Java does not support SHA-256 with a 4096 key size. | For Reporting and Analytics to function properly, ensure that you DO NOT create a SHA-256 4096 SSL key for the HTTPS certificate in your Grid because Java does not support SHA-256 with a 4096 key size. | ||
| + | |||
| + | * Certificate error when connecting to NIOS GUI. [[https:// | ||
| + | * Creating Self-Signed SSL Certificates [[https:// | ||
| + | * Importing SSL Certificates into NIOS [[https:// | ||
| + | |||
| + | ===== Terrapin Attack ===== | ||
| + | [[https:// | ||
| ===== Web UI Certificates ===== | ===== Web UI Certificates ===== | ||
| You can upload HTTPS certificates in the GUI. Remember to create certificates for the GM and also create certificates for all GMC appliances. | You can upload HTTPS certificates in the GUI. Remember to create certificates for the GM and also create certificates for all GMC appliances. | ||
| + | You can use the '' | ||
| + | |||
| + | This works at least on NIOS 8.6+. | ||
| ===== List of Needed Ciphers ===== | ===== List of Needed Ciphers ===== | ||
| Line 21: | Line 30: | ||
| * TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 | * TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 | ||
| + | REMEMBER: If you have the reporting server, then as of NIOS 9.0.4 you will need to NOT disable TLS 1.2 because Splunk (which powers the reporting server) doesn' | ||
| ===== WARNING ===== | ===== WARNING ===== | ||
| Line 27: | Line 37: | ||
| * TLS_RSA_WITH_AES_256_GCM_SHA384 | * TLS_RSA_WITH_AES_256_GCM_SHA384 | ||
| - | However, I noticed a few days later that I could not access the Reporting tab and just go the following error message. | + | However, I noticed a few days later that I could not access the Reporting tab (Splunk) |
| < | < | ||
| Refresh the status | Refresh the status | ||
| Line 88: | Line 98: | ||
| Show ciphers | Show ciphers | ||
| < | < | ||
| - | 1. TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 | + | 1. TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 |
| - | 2. TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 | + | 2. TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 |
| - | 3. TLS_DHE_RSA_WITH_AES_128_CBC_SHA | + | 3. TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA |
| - | 4. TLS_DHE_RSA_WITH_AES_256_CBC_SHA | + | 4. TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA |
| - | 5. TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 | + | 5. TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 |
| - | 6. TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 | + | 6. TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 |
| - | 7. TLS_RSA_WITH_AES_128_GCM_SHA256 | + | 7. TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 |
| - | 8. TLS_RSA_WITH_AES_128_CBC_SHA | + | 8. TLS_DHE_RSA_WITH_AES_128_CBC_SHA |
| - | 9. TLS_RSA_WITH_AES_128_CBC_SHA256 | + | 9. TLS_DHE_RSA_WITH_AES_256_CBC_SHA |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | 15. TLS_RSA_WITH_3DES_EDE_CBC_SHA |
| - | | + | 16. TLS_RSA_WITH_AES_256_GCM_SHA384 |
| - | | + | 17. TLS_RSA_WITH_AES_256_CBC_SHA |
| - | | + | 18. TLS_RSA_WITH_AES_256_CBC_SHA256 |
| - | | + | 19. TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 enabled |
| - | | + | 20. TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 enabled |
| - | | + | 21. TLS_AES_256_GCM_SHA384 |
| - | | + | 22. TLS_CHACHA20_POLY1305_SHA256 |
| - | Say you want to disable RC4. It is item #14 so you disable #14 | + | 23. TLS_AES_128_GCM_SHA256 |
| - | < | + | 24. TLS_AES_128_CCM_8_SHA256 |
| + | 25. TLS_AES_128_CCM_SHA256 | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | Say you want to disable RC4. It is item #25 so you disable #25 | ||
| + | < | ||
| < | < | ||
| - | 1. TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 | + | 1. TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 |
| - | 2. TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 | + | 2. TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 |
| - | 3. TLS_DHE_RSA_WITH_AES_128_CBC_SHA | + | 3. TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA |
| - | 4. TLS_DHE_RSA_WITH_AES_256_CBC_SHA | + | 4. TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA |
| - | 5. TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 | + | 5. TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 |
| - | 6. TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 | + | 6. TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 |
| - | 7. TLS_RSA_WITH_AES_128_GCM_SHA256 | + | 7. TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 |
| - | 8. TLS_RSA_WITH_AES_128_CBC_SHA | + | 8. TLS_DHE_RSA_WITH_AES_128_CBC_SHA |
| - | 9. TLS_RSA_WITH_AES_128_CBC_SHA256 | + | 9. TLS_DHE_RSA_WITH_AES_256_CBC_SHA |
| - | | + | |
| - | | + | |
| - | | + | |
| - | 13. TLS_RSA_WITH_AES_256_CBC_SHA256 | + | 13. TLS_RSA_WITH_AES_128_CBC_SHA |
| - | | + | 14. TLS_RSA_WITH_AES_128_CBC_SHA256 |
| - | | + | 15. TLS_RSA_WITH_3DES_EDE_CBC_SHA |
| - | | + | 16. TLS_RSA_WITH_AES_256_GCM_SHA384 |
| - | | + | 17. TLS_RSA_WITH_AES_256_CBC_SHA |
| - | | + | 18. TLS_RSA_WITH_AES_256_CBC_SHA256 |
| - | | + | 19. TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 enabled |
| - | | + | 20. TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 enabled |
| - | | + | 21. TLS_AES_256_GCM_SHA384 |
| - | | + | 22. TLS_CHACHA20_POLY1305_SHA256 |
| + | 23. TLS_AES_128_GCM_SHA256 | ||
| + | 24. TLS_AES_128_CCM_8_SHA256 | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| Now suppose that for some reason you needed to re-enable the use of RC4. You could do this as follows: | Now suppose that for some reason you needed to re-enable the use of RC4. You could do this as follows: | ||
| < | < | ||
| Line 141: | Line 175: | ||
| TLS_RSA_WITH_RC4_128_SHA was enabled | TLS_RSA_WITH_RC4_128_SHA was enabled | ||
| The following services need to be restarted manually: GUI</ | The following services need to be restarted manually: GUI</ | ||
| + | |||
| + | The following is from NIOS 9.0.4 which introduced five TLS 1.3 ciphers | ||
| < | < | ||
| - | 1. TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 | + | 1. TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 |
| - | 2. TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 | + | 2. TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 |
| - | 3. TLS_DHE_RSA_WITH_AES_128_CBC_SHA | + | 3. TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA |
| - | 4. TLS_DHE_RSA_WITH_AES_256_CBC_SHA | + | 4. TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA |
| - | 5. TLS_DHE_RSA_WITH_AES_128_CBC_SHA256 | + | 5. TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256 |
| - | 6. TLS_DHE_RSA_WITH_AES_256_CBC_SHA256 | + | 6. TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 |
| - | 7. TLS_RSA_WITH_AES_128_GCM_SHA256 | + | 7. TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 |
| - | 8. TLS_RSA_WITH_AES_128_CBC_SHA | + | 8. TLS_DHE_RSA_WITH_AES_128_CBC_SHA |
| - | 9. TLS_RSA_WITH_AES_128_CBC_SHA256 | + | 9. TLS_DHE_RSA_WITH_AES_256_CBC_SHA |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | |
| - | | + | 15. TLS_RSA_WITH_3DES_EDE_CBC_SHA |
| - | | + | 16. TLS_RSA_WITH_AES_256_GCM_SHA384 |
| - | | + | 17. TLS_RSA_WITH_AES_256_CBC_SHA |
| - | | + | 18. TLS_RSA_WITH_AES_256_CBC_SHA256 |
| - | | + | 19. TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 enabled |
| - | | + | 20. TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 enabled |
| - | | + | 21. TLS_AES_256_GCM_SHA384 |
| - | | + | 22. TLS_CHACHA20_POLY1305_SHA256 |
| + | 23. TLS_AES_128_GCM_SHA256 | ||
| + | 24. TLS_AES_128_CCM_8_SHA256 | ||
| + | 25. TLS_AES_128_CCM_SHA256 | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
| + | | ||
infoblox_nios/certificates.1686127782.txt.gz · Last modified: by bstafford
