Mojave SSH failure
up vote
1
down vote
favorite
have some weird issues regarding SSH access.
I just reinstalled a brand new Mac with macOS Mojave.
After configuring my ssh keys, i can connect to both of my Linux servers (Ubuntu 18.04 LTS and Ubuntu 16.04). Connection via terminal without pwd runs without any problems however, when I try to use other software to connect, connection fails.
My pub key is added to the ubuntu authorized_keys, user matches etc. I still have my previous laptop, running mojave and SSH without any problem.
I tried setting up an SSH connection with robo3T, commanderOne and cyberduck. All of these fail while terminal succeeds ...
Don't know where to search for this problem ...
UPDATE
After a long search, I copied private and public keys from my previous laptop, which seems to be a solution to the problem. I'm still curious about why terminal connection works and third party apps don't :-/
macos ubuntu ssh macos-mojave
asked Nov 2 at 14:24
Yoeri
1063
add a comment |
up vote
1
down vote
favorite
have some weird issues regarding SSH access.
I just reinstalled a brand new Mac with macOS Mojave.
After configuring my ssh keys, i can connect to both of my Linux servers (Ubuntu 18.04 LTS and Ubuntu 16.04). Connection via terminal without pwd runs without any problems however, when I try to use other software to connect, connection fails.
My pub key is added to the ubuntu authorized_keys, user matches etc. I still have my previous laptop, running mojave and SSH without any problem.
I tried setting up an SSH connection with robo3T, commanderOne and cyberduck. All of these fail while terminal succeeds ...
Don't know where to search for this problem ...
UPDATE
After a long search, I copied private and public keys from my previous laptop, which seems to be a solution to the problem. I'm still curious about why terminal connection works and third party apps don't :-/
macos ubuntu ssh macos-mojave
asked Nov 2 at 14:24
Yoeri
1063
1
Can you post some messages or indications of the error? Its hard to diagnose with the limited information,
– Hogstrom
Nov 3 at 14:01
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
have some weird issues regarding SSH access.
I just reinstalled a brand new Mac with macOS Mojave.
After configuring my ssh keys, i can connect to both of my Linux servers (Ubuntu 18.04 LTS and Ubuntu 16.04). Connection via terminal without pwd runs without any problems however, when I try to use other software to connect, connection fails.
My pub key is added to the ubuntu authorized_keys, user matches etc. I still have my previous laptop, running mojave and SSH without any problem.
I tried setting up an SSH connection with robo3T, commanderOne and cyberduck. All of these fail while terminal succeeds ...
Don't know where to search for this problem ...
UPDATE
After a long search, I copied private and public keys from my previous laptop, which seems to be a solution to the problem. I'm still curious about why terminal connection works and third party apps don't :-/
macos ubuntu ssh macos-mojave
asked Nov 2 at 14:24
Yoeri
1063
have some weird issues regarding SSH access.
I just reinstalled a brand new Mac with macOS Mojave.
After configuring my ssh keys, i can connect to both of my Linux servers (Ubuntu 18.04 LTS and Ubuntu 16.04). Connection via terminal without pwd runs without any problems however, when I try to use other software to connect, connection fails.
My pub key is added to the ubuntu authorized_keys, user matches etc. I still have my previous laptop, running mojave and SSH without any problem.
I tried setting up an SSH connection with robo3T, commanderOne and cyberduck. All of these fail while terminal succeeds ...
Don't know where to search for this problem ...
UPDATE
After a long search, I copied private and public keys from my previous laptop, which seems to be a solution to the problem. I'm still curious about why terminal connection works and third party apps don't :-/
macos ubuntu ssh macos-mojave
macos ubuntu ssh macos-mojave
asked Nov 2 at 14:24
Yoeri
1063
asked Nov 2 at 14:24
Yoeri
1063
edited Nov 4 at 9:52
asked Nov 2 at 14:24
Yoeri
1063
asked Nov 2 at 14:24
Yoeri
1063
asked Nov 2 at 14:24
Yoeri
1063
1063
1
Can you post some messages or indications of the error? Its hard to diagnose with the limited information,
– Hogstrom
Nov 3 at 14:01
add a comment |
1
Can you post some messages or indications of the error? Its hard to diagnose with the limited information,
– Hogstrom
Nov 3 at 14:01
1
1
Can you post some messages or indications of the error? Its hard to diagnose with the limited information,
– Hogstrom
Nov 3 at 14:01
Can you post some messages or indications of the error? Its hard to diagnose with the limited information,
– Hogstrom
Nov 3 at 14:01
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
My guess is that your new keys have a password on the key itself and the ones you copied from your old machine do not. Other applications don’t know the password and so can’t use the key. I think you can use the KeyChain for the password to avoid this problem but since High Sierra you have to turn that on yourself by updating your SSH config.
answered Nov 19 at 9:30
SDJMcHattie
1113
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
My guess is that your new keys have a password on the key itself and the ones you copied from your old machine do not. Other applications don’t know the password and so can’t use the key. I think you can use the KeyChain for the password to avoid this problem but since High Sierra you have to turn that on yourself by updating your SSH config.
answered Nov 19 at 9:30
SDJMcHattie
1113
add a comment |
up vote
1
down vote
My guess is that your new keys have a password on the key itself and the ones you copied from your old machine do not. Other applications don’t know the password and so can’t use the key. I think you can use the KeyChain for the password to avoid this problem but since High Sierra you have to turn that on yourself by updating your SSH config.
answered Nov 19 at 9:30
SDJMcHattie
1113
add a comment |
up vote
1
down vote
up vote
1
down vote
My guess is that your new keys have a password on the key itself and the ones you copied from your old machine do not. Other applications don’t know the password and so can’t use the key. I think you can use the KeyChain for the password to avoid this problem but since High Sierra you have to turn that on yourself by updating your SSH config.
answered Nov 19 at 9:30
SDJMcHattie
1113
My guess is that your new keys have a password on the key itself and the ones you copied from your old machine do not. Other applications don’t know the password and so can’t use the key. I think you can use the KeyChain for the password to avoid this problem but since High Sierra you have to turn that on yourself by updating your SSH config.
answered Nov 19 at 9:30
SDJMcHattie
1113
answered Nov 19 at 9:30
SDJMcHattie
1113
answered Nov 19 at 9:30
SDJMcHattie
1113
answered Nov 19 at 9:30
SDJMcHattie
1113
1113
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- 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%2fsuperuser.com%2fquestions%2f1372206%2fmojave-ssh-failure%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
1
Can you post some messages or indications of the error? Its hard to diagnose with the limited information,
– Hogstrom
Nov 3 at 14:01