1.\" $OpenBSD: ssh-add.1,v 1.87 2024/06/17 08:30:29 djm Exp $ 2.\" 3.\" Author: Tatu Ylonen <ylo@cs.hut.fi> 4.\" Copyright (c) 1995 Tatu Ylonen <ylo@cs.hut.fi>, Espoo, Finland 5.\" All rights reserved 6.\" 7.\" As far as I am concerned, the code I have written for this software 8.\" can be used freely for any purpose. Any derived versions of this 9.\" software must be clearly marked as such, and if the derived work is 10.\" incompatible with the protocol description in the RFC file, it must be 11.\" called by a name other than "ssh" or "Secure Shell". 12.\" 13.\" 14.\" Copyright (c) 1999,2000 Markus Friedl. All rights reserved. 15.\" Copyright (c) 1999 Aaron Campbell. All rights reserved. 16.\" Copyright (c) 1999 Theo de Raadt. All rights reserved. 17.\" 18.\" Redistribution and use in source and binary forms, with or without 19.\" modification, are permitted provided that the following conditions 20.\" are met: 21.\" 1. Redistributions of source code must retain the above copyright 22.\" notice, this list of conditions and the following disclaimer. 23.\" 2. Redistributions in binary form must reproduce the above copyright 24.\" notice, this list of conditions and the following disclaimer in the 25.\" documentation and/or other materials provided with the distribution. 26.\" 27.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR 28.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES 29.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. 30.\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, 31.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT 32.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, 33.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY 34.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT 35.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF 36.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. 37.\" 38.Dd $Mdocdate: June 17 2024 $ 39.Dt SSH-ADD 1 40.Os 41.Sh NAME 42.Nm ssh-add 43.Nd adds private key identities to the OpenSSH authentication agent 44.Sh SYNOPSIS 45.Nm ssh-add 46.Op Fl CcDdKkLlqvXx 47.Op Fl E Ar fingerprint_hash 48.Op Fl H Ar hostkey_file 49.Op Fl h Ar destination_constraint 50.Op Fl S Ar provider 51.Op Fl t Ar life 52.Op Ar 53.Nm ssh-add 54.Fl s Ar pkcs11 55.Op Fl Cv 56.Op Ar certificate ... 57.Nm ssh-add 58.Fl e Ar pkcs11 59.Nm ssh-add 60.Fl T 61.Ar pubkey ... 62.Sh DESCRIPTION 63.Nm 64adds private key identities to the authentication agent, 65.Xr ssh-agent 1 . 66When run without arguments, it adds the files 67.Pa ~/.ssh/id_rsa , 68.Pa ~/.ssh/id_ecdsa , 69.Pa ~/.ssh/id_ecdsa_sk , 70.Pa ~/.ssh/id_ed25519 71and 72.Pa ~/.ssh/id_ed25519_sk . 73After loading a private key, 74.Nm 75will try to load corresponding certificate information from the 76filename obtained by appending 77.Pa -cert.pub 78to the name of the private key file. 79Alternative file names can be given on the command line. 80.Pp 81If any file requires a passphrase, 82.Nm 83asks for the passphrase from the user. 84The passphrase is read from the user's tty. 85.Nm 86retries the last passphrase if multiple identity files are given. 87.Pp 88The authentication agent must be running and the 89.Ev SSH_AUTH_SOCK 90environment variable must contain the name of its socket for 91.Nm 92to work. 93.Pp 94The options are as follows: 95.Bl -tag -width Ds 96.It Fl C 97When loading keys into or deleting keys from the agent, process 98certificates only and skip plain keys. 99.It Fl c 100Indicates that added identities should be subject to confirmation before 101being used for authentication. 102Confirmation is performed by 103.Xr ssh-askpass 1 . 104Successful confirmation is signaled by a zero exit status from 105.Xr ssh-askpass 1 , 106rather than text entered into the requester. 107.It Fl D 108Deletes all identities from the agent. 109.It Fl d 110Instead of adding identities, removes identities from the agent. 111If 112.Nm 113has been run without arguments, the keys for the default identities and 114their corresponding certificates will be removed. 115Otherwise, the argument list will be interpreted as a list of paths to 116public key files to specify keys and certificates to be removed from the agent. 117If no public key is found at a given path, 118.Nm 119will append 120.Pa .pub 121and retry. 122If the argument list consists of 123.Dq - 124then 125.Nm 126will read public keys to be removed from standard input. 127.It Fl E Ar fingerprint_hash 128Specifies the hash algorithm used when displaying key fingerprints. 129Valid options are: 130.Dq md5 131and 132.Dq sha256 . 133The default is 134.Dq sha256 . 135.It Fl e Ar pkcs11 136Remove keys provided by the PKCS#11 shared library 137.Ar pkcs11 . 138.It Fl H Ar hostkey_file 139Specifies a known hosts file to look up hostkeys when using 140destination-constrained keys via the 141.Fl h 142flag. 143This option may be specified multiple times to allow multiple files to be 144searched. 145If no files are specified, 146.Nm 147will use the default 148.Xr ssh_config 5 149known hosts files: 150.Pa ~/.ssh/known_hosts , 151.Pa ~/.ssh/known_hosts2 , 152.Pa /etc/ssh/ssh_known_hosts , 153and 154.Pa /etc/ssh/ssh_known_hosts2 . 155.It Fl h Ar destination_constraint 156When adding keys, constrain them to be usable only through specific hosts or to 157specific destinations. 158.Pp 159Destination constraints of the form 160.Sq [user@]dest-hostname 161permit use of the key only from the origin host (the one running 162.Xr ssh-agent 1 ) 163to the listed destination host, with optional user name. 164.Pp 165Constraints of the form 166.Sq src-hostname>[user@]dst-hostname 167allow a key available on a forwarded 168.Xr ssh-agent 1 169to be used through a particular host (as specified by 170.Sq src-hostname ) 171to authenticate to a further host, 172specified by 173.Sq dst-hostname . 174.Pp 175Multiple destination constraints may be added when loading keys. 176When attempting authentication with a key that has destination constraints, 177the whole connection path, including 178.Xr ssh-agent 1 179forwarding, is tested against those constraints and each 180hop must be permitted for the attempt to succeed. 181For example, if key is forwarded to a remote host, 182.Sq host-b , 183and is attempting authentication to another host, 184.Sq host-c , 185then the operation will be successful only if 186.Sq host-b 187was permitted from the origin host and the subsequent 188.Sq host-b>host-c 189hop is also permitted by destination constraints. 190.Pp 191Hosts are identified by their host keys, and are looked up from known hosts 192files by 193.Nm . 194Wildcards patterns may be used for hostnames and certificate host 195keys are supported. 196By default, keys added by 197.Nm 198are not destination constrained. 199.Pp 200Destination constraints were added in OpenSSH release 8.9. 201Support in both the remote SSH client and server is required when using 202destination-constrained keys over a forwarded 203.Xr ssh-agent 1 204channel. 205.Pp 206It is also important to note that destination constraints can only be 207enforced by 208.Xr ssh-agent 1 209when a key is used, or when it is forwarded by a 210.Sy cooperating 211.Xr ssh 1 . 212Specifically, it does not prevent an attacker with access to a remote 213.Ev SSH_AUTH_SOCK 214from forwarding it again and using it on a different host (but only to 215a permitted destination). 216.It Fl K 217Load resident keys from a FIDO authenticator. 218.It Fl k 219When loading keys into or deleting keys from the agent, process plain private 220keys only and skip certificates. 221.It Fl L 222Lists public key parameters of all identities currently represented 223by the agent. 224.It Fl l 225Lists fingerprints of all identities currently represented by the agent. 226.It Fl q 227Be quiet after a successful operation. 228.It Fl S Ar provider 229Specifies a path to a library that will be used when adding 230FIDO authenticator-hosted keys, overriding the default of using the 231internal USB HID support. 232.It Fl s Ar pkcs11 233Add keys provided by the PKCS#11 shared library 234.Ar pkcs11 . 235Certificate files may optionally be listed as command-line arguments. 236If these are present, then they will be loaded into the agent using any 237corresponding private keys loaded from the PKCS#11 token. 238.It Fl T Ar pubkey ... 239Tests whether the private keys that correspond to the specified 240.Ar pubkey 241files are usable by performing sign and verify operations on each. 242.It Fl t Ar life 243Set a maximum lifetime when adding identities to an agent. 244The lifetime may be specified in seconds or in a time format 245specified in 246.Xr sshd_config 5 . 247.It Fl v 248Verbose mode. 249Causes 250.Nm 251to print debugging messages about its progress. 252This is helpful in debugging problems. 253Multiple 254.Fl v 255options increase the verbosity. 256The maximum is 3. 257.It Fl X 258Unlock the agent. 259.It Fl x 260Lock the agent with a password. 261.El 262.Sh ENVIRONMENT 263.Bl -tag -width Ds 264.It Ev "DISPLAY", "SSH_ASKPASS" and "SSH_ASKPASS_REQUIRE" 265If 266.Nm 267needs a passphrase, it will read the passphrase from the current 268terminal if it was run from a terminal. 269If 270.Nm 271does not have a terminal associated with it but 272.Ev DISPLAY 273and 274.Ev SSH_ASKPASS 275are set, it will execute the program specified by 276.Ev SSH_ASKPASS 277(by default 278.Dq ssh-askpass ) 279and open an X11 window to read the passphrase. 280This is particularly useful when calling 281.Nm 282from a 283.Pa .xsession 284or related script. 285.Pp 286.Ev SSH_ASKPASS_REQUIRE 287allows further control over the use of an askpass program. 288If this variable is set to 289.Dq never 290then 291.Nm 292will never attempt to use one. 293If it is set to 294.Dq prefer , 295then 296.Nm 297will prefer to use the askpass program instead of the TTY when requesting 298passwords. 299Finally, if the variable is set to 300.Dq force , 301then the askpass program will be used for all passphrase input regardless 302of whether 303.Ev DISPLAY 304is set. 305.It Ev SSH_AUTH_SOCK 306Identifies the path of a 307.Ux Ns -domain 308socket used to communicate with the agent. 309.It Ev SSH_SK_PROVIDER 310Specifies a path to a library that will be used when loading any 311FIDO authenticator-hosted keys, overriding the default of using 312the built-in USB HID support. 313.El 314.Sh FILES 315.Bl -tag -width Ds -compact 316.It Pa ~/.ssh/id_ecdsa 317.It Pa ~/.ssh/id_ecdsa_sk 318.It Pa ~/.ssh/id_ed25519 319.It Pa ~/.ssh/id_ed25519_sk 320.It Pa ~/.ssh/id_rsa 321Contains the ECDSA, authenticator-hosted ECDSA, Ed25519, 322authenticator-hosted Ed25519 or RSA authentication identity of the user. 323.El 324.Pp 325Identity files should not be readable by anyone but the user. 326Note that 327.Nm 328ignores identity files if they are accessible by others. 329.Sh EXIT STATUS 330Exit status is 0 on success, 1 if the specified command fails, 331and 2 if 332.Nm 333is unable to contact the authentication agent. 334.Sh SEE ALSO 335.Xr ssh 1 , 336.Xr ssh-agent 1 , 337.Xr ssh-askpass 1 , 338.Xr ssh-keygen 1 , 339.Xr sshd 8 340.Sh AUTHORS 341OpenSSH is a derivative of the original and free 342ssh 1.2.12 release by Tatu Ylonen. 343Aaron Campbell, Bob Beck, Markus Friedl, Niels Provos, 344Theo de Raadt and Dug Song 345removed many bugs, re-added newer features and 346created OpenSSH. 347Markus Friedl contributed the support for SSH 348protocol versions 1.5 and 2.0. 349