Guest

Preview Tool

Cisco Bug: CSCvs79291 - FIPS Mode - ssh_config values are not updated with ssh_config.fips

Last Modified

Jul 29, 2020

Products (1)

  • Cisco Email Security Appliance

Known Affected Releases

13.0.0-380

Description (partial)

Symptom:
i)  Specific to X90 (Hardware device): After upgrading ESA (in FIPS mode) from 11-0-0-274 to 13-0-0-380, it is expected that /etc/ssh/ssh_config should have FIPS related values as defined in /etc/ssh/ssh_config.fips. However, X90 device fails to hold/copy the values and the same scenario works as expected in VM machines.

ii) Applicable for VM & Hardware : In clustered machines setup, if we enable FIPS on one ESA it is expected that /etc/ssh/ssh_config should have FIPS related values as defined in /etc/ssh/ssh_config.fips on all the machines exist in the cluster. Currently, only the machine from where FIPS is enabled/enabled holds the expected config and changes are not reflected to other machines in the cluster. (On both Netinstall and Upgrade scenarios)

Conditions:
Condition 1:
1. Enable FIPS mode in ESA
2. Verify /etc/ssh/ssh_config holds configuration as defined in /etc/ssh/ssh_config.fips
3. Configure update server on ESA and Upgrade ESA to 13-0-0-x 
4. Post upgrade, Verify /etc/ssh/ssh_config holds configuration as defined in /etc/ssh/ssh_config.fips

Condition 2:
1. Create a cluster in one ESA and Join other machines to cluster
2. Enable FIPS on 1st machine
3. Verify /etc/ssh/ssh_config holds configuration as defined in /etc/ssh/ssh_config.fips on all machines
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.