cloud351
By:
cloud351

Console Access only - No incoming connections

October 15, 2015 1.2k views
Security Firewall Ubuntu

I am planning on creating some servers which don't require incoming connections.

They are simply worker servers. They will connect to other systems themselves, download work, perform it and upload the result. So nothing needs to connect to that server to make it work.

As such I want to firewall the server so that incoming connections are entirely blocked. My original plan was to leave SSH 22 open on the private network so I could connect to the server for updates, and maintenance, etc.

However would Console Access be more appropriate than leaving the SSH port open?

The downside to Console Access is having to use a password versus using an SSH key, but surely using Console Access is more secure, in that access is only via my control panel, and not exposed to any network access?

What would be the best strategy? Console Access only or leave SSH on private network?

Thanks

1 comment
  • The console is a secure option though it does require a password. It is also intended primarily for emergency or recovery purposes and doesn't support some things like copy/paste. Using ssh with key based authentication on a non-standard port will generally be just as secure and would be more user-friendly. Either option would work so in many ways it's just a matter of preference.

1 Answer

This question was answered by @ryanpq:

The console is a secure option though it does require a password. It is also intended primarily for emergency or recovery purposes and doesn't support some things like copy/paste. Using ssh with key based authentication on a non-standard port will generally be just as secure and would be more user-friendly. Either option would work so in many ways it's just a matter of preference.

View the original comment

Have another answer? Share your knowledge.