first time login denied
I'm installing on a raspberry pi, device is fine as I'm converting from raspbian.
Followed the account setup and install as per:
https://www.ubuntu.com/download/iot/raspberry-pi-2-3
I've generated an SSH key pair and uploaded to my ubunto one account.
I'm using Mobaxterm as a terminal program. Is there some problem with the key validation?
The terminal log shows that the key is accepted (right? The fingerprint matches that shown on the remote server)
ssh -v johnmcdnz@192.168.1.24
OpenSSH_7.1p2, OpenSSL 1.0.1g 7 Apr 2014
debug1: Reading configuration data /etc/ssh_config
debug1: Connecting to 192.168.1.24 [192.168.1.24] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.1
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.1
debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.1 pat OpenSSH* compat 0x04000000
debug1: Authenticating to 192.168.1.24:22 as 'johnmcdnz'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-sha1 zlib@openssh.com
debug1: kex: client->server aes128-ctr hmac-sha1 zlib@openssh.com
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ssh-rsa SHA256:OXGzdP3EuoHBPEbhwf7jWxDVwaIkK+jht06HBB08BAI
debug1: Host '192.168.1.24' is known and matches the RSA host key.
debug1: Found key in /home/mobaxterm/.ssh/known_hosts:1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: pubkey_prepare: ssh_fetch_identitylist: agent refused operation
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /home/mobaxterm/.ssh/id_rsa
debug1: Trying private key: /home/mobaxterm/.ssh/id_dsa
debug1: Trying private key: /home/mobaxterm/.ssh/id_ecdsa
debug1: Trying private key: /home/mobaxterm/.ssh/id_ed25519
debug1: Next authentication method: password
johnmcdnz@192.168.1.24's password:
debug1: Authentications that can continue: publickey,password
johnmcdnz@192.168.1.24's password:
debug1: Authentications that can continue: publickey,password
johnmcdnz@192.168.1.24's password:
ssh password authentication
New contributor
add a comment |
I'm installing on a raspberry pi, device is fine as I'm converting from raspbian.
Followed the account setup and install as per:
https://www.ubuntu.com/download/iot/raspberry-pi-2-3
I've generated an SSH key pair and uploaded to my ubunto one account.
I'm using Mobaxterm as a terminal program. Is there some problem with the key validation?
The terminal log shows that the key is accepted (right? The fingerprint matches that shown on the remote server)
ssh -v johnmcdnz@192.168.1.24
OpenSSH_7.1p2, OpenSSL 1.0.1g 7 Apr 2014
debug1: Reading configuration data /etc/ssh_config
debug1: Connecting to 192.168.1.24 [192.168.1.24] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.1
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.1
debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.1 pat OpenSSH* compat 0x04000000
debug1: Authenticating to 192.168.1.24:22 as 'johnmcdnz'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-sha1 zlib@openssh.com
debug1: kex: client->server aes128-ctr hmac-sha1 zlib@openssh.com
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ssh-rsa SHA256:OXGzdP3EuoHBPEbhwf7jWxDVwaIkK+jht06HBB08BAI
debug1: Host '192.168.1.24' is known and matches the RSA host key.
debug1: Found key in /home/mobaxterm/.ssh/known_hosts:1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: pubkey_prepare: ssh_fetch_identitylist: agent refused operation
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /home/mobaxterm/.ssh/id_rsa
debug1: Trying private key: /home/mobaxterm/.ssh/id_dsa
debug1: Trying private key: /home/mobaxterm/.ssh/id_ecdsa
debug1: Trying private key: /home/mobaxterm/.ssh/id_ed25519
debug1: Next authentication method: password
johnmcdnz@192.168.1.24's password:
debug1: Authentications that can continue: publickey,password
johnmcdnz@192.168.1.24's password:
debug1: Authentications that can continue: publickey,password
johnmcdnz@192.168.1.24's password:
ssh password authentication
New contributor
fyi, the password is lowercase alpha and numbers. So should not be any keyboard issues.
– John McDermott
Jan 4 at 0:15
add a comment |
I'm installing on a raspberry pi, device is fine as I'm converting from raspbian.
Followed the account setup and install as per:
https://www.ubuntu.com/download/iot/raspberry-pi-2-3
I've generated an SSH key pair and uploaded to my ubunto one account.
I'm using Mobaxterm as a terminal program. Is there some problem with the key validation?
The terminal log shows that the key is accepted (right? The fingerprint matches that shown on the remote server)
ssh -v johnmcdnz@192.168.1.24
OpenSSH_7.1p2, OpenSSL 1.0.1g 7 Apr 2014
debug1: Reading configuration data /etc/ssh_config
debug1: Connecting to 192.168.1.24 [192.168.1.24] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.1
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.1
debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.1 pat OpenSSH* compat 0x04000000
debug1: Authenticating to 192.168.1.24:22 as 'johnmcdnz'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-sha1 zlib@openssh.com
debug1: kex: client->server aes128-ctr hmac-sha1 zlib@openssh.com
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ssh-rsa SHA256:OXGzdP3EuoHBPEbhwf7jWxDVwaIkK+jht06HBB08BAI
debug1: Host '192.168.1.24' is known and matches the RSA host key.
debug1: Found key in /home/mobaxterm/.ssh/known_hosts:1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: pubkey_prepare: ssh_fetch_identitylist: agent refused operation
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /home/mobaxterm/.ssh/id_rsa
debug1: Trying private key: /home/mobaxterm/.ssh/id_dsa
debug1: Trying private key: /home/mobaxterm/.ssh/id_ecdsa
debug1: Trying private key: /home/mobaxterm/.ssh/id_ed25519
debug1: Next authentication method: password
johnmcdnz@192.168.1.24's password:
debug1: Authentications that can continue: publickey,password
johnmcdnz@192.168.1.24's password:
debug1: Authentications that can continue: publickey,password
johnmcdnz@192.168.1.24's password:
ssh password authentication
New contributor
I'm installing on a raspberry pi, device is fine as I'm converting from raspbian.
Followed the account setup and install as per:
https://www.ubuntu.com/download/iot/raspberry-pi-2-3
I've generated an SSH key pair and uploaded to my ubunto one account.
I'm using Mobaxterm as a terminal program. Is there some problem with the key validation?
The terminal log shows that the key is accepted (right? The fingerprint matches that shown on the remote server)
ssh -v johnmcdnz@192.168.1.24
OpenSSH_7.1p2, OpenSSL 1.0.1g 7 Apr 2014
debug1: Reading configuration data /etc/ssh_config
debug1: Connecting to 192.168.1.24 [192.168.1.24] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_rsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_rsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_dsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_dsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_ecdsa type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_ecdsa-cert type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_ed25519 type -1
debug1: key_load_public: No such file or directory
debug1: identity file /home/mobaxterm/.ssh/id_ed25519-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.1
debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.1
debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.1 pat OpenSSH* compat 0x04000000
debug1: Authenticating to 192.168.1.24:22 as 'johnmcdnz'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: server->client aes128-ctr hmac-sha1 zlib@openssh.com
debug1: kex: client->server aes128-ctr hmac-sha1 zlib@openssh.com
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ssh-rsa SHA256:OXGzdP3EuoHBPEbhwf7jWxDVwaIkK+jht06HBB08BAI
debug1: Host '192.168.1.24' is known and matches the RSA host key.
debug1: Found key in /home/mobaxterm/.ssh/known_hosts:1
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_REQUEST sent
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: pubkey_prepare: ssh_fetch_identitylist: agent refused operation
debug1: Authentications that can continue: publickey,password
debug1: Next authentication method: publickey
debug1: Trying private key: /home/mobaxterm/.ssh/id_rsa
debug1: Trying private key: /home/mobaxterm/.ssh/id_dsa
debug1: Trying private key: /home/mobaxterm/.ssh/id_ecdsa
debug1: Trying private key: /home/mobaxterm/.ssh/id_ed25519
debug1: Next authentication method: password
johnmcdnz@192.168.1.24's password:
debug1: Authentications that can continue: publickey,password
johnmcdnz@192.168.1.24's password:
debug1: Authentications that can continue: publickey,password
johnmcdnz@192.168.1.24's password:
ssh password authentication
ssh password authentication
New contributor
New contributor
edited Jan 4 at 0:09
vidarlo
9,38942445
9,38942445
New contributor
asked Jan 4 at 0:04
John McDermottJohn McDermott
11
11
New contributor
New contributor
fyi, the password is lowercase alpha and numbers. So should not be any keyboard issues.
– John McDermott
Jan 4 at 0:15
add a comment |
fyi, the password is lowercase alpha and numbers. So should not be any keyboard issues.
– John McDermott
Jan 4 at 0:15
fyi, the password is lowercase alpha and numbers. So should not be any keyboard issues.
– John McDermott
Jan 4 at 0:15
fyi, the password is lowercase alpha and numbers. So should not be any keyboard issues.
– John McDermott
Jan 4 at 0:15
add a comment |
1 Answer
1
active
oldest
votes
I friend ... look your first information, debug1: Reading configuration data /etc/ssh_config
you see and remove comments on this file? this is necessary to work, if you do not remove the comments it will work as a standard (#).
Try removing comments: (#RSAAuthentication yes) or (# RhostsRSAAuthentication yes)
change default "no" to "yes"
Other lines need to have your comments removed too, see some tips on the internet about ssh, I will not put everything here would be extended the answer.
Any time you change /etc/ssh/ssh_config, run for restart:
service ssh restart
verify if this is on command: service ssh status (if have any error this command show)
sorry about my English, I hope I've helped.
New contributor
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
John McDermott is a new contributor. Be nice, and check out our Code of Conduct.
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%2faskubuntu.com%2fquestions%2f1106768%2ffirst-time-login-denied%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I friend ... look your first information, debug1: Reading configuration data /etc/ssh_config
you see and remove comments on this file? this is necessary to work, if you do not remove the comments it will work as a standard (#).
Try removing comments: (#RSAAuthentication yes) or (# RhostsRSAAuthentication yes)
change default "no" to "yes"
Other lines need to have your comments removed too, see some tips on the internet about ssh, I will not put everything here would be extended the answer.
Any time you change /etc/ssh/ssh_config, run for restart:
service ssh restart
verify if this is on command: service ssh status (if have any error this command show)
sorry about my English, I hope I've helped.
New contributor
add a comment |
I friend ... look your first information, debug1: Reading configuration data /etc/ssh_config
you see and remove comments on this file? this is necessary to work, if you do not remove the comments it will work as a standard (#).
Try removing comments: (#RSAAuthentication yes) or (# RhostsRSAAuthentication yes)
change default "no" to "yes"
Other lines need to have your comments removed too, see some tips on the internet about ssh, I will not put everything here would be extended the answer.
Any time you change /etc/ssh/ssh_config, run for restart:
service ssh restart
verify if this is on command: service ssh status (if have any error this command show)
sorry about my English, I hope I've helped.
New contributor
add a comment |
I friend ... look your first information, debug1: Reading configuration data /etc/ssh_config
you see and remove comments on this file? this is necessary to work, if you do not remove the comments it will work as a standard (#).
Try removing comments: (#RSAAuthentication yes) or (# RhostsRSAAuthentication yes)
change default "no" to "yes"
Other lines need to have your comments removed too, see some tips on the internet about ssh, I will not put everything here would be extended the answer.
Any time you change /etc/ssh/ssh_config, run for restart:
service ssh restart
verify if this is on command: service ssh status (if have any error this command show)
sorry about my English, I hope I've helped.
New contributor
I friend ... look your first information, debug1: Reading configuration data /etc/ssh_config
you see and remove comments on this file? this is necessary to work, if you do not remove the comments it will work as a standard (#).
Try removing comments: (#RSAAuthentication yes) or (# RhostsRSAAuthentication yes)
change default "no" to "yes"
Other lines need to have your comments removed too, see some tips on the internet about ssh, I will not put everything here would be extended the answer.
Any time you change /etc/ssh/ssh_config, run for restart:
service ssh restart
verify if this is on command: service ssh status (if have any error this command show)
sorry about my English, I hope I've helped.
New contributor
New contributor
answered Jan 4 at 0:57
Júlio Gadioli SoaresJúlio Gadioli Soares
1
1
New contributor
New contributor
add a comment |
add a comment |
John McDermott is a new contributor. Be nice, and check out our Code of Conduct.
John McDermott is a new contributor. Be nice, and check out our Code of Conduct.
John McDermott is a new contributor. Be nice, and check out our Code of Conduct.
John McDermott is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f1106768%2ffirst-time-login-denied%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
fyi, the password is lowercase alpha and numbers. So should not be any keyboard issues.
– John McDermott
Jan 4 at 0:15