Timeline for Is starting an AWS instance with only ssh to port 22 significantly insecure?
Current License: CC BY-SA 4.0
27 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 29, 2020 at 3:20 | answer | added | R.. GitHub STOP HELPING ICE | timeline score: 0 | |
| S Jun 28, 2020 at 15:57 | history | suggested | Nemo | CC BY-SA 4.0 |
Fix typo in title
|
| Jun 28, 2020 at 15:04 | review | Suggested edits | |||
| S Jun 28, 2020 at 15:57 | |||||
| Jun 28, 2020 at 8:18 | comment | added | Andrew Savinykh | "I prefer to not need to indicate their source IP addresses in advance". You do not have to do that in advance. Ask them the IP they are going to access the server from, at the same time you receive their public key from them. If you consider this a part of setting up a user access, it can be followed quite naturally. | |
| Jun 28, 2020 at 8:14 | answer | added | Pedro Lobito | timeline score: 0 | |
| Jun 28, 2020 at 0:00 | answer | added | eckes | timeline score: 0 | |
| Jun 27, 2020 at 19:57 | history | edited | WestCoastProjects | CC BY-SA 4.0 |
edited title
|
| Jun 27, 2020 at 13:18 | answer | added | tankmek | timeline score: 0 | |
| Jun 27, 2020 at 1:35 | answer | added | Criggie | timeline score: 6 | |
| Jun 27, 2020 at 1:00 | answer | added | Ángel | timeline score: 2 | |
| Jun 27, 2020 at 0:55 | answer | added | TrypanosomaBruceii | timeline score: 0 | |
| Jun 26, 2020 at 21:05 | comment | added | GuilleOjeda | Not an answer to your question, but you might be interested in knowing that you can connect through SSH using Systems Manager without opening port 22 to public IPs and without using an SSH key | |
| Jun 26, 2020 at 19:52 | answer | added | Captain Man | timeline score: 4 | |
| Jun 26, 2020 at 19:17 | comment | added | JesseM | @jcaron 's comment above should get more attention. Don't distribute "the" (singular) key the AWS instance generates. Have each user have their own public key added to the host. Not strictly addressing the topic of the question, but important. | |
| Jun 26, 2020 at 19:14 | answer | added | Paul Draper | timeline score: 2 | |
| Jun 26, 2020 at 18:51 | answer | added | Peter Green | timeline score: 1 | |
| Jun 26, 2020 at 13:32 | comment | added | jcaron | "The ssh key would be distributed"? Erm, no. Each user/computer combination should have their own key. It should really be generated by each user, and their public key set up on their account on the server. | |
| Jun 26, 2020 at 10:08 | comment | added | marcelm | I feel going from "We recommend ... to only allow access from known IP adresses" (amazon) to "trivially insecure" (question title) is a bit of a leap there ;) | |
| Jun 26, 2020 at 9:37 | comment | added | David Tonhofer | "Unless someone has my private ssh key, how is leaving an aws instance open to 0.0.0.0 but only on port 22 via ssh insecure?" It is not, unless your SSH server has bugs that can be exploited (not unheard of, remember the OpenSSH hacks of 2003 or so) or is badly configured. It's interesting to leave it on port 22 though, you will get immediate brute-forcing attempts from notorious IP addresses. The AWS text is standard lawyer-proofing. | |
| Jun 26, 2020 at 8:12 | answer | added | iBug | timeline score: 31 | |
| Jun 26, 2020 at 4:52 | history | became hot network question | |||
| Jun 26, 2020 at 0:00 | history | tweeted | twitter.com/StackSecurity/status/1276304191359717376 | ||
| Jun 25, 2020 at 21:51 | history | edited | WestCoastProjects | CC BY-SA 4.0 |
edited title
|
| Jun 25, 2020 at 21:22 | vote | accept | WestCoastProjects | ||
| Jun 25, 2020 at 21:20 | answer | added | Demento | timeline score: 37 | |
| Jun 25, 2020 at 20:55 | review | First posts | |||
| Jun 25, 2020 at 22:20 | |||||
| Jun 25, 2020 at 20:51 | history | asked | WestCoastProjects | CC BY-SA 4.0 |