From 0af7b803bcac12b71603a8c2e7d9f3f7e2c8a307 Mon Sep 17 00:00:00 2001 From: Paul Date: Sat, 26 Feb 2022 23:48:24 +0100 Subject: [PATCH] Add section on SSH agent forwarding to FAQ (#360) --- FAQ.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/FAQ.md b/FAQ.md index a0f62e3..b92ea53 100644 --- a/FAQ.md +++ b/FAQ.md @@ -28,6 +28,10 @@ Please run `ssh -Tv git@github.com` in your terminal and paste the output in a [ You can create a `mykey.pub` (where `mykey` is the name of your key) in your `~/.ssh/` directory with the contents of your public key, and specify that you want to use that key in your `~/.ssh/config`. [This ServerFault answer](https://serverfault.com/a/295771) has more details on setting that up +### Can I use Secretive for SSH Agent Forwarding? + +Yes, you can! Once you've set up Secretive, just add `ForwardAgent yes` to the hosts you want to forward to in your SSH config file. Afterwards, any use of one of your SSH keys on the remote host must be authenticated through Secretive. + ### Why should I trust you? You shouldn't, for a piece of software like this. Secretive, by design, has an auditable build process. Each build has a fully auditable build log, showing the source it was built from and a SHA of the build product. You can check the SHA of the zip you download against the SHA output in the build log (which is linked in the About window).