Edit (or add, if they don't exist) the following lines: Ciphers aes256-cbc,aes192-cbc,aes128-cbc,3des-cbc If you'd like the ssh server to start automatically when the system boots, enable it using systemctl: sudo systemctl enable ssh On the Linux system, install and start the OpenSSH server: sudo apt install openssh-server To set up the SSH server on the remote system However, the instructions should be the same for any distro using a moderately recent version of OpenSSH. The examples in this article use Ubuntu 18.04 LTS with OpenSSH server version 7.6. For FIPS-140-2 compliance, Visual Studio only supports RSA keys. Some preparation is required to use a FIPS-compliant, cryptographically secure ssh connection between Visual Studio and your remote Linux system. This article is the FIPS-compliant version of the connection instructions in Connect to your remote Linux computer.

This guide is applicable when you build CMake or MSBuild Linux projects in Visual Studio.

Here's how to set up a secure, FIPS-compliant connection between Visual Studio and your remote Linux system. In Visual Studio 2019 version 16.5 and later, you can use a secure, FIPS-compliant cryptographic connection to your Linux system for remote development. Windows has validated support for FIPS-compliant cryptographic modules. Implementations of the standard are validated by NIST. government standard for cryptographic modules. Summary: if you do not target some sort of conformance to FIPS 140-2, use the normal OpenSSL.Federal Information Processing Standard (FIPS) Publication 140-2 is a U.S. Therefore, it can be argued that the plain OpenSSL is in fact more secure than the FIPS module, since it is fixed much more quickly when holes are uncovered. The second point, in particular, implies that if a bug is found in 'normal OpenSSL', and a bugfix is published, then that bugfix is not immediately imported into the FIPS module, because that would void its FIPSness. If you modify the slightest character in the source code, you are no longer covered by the FIPS validation. The FIPS module is validated only insofar as you use it absolutely unchanged. (For functionalities which the plain OpenSSL offers but not the FIPS module, anything goes). For the same functionalities, the plain OpenSSL should be no less secure than the FIPS module. Both versions share a lot of code the FIPS module is actually a subset of the normal library version. In practice, the OpenSSL developers applied the same development methodologies for both the FIPS module, and 'plain' OpenSSL. Validation cannot prove that there is no bug or vulnerability, but it can show that the developers applied proper methodologies which, hopefully, should avoid bugs and make the software conform to a specific set of target properties. The intent of FIPS 140-2 validation is to show, basically, that some level of 'seriousness' was applied during the development. It has achieved the 'overall level: 1' (see the validation certificate).

That module has gone through the long and painful administrative process of obtaining a FIPS 140-2 validation. The OpenSSL FIPS Object Module is a specific subset of OpenSSL, API-compatible with OpenSSL, and provided as source code. For the relationships between OpenSSL and FIPS 140-2, read this documentation.

Openssh fips 140 2