Tell SSH to to use special IdentityFile for special user
up vote
1
down vote
favorite
I need to tell SSH to use special IdentityFile for special user.
For example host specs wizard@host1.com wizard@any-other-host.org should use key ~/.ssh/id_wizard
I'd like to write
User wizard
IdentityFile ~/.ssh/id_wizard
but there is no such option in man ssh_config.
ssh ssh-config
asked Nov 11 at 15:06
kyb
1,5591934
add a comment |
up vote
1
down vote
favorite
I need to tell SSH to use special IdentityFile for special user.
For example host specs wizard@host1.com wizard@any-other-host.org should use key ~/.ssh/id_wizard
I'd like to write
User wizard
IdentityFile ~/.ssh/id_wizard
but there is no such option in man ssh_config.
ssh ssh-config
asked Nov 11 at 15:06
kyb
1,5591934
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I need to tell SSH to use special IdentityFile for special user.
For example host specs wizard@host1.com wizard@any-other-host.org should use key ~/.ssh/id_wizard
I'd like to write
User wizard
IdentityFile ~/.ssh/id_wizard
but there is no such option in man ssh_config.
ssh ssh-config
asked Nov 11 at 15:06
kyb
1,5591934
I need to tell SSH to use special IdentityFile for special user.
For example host specs wizard@host1.com wizard@any-other-host.org should use key ~/.ssh/id_wizard
I'd like to write
User wizard
IdentityFile ~/.ssh/id_wizard
but there is no such option in man ssh_config.
ssh ssh-config
ssh ssh-config
asked Nov 11 at 15:06
kyb
1,5591934
asked Nov 11 at 15:06
kyb
1,5591934
asked Nov 11 at 15:06
kyb
1,5591934
asked Nov 11 at 15:06
kyb
1,5591934
asked Nov 11 at 15:06
kyb
1,5591934
1,5591934
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
You should be able to use the Match directive. Match is a more generalized form of the Host directive:
Match
Restricts the following declarations (up to the next Host or Match
keyword) to be used only when the conditions following the Match
keyword are satisfied. Match conditions are specified using one or
more criteria or the single token all which always matches. The
available criteria keywords are: canonical, exec, host, originalhost,
user, and localuser. The all criteria must appear alone or immediately
after canonical. Other criteria may be combined arbitrarily. All
criteria but all and canonical require an argument. Criteria may be
negated by prepending an exclamation mark (‘!’).
...
The other keywords' criteria must be single entries or comma-separated
lists and may use the wildcard and negation operators described in the
PATTERNS section. ... The user keyword
matches against the target username on the remote host.
So:
Match user wizard
IdentityFile ~/.ssh/id_wizard
answered Nov 11 at 15:27
Kenster
13.1k104869
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
You should be able to use the Match directive. Match is a more generalized form of the Host directive:
Match
Restricts the following declarations (up to the next Host or Match
keyword) to be used only when the conditions following the Match
keyword are satisfied. Match conditions are specified using one or
more criteria or the single token all which always matches. The
available criteria keywords are: canonical, exec, host, originalhost,
user, and localuser. The all criteria must appear alone or immediately
after canonical. Other criteria may be combined arbitrarily. All
criteria but all and canonical require an argument. Criteria may be
negated by prepending an exclamation mark (‘!’).
...
The other keywords' criteria must be single entries or comma-separated
lists and may use the wildcard and negation operators described in the
PATTERNS section. ... The user keyword
matches against the target username on the remote host.
So:
Match user wizard
IdentityFile ~/.ssh/id_wizard
answered Nov 11 at 15:27
Kenster
13.1k104869
add a comment |
up vote
1
down vote
accepted
You should be able to use the Match directive. Match is a more generalized form of the Host directive:
Match
Restricts the following declarations (up to the next Host or Match
keyword) to be used only when the conditions following the Match
keyword are satisfied. Match conditions are specified using one or
more criteria or the single token all which always matches. The
available criteria keywords are: canonical, exec, host, originalhost,
user, and localuser. The all criteria must appear alone or immediately
after canonical. Other criteria may be combined arbitrarily. All
criteria but all and canonical require an argument. Criteria may be
negated by prepending an exclamation mark (‘!’).
...
The other keywords' criteria must be single entries or comma-separated
lists and may use the wildcard and negation operators described in the
PATTERNS section. ... The user keyword
matches against the target username on the remote host.
So:
Match user wizard
IdentityFile ~/.ssh/id_wizard
answered Nov 11 at 15:27
Kenster
13.1k104869
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
You should be able to use the Match directive. Match is a more generalized form of the Host directive:
Match
Restricts the following declarations (up to the next Host or Match
keyword) to be used only when the conditions following the Match
keyword are satisfied. Match conditions are specified using one or
more criteria or the single token all which always matches. The
available criteria keywords are: canonical, exec, host, originalhost,
user, and localuser. The all criteria must appear alone or immediately
after canonical. Other criteria may be combined arbitrarily. All
criteria but all and canonical require an argument. Criteria may be
negated by prepending an exclamation mark (‘!’).
...
The other keywords' criteria must be single entries or comma-separated
lists and may use the wildcard and negation operators described in the
PATTERNS section. ... The user keyword
matches against the target username on the remote host.
So:
Match user wizard
IdentityFile ~/.ssh/id_wizard
answered Nov 11 at 15:27
Kenster
13.1k104869
You should be able to use the Match directive. Match is a more generalized form of the Host directive:
Match
Restricts the following declarations (up to the next Host or Match
keyword) to be used only when the conditions following the Match
keyword are satisfied. Match conditions are specified using one or
more criteria or the single token all which always matches. The
available criteria keywords are: canonical, exec, host, originalhost,
user, and localuser. The all criteria must appear alone or immediately
after canonical. Other criteria may be combined arbitrarily. All
criteria but all and canonical require an argument. Criteria may be
negated by prepending an exclamation mark (‘!’).
...
The other keywords' criteria must be single entries or comma-separated
lists and may use the wildcard and negation operators described in the
PATTERNS section. ... The user keyword
matches against the target username on the remote host.
So:
Match user wizard
IdentityFile ~/.ssh/id_wizard
answered Nov 11 at 15:27
Kenster
13.1k104869
answered Nov 11 at 15:27
Kenster
13.1k104869
answered Nov 11 at 15:27
Kenster
13.1k104869
answered Nov 11 at 15:27
Kenster
13.1k104869
13.1k104869
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53250034%2ftell-ssh-to-to-use-special-identityfile-for-special-user%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
