Score:0

ssh-keyscan Fails to Retrieve Keys from non-FIPS Server

ng flag

We've recently made our client machine FIPS-compliant. But the server we collect keys from using ssh-keyscan is still non-compliant, and may remain so for some time. Running ssh-keyscan fails to return any keys. On a simulated system we get this same behavior, but switching the server to FIPS-compliant makes it work.

How can we make this work between a FIPS-compliant client and a non-FIPS-compliant server, or how can we accomplish the same thing by some other method? We could provision the client manually based on server settings, transferred to client:ssh_known_hosts, but this seems like a bad approach.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.