Confirming that public-key is the only authentication for ssh [on hold]
Clash Royale CLAN TAG#URR8PPP
up vote
-1
down vote
favorite
Question to be deleted soon. Do not answer.
Please answer this all-encompassing question instead (as RubberStamp suggests):
Security review: classifying ssh log-in attempts
If public-key is the only authentication method for ssh, your configuration is fairly unassailable from the scripting bots.
(from this U&L post)
I recall I chose public-key ssh as my only authentication method, but I've also dabbled with this and that on the AWS settings.
In the past I used to generate via ssh-keygen a file that I copy/pasted to the remote server, but now I'm using AWS's ssh -i myKeyPair.pem ubuntu@11.22.33.44. Is one method more secure than the other? More importantly, what is a test that I can run to confirm, now and continuously, that neither I nor someone else have opened anything other than public key in ssh?
ssh security
asked Nov 19 at 1:49
Calaf
13016
put on hold as unclear what you're asking by Jeff Schaller, thrig, mosvy, sam, Romeo Ninov Nov 19 at 17:28
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
up vote
-1
down vote
favorite
Question to be deleted soon. Do not answer.
Please answer this all-encompassing question instead (as RubberStamp suggests):
Security review: classifying ssh log-in attempts
If public-key is the only authentication method for ssh, your configuration is fairly unassailable from the scripting bots.
(from this U&L post)
I recall I chose public-key ssh as my only authentication method, but I've also dabbled with this and that on the AWS settings.
In the past I used to generate via ssh-keygen a file that I copy/pasted to the remote server, but now I'm using AWS's ssh -i myKeyPair.pem ubuntu@11.22.33.44. Is one method more secure than the other? More importantly, what is a test that I can run to confirm, now and continuously, that neither I nor someone else have opened anything other than public key in ssh?
ssh security
asked Nov 19 at 1:49
Calaf
13016
put on hold as unclear what you're asking by Jeff Schaller, thrig, mosvy, sam, Romeo Ninov Nov 19 at 17:28
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
You may want to add these thoughts to your original question rather than create a second one ... However, it's a bit unclear what you asking. Which "methods" of authentication are being compared? Or are you asking about the security of one key versus another? ... As for the complete history of authentication is concerned, if you've always had public key auth enabled and the other methods disabled, then public key is the historical past.
– RubberStamp
Nov 19 at 2:32
Damned if one does, damned if one doesn't. OK. Putting more than one question in one question.
– Calaf
Nov 19 at 3:17
add a comment |
up vote
-1
down vote
favorite
up vote
-1
down vote
favorite
Question to be deleted soon. Do not answer.
Please answer this all-encompassing question instead (as RubberStamp suggests):
Security review: classifying ssh log-in attempts
If public-key is the only authentication method for ssh, your configuration is fairly unassailable from the scripting bots.
(from this U&L post)
I recall I chose public-key ssh as my only authentication method, but I've also dabbled with this and that on the AWS settings.
In the past I used to generate via ssh-keygen a file that I copy/pasted to the remote server, but now I'm using AWS's ssh -i myKeyPair.pem ubuntu@11.22.33.44. Is one method more secure than the other? More importantly, what is a test that I can run to confirm, now and continuously, that neither I nor someone else have opened anything other than public key in ssh?
ssh security
asked Nov 19 at 1:49
Calaf
13016
Question to be deleted soon. Do not answer.
Please answer this all-encompassing question instead (as RubberStamp suggests):
Security review: classifying ssh log-in attempts
If public-key is the only authentication method for ssh, your configuration is fairly unassailable from the scripting bots.
(from this U&L post)
I recall I chose public-key ssh as my only authentication method, but I've also dabbled with this and that on the AWS settings.
In the past I used to generate via ssh-keygen a file that I copy/pasted to the remote server, but now I'm using AWS's ssh -i myKeyPair.pem ubuntu@11.22.33.44. Is one method more secure than the other? More importantly, what is a test that I can run to confirm, now and continuously, that neither I nor someone else have opened anything other than public key in ssh?
ssh security
ssh security
asked Nov 19 at 1:49
Calaf
13016
asked Nov 19 at 1:49
Calaf
13016
edited Nov 19 at 3:27
asked Nov 19 at 1:49
Calaf
13016
asked Nov 19 at 1:49
Calaf
13016
asked Nov 19 at 1:49
Calaf
13016
13016
put on hold as unclear what you're asking by Jeff Schaller, thrig, mosvy, sam, Romeo Ninov Nov 19 at 17:28
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
put on hold as unclear what you're asking by Jeff Schaller, thrig, mosvy, sam, Romeo Ninov Nov 19 at 17:28
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
You may want to add these thoughts to your original question rather than create a second one ... However, it's a bit unclear what you asking. Which "methods" of authentication are being compared? Or are you asking about the security of one key versus another? ... As for the complete history of authentication is concerned, if you've always had public key auth enabled and the other methods disabled, then public key is the historical past.
– RubberStamp
Nov 19 at 2:32
Damned if one does, damned if one doesn't. OK. Putting more than one question in one question.
– Calaf
Nov 19 at 3:17
add a comment |
You may want to add these thoughts to your original question rather than create a second one ... However, it's a bit unclear what you asking. Which "methods" of authentication are being compared? Or are you asking about the security of one key versus another? ... As for the complete history of authentication is concerned, if you've always had public key auth enabled and the other methods disabled, then public key is the historical past.
– RubberStamp
Nov 19 at 2:32
Damned if one does, damned if one doesn't. OK. Putting more than one question in one question.
– Calaf
Nov 19 at 3:17
You may want to add these thoughts to your original question rather than create a second one ... However, it's a bit unclear what you asking. Which "methods" of authentication are being compared? Or are you asking about the security of one key versus another? ... As for the complete history of authentication is concerned, if you've always had public key auth enabled and the other methods disabled, then public key is the historical past.
– RubberStamp
Nov 19 at 2:32
You may want to add these thoughts to your original question rather than create a second one ... However, it's a bit unclear what you asking. Which "methods" of authentication are being compared? Or are you asking about the security of one key versus another? ... As for the complete history of authentication is concerned, if you've always had public key auth enabled and the other methods disabled, then public key is the historical past.
– RubberStamp
Nov 19 at 2:32
Damned if one does, damned if one doesn't. OK. Putting more than one question in one question.
– Calaf
Nov 19 at 3:17
Damned if one does, damned if one doesn't. OK. Putting more than one question in one question.
– Calaf
Nov 19 at 3:17
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
You may want to add these thoughts to your original question rather than create a second one ... However, it's a bit unclear what you asking. Which "methods" of authentication are being compared? Or are you asking about the security of one key versus another? ... As for the complete history of authentication is concerned, if you've always had public key auth enabled and the other methods disabled, then public key is the historical past.
– RubberStamp
Nov 19 at 2:32
Damned if one does, damned if one doesn't. OK. Putting more than one question in one question.
– Calaf
Nov 19 at 3:17