![]() ![]() In your WSL2, download and extract the npiperelay binary. ![]() Although it’s a Windows based tool, it’s still possible to run it from within WSL2, which makes for a convenient setup. Npiperelay allows named pipes to communicate between Linux in WSL and Windows. So the private (password protected) ssh key isnt stored in /.ssh/ided25519 like it normaly. Once again hit OK and save KeePassXC is now serving those keys to the Windows SSH agent. Im using KeepassXC to add my ssh Keys to the ssh-agent. The rest of the section should get filled out with details about your key. Now reopen the entry, then go to the SSH Agent section, under Private key, pick the file you attached earlier. You need to save so that the SSH Agent can read your key in the next step. ![]() In the advanced section, attach your public and private key, then hit OK, then save the entry. The second option requires the OpenSSH service in Windows to already be running, you will get an error message if it isn’t.Ĭreate a new entry in your database, give it some name, and in the password field, put the passphrase for your SSH key. Open up KeePassXC’s settings, and choose to Enable SSH Agent and also Use OpenSSH for Windows instead of Pageant. You can also skip the steps and go straight to the setup script Set up KeePassXC Some benefits of putting your SSH key into your KeepassXC are that you can have a strong password on the private key but don’t need to type it out each time, and that you don’t need to save your keys on disk - you can let KeePassXC manage the storage, unlocking and serving of the keys for you. KeepassXC can be used to serve SSH keys to WSL2, which is useful when remoting on to servers, or using Git over SSH. I have previously shown how to serve keys to WSL1, here I’ll be going over the method to do it for WSL2. How to use KeepassXC to serve SSH keys to WSL2 and Ubuntu ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |