Skip to content
This repository has been archived by the owner on Jul 19, 2018. It is now read-only.

Commit

Permalink
update documentation to mention confirmation stuff
Browse files Browse the repository at this point in the history
Thanks: Christian Amsüss <chrysn@fsfe.org> for requesting that feature
  • Loading branch information
tiwe-de committed Oct 25, 2013
1 parent fad26b6 commit d8b50eb
Showing 1 changed file with 13 additions and 6 deletions.
19 changes: 13 additions & 6 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,20 +13,27 @@ our solution
------------

1. create one key(pair) for each realm you connect to
2. load keys into your ssh-agent as usual
3. use ssh-agent-filter to allow only the key(s) you need
2. load keys into your `ssh-agent` as usual
3. use `ssh-agent-filter` to allow only the key(s) you need

afssh (agent filtered ssh) can wrap ssh-agent-filter and ssh for you:
`afssh` (agent filtered ssh) can wrap `ssh-agent-filter` and `ssh` for you, forwarding only the key with the comment `id_example`:

$ afssh -c id_example -- example.com
$ afssh --comment id_example -- example.com

starts an `ssh-agent-filter -c id_example`, runs `ssh -A example.com` and kills the ssh-agent-filter afterwards.
starts an `ssh-agent-filter --comment id_example`, runs `ssh -A example.com` and kills the `ssh-agent-filter` afterwards.

If you leave out the options before the `--`:

$ afssh -- example.com

it will ask you via whiptail or dialog which keys you want to have forwarded.
it will ask you via `whiptail` or `dialog` which keys you want to have forwarded.


confirmation
------------

You can use the `--*-confirmed` options (e.g.`--comment-confirmed`) to add keys for which you want to be asked on each use through the filter.
The confirmation is done in the same way as when you `ssh-add -c` a key to your `ssh-agent`, but the question will contain some additional information extracted from the sign request.


how it works
Expand Down

0 comments on commit d8b50eb

Please sign in to comment.