Merge pull request #4398 from corob-msft/docs/corob/dd1331923

Address DevDiv bug 1331923

Author: BCS2022

docs/linux/set-up-fips-compliant-secure-remote-linux-development.md

@@ -1,7 +1,7 @@
 ---
 title: "Set up FIPS-compliant secure remote Linux development"
 description: "How to set up a FIPS-compliant cryptographic connection between Visual Studio and a Linux machine for remote development."
-ms.date: "01/17/2020"
+ms.date: 07/06/2022
 ---
 # Set up FIPS-compliant secure remote Linux development
 
@@ -32,13 +32,13 @@ The examples in this article use Ubuntu 18.04 LTS with OpenSSH server version 7.
    sudo service ssh start
    ```
 
-1. If you’d like the ssh server to start automatically when the system boots, enable it using systemctl:
+1. If you'd like the `ssh` server to start automatically when the system boots, enable it using `systemctl`:
 
    ```bash
    sudo systemctl enable ssh
    ```
 
-1. Open */etc/ssh/sshd_config* as root. Edit (or add, if they don’t exist) the following lines:
+1. Open *`/etc/ssh/sshd_config`* as root. Edit (or add, if they don't exist) the following lines:
 
    ```config
    Ciphers aes256-cbc,aes192-cbc,aes128-cbc,3des-cbc
@@ -48,27 +48,27 @@ The examples in this article use Ubuntu 18.04 LTS with OpenSSH server version 7.
    ```
 
    > [!NOTE]
-   > ssh-rsa is the only FIPS compliant host key algorithm VS supports. The aes\*-ctr algorithms are also FIPS compliant, but the implementation in Visual Studio isn't approved. The ecdh-\* key exchange algorithms are FIPS compliant, but Visual Studio doesn't support them.
+   > `ssh-rsa` is the only FIPS compliant host key algorithm VS supports. The `aes*-ctr` algorithms are also FIPS compliant, but the implementation in Visual Studio isn't approved. The `ecdh-*` key exchange algorithms are FIPS compliant, but Visual Studio doesn't support them.
 
-   You're not limited to these options. You can configure ssh to use additional ciphers, host key algorithms, and so on. Some other relevant security options you may want to consider are `PermitRootLogin`, `PasswordAuthentication`, and `PermitEmptyPasswords`. For more information, see the man page for sshd_config or the article [SSH Server Configuration](https://www.ssh.com/ssh/sshd_config).
+   You're not limited to these options. You can configure `ssh` to use other ciphers, host key algorithms, and so on. Some other relevant security options you may want to consider are `PermitRootLogin`, `PasswordAuthentication`, and `PermitEmptyPasswords`. For more information, see the `man` page for `sshd_config` or the article [SSH Server Configuration](https://www.ssh.com/ssh/sshd_config).
 
-1. After saving and closing sshd_config, restart the ssh server to apply the new configuration:
+1. After saving and closing `sshd_config`, restart the ssh server to apply the new configuration:
 
    ```bash
    sudo service ssh restart
    ```
 
-Next, you'll create an RSA key pair on your Windows computer. Then you'll copy the public key to the remote Linux system for use by ssh.
+Next, you'll create an RSA key pair on your Windows computer. Then you'll copy the public key to the remote Linux system for use by `ssh`.
 
 ### To create and use an RSA key file
 
 1. On the Windows machine, generate a public/private RSA key pair by using this command:
 
    ```cmd
-   ssh-keygen -t rsa -b 4096
+   ssh-keygen -t rsa -b 4096 -m PEM
    ```
 
-   The command creates a public key and a private key. By default, the keys are saved to *%USERPROFILE%\\.ssh\\id_rsa* and *%USERPROFILE%\\.ssh\\id_rsa.pub*. (In Powershell, use `$env:USERPROFILE` instead of the cmd macro `%USERPROFILE%`) If you change the key name, use the changed name in the steps that follow.  We recommend you use a passphrase for increased security.
+   The command creates a public key and a private key. By default, the keys are saved to *`%USERPROFILE%\.ssh\id_rsa`* and *`%USERPROFILE%\\.ssh\\id_rsa.pub`*. (In PowerShell, use `$env:USERPROFILE` instead of the cmd macro `%USERPROFILE%`) If you change the key name, use the changed name in the steps that follow. We recommend you use a passphrase for increased security.
 
 1. From Windows, copy the public key to the Linux machine:
 
@@ -83,13 +83,13 @@ Next, you'll create an RSA key pair on your Windows computer. Then you'll copy t
    chmod 600 ~/.ssh/authorized_keys
    ```
 
-1. Now, you can test to see if the new key works in ssh. Use it to sign in from Windows:
+1. Now, you can test to see if the new key works in `ssh`. Use it to sign in from Windows:
 
     ```cmd
     ssh -i %USERPROFILE%\.ssh\id_rsa user@hostname
     ```
 
-You've successfully set up ssh, created and deployed encryption keys, and tested your connection. Now you're ready to set up the Visual Studio connection.
+You've successfully set up `ssh`, created and deployed encryption keys, and tested your connection. Now you're ready to set up the Visual Studio connection.
 
 ## Connect to the remote system in Visual Studio
 
@@ -107,14 +107,14 @@ You've successfully set up ssh, created and deployed encryption keys, and tested
 
 1. In the **Connect to Remote System** dialog, enter the connection details of your remote machine.
 
-   | Entry | Description
-   | ----- | ---
-   | **Host Name**           | Name or IP address of your target device
-   | **Port**                | Port that the SSH service is running on, typically 22
-   | **User name**           | User to authenticate as
-   | **Authentication type** | Choose Private Key for a FIPS-compliant connection
-   | **Private key file**    | Private key file created for ssh connection
-   | **Passphrase**          | Passphrase used with private key selected above
+   | Entry | Description |
+   |--|--|
+   | **Host Name**           | Name or IP address of your target device |
+   | **Port**                | Port that the SSH service is running on, typically 22 |
+   | **User name**           | User to authenticate as |
+   | **Authentication type** | Choose **Private Key** for a FIPS-compliant connection |
+   | **Private key file**    | Private key file created for ssh connection |
+   | **Passphrase**          | Passphrase used with private key selected above |
 
    Change the authentication type to **Private Key**. Enter the path to your private key in the **Private key file** field. You can use the **Browse** button to navigate to your private key file instead. Then, enter the passphrase used to encrypt your private key file in the **Passphrase** field.
 
@@ -130,13 +130,13 @@ You've successfully set up ssh, created and deployed encryption keys, and tested
 
 ## Command-line utility for the Connection Manager  
 
-**Visual Studio 2019 version 16.5 or later**: ConnectionManager.exe is a command-line utility to manage remote development connections outside of Visual Studio. It's useful for tasks such as provisioning a new development machine. Or, you can use it to set up Visual Studio for continuous integration. For examples and a complete reference to the ConnectionManager command, see [ConnectionManager reference](connectionmanager-reference.md).  
+**Visual Studio 2019 version 16.5 or later**: `ConnectionManager.exe` is a command-line utility to manage remote development connections outside of Visual Studio. It's useful for tasks such as provisioning a new development machine. Or, you can use it to set up Visual Studio for continuous integration. For examples and a complete reference to the ConnectionManager command, see [ConnectionManager reference](connectionmanager-reference.md).  
 
 ## Optional: Enable or disable FIPS mode
 
 It's possible to enable FIPS mode globally in Windows.
 
-1. To enable FIPS mode, press **Windows+R** to open the Run dialog, and then run gpedit.msc.
+1. To enable FIPS mode, press **Windows+R** to open the **Run** dialog, and then run `gpedit.msc`.
 
 1. Expand **Local Computer Policy > Computer Configuration > Windows Settings > Security Settings > Local Policies** and select **Security Options**.