SSH host key changed just after setting root password











up vote
1
down vote

favorite
1












This might sound super suspicious, but it just happened to me:



I run a rented Raspberry Pi as my own mail server and today I set a root password to eventually login as root directly. I did not yet check whether the default configuration forbids root login. I exited the SSH session and restartet Putty to login as root.



The access was denied and after restarting Putty again to login to the account which I usually use, the host seems to have changed its key and Putty warned me about this.



Between setting the root password and getting the warning from Putty about the changed host key, less than two minutes passed. Also, I mostly trust the client machine, it is a quite freshly set up Windows 10 machine I got from my employer for work.



Should I be concerned, that someone cracked my server in such a short time (I couldn't do it nearly that fast)? It would not make any sense to change the key after already having root access.



What would be the best to do now? Should I contanct the data center operator to physically shut down my machine? Or should I just connect via SSH anyway?










share|improve this question
























  • moved here from stackoverflow
    – Fabian31415
    Nov 28 at 11:07










  • Actually, if you have the default rpi login, and enable root login, it might actually get hacked instantly if the provider is specialized to rpi hosting.
    – davidbaumann
    Nov 28 at 16:42










  • Thanks! I forgot to mention that all users have very strong passwords so far, because default login credentials are definitely a big threat.
    – Fabian31415
    Nov 29 at 9:12















up vote
1
down vote

favorite
1












This might sound super suspicious, but it just happened to me:



I run a rented Raspberry Pi as my own mail server and today I set a root password to eventually login as root directly. I did not yet check whether the default configuration forbids root login. I exited the SSH session and restartet Putty to login as root.



The access was denied and after restarting Putty again to login to the account which I usually use, the host seems to have changed its key and Putty warned me about this.



Between setting the root password and getting the warning from Putty about the changed host key, less than two minutes passed. Also, I mostly trust the client machine, it is a quite freshly set up Windows 10 machine I got from my employer for work.



Should I be concerned, that someone cracked my server in such a short time (I couldn't do it nearly that fast)? It would not make any sense to change the key after already having root access.



What would be the best to do now? Should I contanct the data center operator to physically shut down my machine? Or should I just connect via SSH anyway?










share|improve this question
























  • moved here from stackoverflow
    – Fabian31415
    Nov 28 at 11:07










  • Actually, if you have the default rpi login, and enable root login, it might actually get hacked instantly if the provider is specialized to rpi hosting.
    – davidbaumann
    Nov 28 at 16:42










  • Thanks! I forgot to mention that all users have very strong passwords so far, because default login credentials are definitely a big threat.
    – Fabian31415
    Nov 29 at 9:12













up vote
1
down vote

favorite
1









up vote
1
down vote

favorite
1






1





This might sound super suspicious, but it just happened to me:



I run a rented Raspberry Pi as my own mail server and today I set a root password to eventually login as root directly. I did not yet check whether the default configuration forbids root login. I exited the SSH session and restartet Putty to login as root.



The access was denied and after restarting Putty again to login to the account which I usually use, the host seems to have changed its key and Putty warned me about this.



Between setting the root password and getting the warning from Putty about the changed host key, less than two minutes passed. Also, I mostly trust the client machine, it is a quite freshly set up Windows 10 machine I got from my employer for work.



Should I be concerned, that someone cracked my server in such a short time (I couldn't do it nearly that fast)? It would not make any sense to change the key after already having root access.



What would be the best to do now? Should I contanct the data center operator to physically shut down my machine? Or should I just connect via SSH anyway?










share|improve this question















This might sound super suspicious, but it just happened to me:



I run a rented Raspberry Pi as my own mail server and today I set a root password to eventually login as root directly. I did not yet check whether the default configuration forbids root login. I exited the SSH session and restartet Putty to login as root.



The access was denied and after restarting Putty again to login to the account which I usually use, the host seems to have changed its key and Putty warned me about this.



Between setting the root password and getting the warning from Putty about the changed host key, less than two minutes passed. Also, I mostly trust the client machine, it is a quite freshly set up Windows 10 machine I got from my employer for work.



Should I be concerned, that someone cracked my server in such a short time (I couldn't do it nearly that fast)? It would not make any sense to change the key after already having root access.



What would be the best to do now? Should I contanct the data center operator to physically shut down my machine? Or should I just connect via SSH anyway?







ssh security putty ssh-keys






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 28 at 16:29









Mureinik

2,27951525




2,27951525










asked Nov 28 at 11:07









Fabian31415

62




62












  • moved here from stackoverflow
    – Fabian31415
    Nov 28 at 11:07










  • Actually, if you have the default rpi login, and enable root login, it might actually get hacked instantly if the provider is specialized to rpi hosting.
    – davidbaumann
    Nov 28 at 16:42










  • Thanks! I forgot to mention that all users have very strong passwords so far, because default login credentials are definitely a big threat.
    – Fabian31415
    Nov 29 at 9:12


















  • moved here from stackoverflow
    – Fabian31415
    Nov 28 at 11:07










  • Actually, if you have the default rpi login, and enable root login, it might actually get hacked instantly if the provider is specialized to rpi hosting.
    – davidbaumann
    Nov 28 at 16:42










  • Thanks! I forgot to mention that all users have very strong passwords so far, because default login credentials are definitely a big threat.
    – Fabian31415
    Nov 29 at 9:12
















moved here from stackoverflow
– Fabian31415
Nov 28 at 11:07




moved here from stackoverflow
– Fabian31415
Nov 28 at 11:07












Actually, if you have the default rpi login, and enable root login, it might actually get hacked instantly if the provider is specialized to rpi hosting.
– davidbaumann
Nov 28 at 16:42




Actually, if you have the default rpi login, and enable root login, it might actually get hacked instantly if the provider is specialized to rpi hosting.
– davidbaumann
Nov 28 at 16:42












Thanks! I forgot to mention that all users have very strong passwords so far, because default login credentials are definitely a big threat.
– Fabian31415
Nov 29 at 9:12




Thanks! I forgot to mention that all users have very strong passwords so far, because default login credentials are definitely a big threat.
– Fabian31415
Nov 29 at 9:12










1 Answer
1






active

oldest

votes

















up vote
0
down vote













It seems ridiculous, but restarting the Windows client machine solved(!) the problem. The server's auth.log does not show any strange activities.






share|improve this answer





















  • moved here from stackoverflow
    – Fabian31415
    Nov 28 at 11:08











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
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',
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
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1379051%2fssh-host-key-changed-just-after-setting-root-password%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








up vote
0
down vote













It seems ridiculous, but restarting the Windows client machine solved(!) the problem. The server's auth.log does not show any strange activities.






share|improve this answer





















  • moved here from stackoverflow
    – Fabian31415
    Nov 28 at 11:08















up vote
0
down vote













It seems ridiculous, but restarting the Windows client machine solved(!) the problem. The server's auth.log does not show any strange activities.






share|improve this answer





















  • moved here from stackoverflow
    – Fabian31415
    Nov 28 at 11:08













up vote
0
down vote










up vote
0
down vote









It seems ridiculous, but restarting the Windows client machine solved(!) the problem. The server's auth.log does not show any strange activities.






share|improve this answer












It seems ridiculous, but restarting the Windows client machine solved(!) the problem. The server's auth.log does not show any strange activities.







share|improve this answer












share|improve this answer



share|improve this answer










answered Nov 28 at 11:08









Fabian31415

62




62












  • moved here from stackoverflow
    – Fabian31415
    Nov 28 at 11:08


















  • moved here from stackoverflow
    – Fabian31415
    Nov 28 at 11:08
















moved here from stackoverflow
– Fabian31415
Nov 28 at 11:08




moved here from stackoverflow
– Fabian31415
Nov 28 at 11:08


















draft saved

draft discarded




















































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.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1379051%2fssh-host-key-changed-just-after-setting-root-password%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

Plaza Victoria

Puebla de Zaragoza

Musa