Managed system host key check is enabled but the list of accepted host keys is empty

I am facing the same issue after upgrading to 25.3, but no resolution yet. Have you found a solution for this?

Hi ​@Diliphan R  The situation was handled without a well-defined or structured approach.

I created a Managed System Smart Rule to modify the attribute for systems where “SSH Key Enforcement Mode” was set to “None”, changing the setting to “Auto Accept Initial Key.”

This helped a lot of affected system, but in some systems, we had to manually revert the setting back to “None.”

Support shared the following feedback and references:

• As of now, changes to SSH Key Enforcement values have not been confirmed as a reported bug by any previous customer.

• The issue could not be reproduced in their test environment, which was recently upgraded to version 25.3 (as mentioned during the call).

They also suggested reviewing the following Knowledge Base articles:

• KB0021412: How to manually configure SSH host keys to make fingerprints consistent

• KB0017016: ERROR: SSH client: No matching key exchange algorithm found – No matching cipher found – No matching MAC algorithm found

In the meantime, we decided not to upgrade the other customers.

If you have a solid or definitive solution, I would greatly appreciate your feedback.

Hi ​@Diliphan R , did you solve this officially or are you using a workaround?