![]() In the Triggers tab, you should not have to change anything. In the General tab, click on Change User or Group… and fix the name of the Windows user that will launch WSL: Screenshot of the General tab contents in the task configuration. #Ssh proxy 24 top updateNow edit the task to update the few settings that are machine- and user-dependent. Open the Task scheduler tool from the Start menu.Ĭlick on the Import Task… action and select the XML file you created. Proceed with these fake values during the initial import. In particular, UserId and Command are wrong for your machine. WARNING: Beware that this task definition relies on machine- and user-specific properties, and that I wiped them in the file above. T16:32:19.159532 CHERRY\jmmv \Start WSL SSH true PT30S S-0-0-00-0000000000-0000000000-0000000000-0000 Password LeastPrivilege IgnoreNew true true true false false true false true true false false false PT72H 7 C:\Users\youruser\sshd.bat The instructions here are based on Debian. #Ssh proxy 24 top installInstall WSL and a Linux distribution, and choose whether you want to use version 1 or 2. Let’s start by configuring the SSH server within WSL: The majority of the configuration process is common between WSL 1 and WSL 2, so let’s do those common steps first. The goal configuration in this post is to have an SSH server on port 2022 to reach WSL and to have it readily available when the machine boots (because reboots can unfortunately happen at any time “thanks to” forced OS updates). The process is tricky though and depends on the WSL version in use, so you can take these as my lab notes set this whole ordeal up.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |