Multiple similar entries in ssh config

Say I want to configure my ssh options for 30 servers with the same setup in my .ssh config file:

host XXX
     User my_username
     Compression yes
     Ciphers arcfour,blowfish-cbc
     Protocol 2
     ControlMaster auto
     ControlPath ~/.ssh/%r@%h:%p
     IdentityFile ~/.ssh/YYY/id_rsa

where the only thing that changes between these 30 machines is XXX.

Instead than repeating the above structure 30 times in my config file, is there another way to define a range of machines?

Simply use *

See man ssh_config:

A pattern consists of zero or more non-whitespace characters, ‘*’ (a wildcard that matches zero or more characters), or ‘?’
(a wildcard that matches exactly one character). For example, to specify a set of declarations for any host in the “”
set of domains, the following pattern could be used:

       Host *

 The following pattern would match any host in the 192.168.0.[0-9] network range:

       Host 192.168.0.?

 A pattern-list is a comma-separated list of patterns.  Patterns within pattern-lists may be negated by preceding them with an
 exclamation mark (‘!’).  For example, to allow a key to be used from anywhere within an organisation except from the “dialup”
 pool, the following entry (in authorized_keys) could be used:

Answered By: H.-Dirk Schmitt

From the ssh_config(5) man page:

 Host    Restricts the following declarations (up to the next Host key‐
         word) to be only for those hosts that match one of the patterns
         given after the keyword.  If more than one pattern is provided,
         they should be separated by whitespace.

         Specifies the real host name to log into.  This can be used to
         specify nicknames or abbreviations for hosts.  If the hostname
         contains the character sequence ‘%h’, then this will be replaced
         with the host name specified on the commandline (this is useful
         for manipulating unqualified names).



To minimize the setup you can have a .ssh/config like this one

Host X01

Host X02


Host X01 X02 ...
     User my_username
     Compression yes
     Ciphers arcfour,blowfish-cbc
     Protocol 2
     ControlMaster auto
     ControlPath ~/.ssh/%r@%h:%p
     IdentityFile ~/.ssh/YYY/id_rsa

Host X01 X02 ... could be replace by Host * if every host have the following configuration

Answered By: Guillaume Vincent

this works for me:

CanonicalizeHostname yes

host  *
   user myuser
host *
   user myuser

this allows one to use names within the domain and have the username changed:

bluebottle:~ user_one$ ssh itslogprd05's password: 
Answered By: Russell Fulton

From Ignacio Vazquez-Abrams and H.-Dirk Schmitt’s answers, one can add the following to .ssh/config

    User myname

and then, for example, you can login as by

ssh XXX2
Answered By: Vito Chou

The following way works.

Host 10.10.* 10.11.*
     User vagrant
Answered By: edib
Categories: Answers Tags:
Answers are sorted by their score. The answer accepted by the question owner as the best is marked with
at the top-right corner.