Run:
/tmp $ trezor-agent [email protected] -v > hostname.pub
2015-09-02 15:03:18,929 INFO getting "ssh://[email protected]" public key from Trezor...
2015-09-02 15:03:23,342 INFO disconnected from Trezor
/tmp $ cat hostname.pub
ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBGSevcDwmT+QaZPUEWUUjTeZRBICChxMKuJ7dRpBSF8+qt+8S1GBK5Zj8Xicc8SHG/SE/EXKUL2UU3kcUzE7ADQ= ssh://[email protected]
Append hostname.pub
contents to /home/user/.ssh/authorized_keys
configuration file at ssh.hostname.com
, so the remote server
would allow you to login using the corresponding private key signature.
Run:
/tmp $ trezor-agent [email protected] -v -c
2015-09-02 15:09:39,782 INFO getting "ssh://[email protected]" public key from Trezor...
2015-09-02 15:09:44,430 INFO please confirm user "roman" login to "ssh://[email protected]" using Trezor...
2015-09-02 15:09:46,152 INFO signature status: OK
Linux lmde 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u3 (2015-08-04) x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Tue Sep 1 15:57:05 2015 from localhost
~ $
Make sure to confirm SSH signature on the Trezor device when requested.
Use your SSH public key to access your remote repository (e.g. GitHub):
$ trezor-agent -v -e ed25519 [email protected] | xclip
Use the following Bash alias for convinient Git operations:
$ alias git_hub='trezor-agent -v -e ed25519 [email protected] -- git'
Replace git
with git_hub
for remote operations:
$ git_hub push origin master
The same works for Mercurial (e.g. on BitBucket):
$ trezor-agent -v -e ed25519 [email protected] -- hg push
If SSH connection fails to work, please open an issue
with a verbose log attached (by running trezor-agent -vv
) .
Note that your local SSH configuration may ignore trezor-agent
, if it has IdentitiesOnly
option set to yes
.
IdentitiesOnly
Specifies that ssh(1) should only use the authentication identity files configured in
the ssh_config files, even if ssh-agent(1) or a PKCS11Provider offers more identities.
The argument to this keyword must be “yes” or “no”.
This option is intended for situations where ssh-agent offers many different identities.
The default is “no”.
If you are failing to connect, try running:
$ trezor-agent -vv user@host -- ssh -vv -oIdentitiesOnly=no user@host