It may be worth noting that if using the ssh configuration file, you may need to do this a slightly different way.
Due to strict permissions requirements of the .ssh/config, it requires it be only read/write on that file. Thus it cannot exist on the windows file system. A way around this is to simply use symlinks to each individual key file and known hosts, and let config reside on the linux side.
ln -s /mnt/c/Users/YourName/.ssh/id_rsa.pub ~/.ssh/id_rsa.pub
ln -s /mnt/c/Users/YourName/.ssh/id_rsa ~/.ssh/id_rsa
ln -s /mnt/c/Users/YourName/.ssh/known_hosts ~/.ssh/known_hosts
And then leaving the .ssh/config file as-is, not symlinked on the linux side, with permissions 600, allows for usage of the .ssh config file. Thus, you can have quick alias names in there such as:
And can easily connect with:
If you symlink the entire .ssh folder, and have a config file in there, windows takes over the ACL and you can no longer specify a 600 permission. Thus, trying to connect via the alias will result in a failure due to incorrect permissions. This is what wound up working for me anyhow. Hopefully it helps someone else out setting this up!