Add release notes for dynamic forwarding and tmp lockfiles

remote-release-notes/v1_37.md

@@ -58,5 +58,14 @@ If you haven't set up your SSH agent, see [our documentation about this](https:/
 
 If you lose your internet connection during a remote session, VS Code has to reconnect to the host. If you had any terminals open during reconnection, they will have a stale value for the `$SSH_AUTH_SOCK` environment variable and won't be able to access your local SSH agent. You can refresh the value of this variable by running this command: ```SSH_AUTH_SOCK=`cat $SSH_AUTH_SOCK_LOCATION` ```. New terminals opened after reconnection should already be set up correctly. We are working on improving this!
 
+
 ### Improved Password Authentication
 
+If you are using password-based authentication for your SSH remote, then currently you have to enter your password twice for each window, each reconnection, and again if you want to forward a port. We are experimenting with a new way to set up the SSH connection that will only require one password when the window opens, and no extra password entry to forward a port. To try it out, set `"remote.SSH.enableDynamicForwarding": true` and report any issues that you see. This mode is also a little faster to connect, even if you aren't using password-based auth.
+
+And we still recommend [setting up key-based authentication](https://code.visualstudio.com/docs/remote/troubleshooting#_configuring-key-based-authentication) for the best experience.
+
+
+### Hosts Using Distributed Filesystems
+
+Some users have reported issues with installing the remote server on hosts that mount a home directory from a distributed filesystem like NFS or AFS. To work around this, we've added a setting to keep the installation lockfiles in `/tmp` instead of in the server install directory. Set `"remote.SSH.lockfilesInTmp": true` to use this.