Update connect-to-your-remote-linux-computer.md

Removing references to RSA/DSA keys due to security concerns

Author: sinemakinci1

docs/linux/connect-to-your-remote-linux-computer.md

@@ -82,7 +82,10 @@ If `ssh` isn't already set up and running on your Linux system, follow these ste
    | **Private key file** | Private key file created for ssh connection |
    | **Passphrase** | Passphrase used with private key selected above |
 
-   You can use either a password or a key file and passphrase for authentication. For many development scenarios, password authentication is sufficient, but key files are more secure. If you already have a key pair, it's possible to reuse it. Currently Visual Studio only supports RSA and DSA keys for remote connections.
+   You can use either a password or a key file and passphrase for authentication. For many development scenarios, password authentication is sufficient, but key files are more secure. If you already have a key pair, it's possible to reuse it.
+
+   Versions of Visual Studio before 17.10 support EC, RSA and DSA keys for remote connections. Because of security concerns, RSA and DSA keys are no longer supported in VS 17.10 and later. Only EC keys are currently supported. To create a key pair compatible with the connection manager use the command:
+   `ssh-keygen -m pem -t ecdsa -f <key-name>`
 
    > [!NOTE]
    > If using `ssh-keygen` to create the private key, you must specify the switch `-m pem`, or the key will not be accepted by Visual Studio. If your private key begins with `-----BEGIN OPENSSH PRIVATE KEY-----`, you must convert it with `ssh-keygen -p -f <FILE> -m pem`. 
@@ -122,7 +125,7 @@ Starting in Visual Studio version 16.9, support for older, insecure SSH algorith
 | Encryption | `aes128-cbc`</br>`aes128-ctr`</br>`aes192-cbc`</br>`aes192-ctr`</br>`aes256-cbc`</br>`aes256-ctr` |
 | HMAC | `hmac-sha2-256`</br>`hmac-sha2-512` |
 | Key exchange | `diffie-hellman-group14-sha256`</br>`diffie-hellman-group16-sha512`</br>`diffie-hellman-group-exchange-sha256`</br>`ecdh-sha2-nistp256`</br>`ecdh-sha2-nistp384`</br>`ecdh-sha2-nistp521` |
-| Host key | `ecdsa-sha2-nistp256`</br>`ecdsa-sha2-nistp384`</br>`ecdsa-sha2-nistp521`</br>`ssh-dss`</br>`ssh-rsa` |
+| Host key | `ecdsa-sha2-nistp256`</br>`ecdsa-sha2-nistp384`</br>`ecdsa-sha2-nistp521` |
 
 ### Configure the SSH server
 
@@ -178,7 +181,7 @@ For example: `KexAlgorithms ecdh-sha2-nistp256,ecdh-sha2-nistp384`
 #### Host key example
 
 Add: `HostKeyAlgorithms <algorithms to enable>`  
-For example: `HostKeyAlgorithms ssh-dss,ssh-rsa`
+For example: `HostKeyAlgorithms ecdsa-sha2-nistp256,ecdsa-sha2-nistp384`
 
 ## Logging for remote connections