Not using IPTables. Using firewalld and yes, I opened the new port there as well.
Mike
On 07/09/2014 11:08 AM, Robert Moskowitz wrote:
On 07/09/2014 10:54 AM, Mike McCarthy, W1NR wrote: SELinux is not running. Any other ideas?
Did you update your IPTable? I change my SSHD port all the time.
One of
the first things I do on setting up a server. I know this is just obfusication, but it stops the robot noise. There are five steps:
edit /etc/ssh/sshd_config edit IPtables add ssh policy for new port restart sshd restart iptables
Mike
On 07/09/2014 10:50 AM, Mike McCarthy, W1NR wrote:
This was a "minimal" install for a virtual server and semanage is not available so the command doesn't work...
What package is semanage in?
Mike
On 07/09/2014 10:45 AM, Jonathan Billings wrote:
On Wed, Jul 09, 2014 at 10:35:12AM -0400, Mike McCarthy, W1NR wrote:
I am having a problem getting sshd to run after changing it's
default
port. I edit sshd_config and set the desired port, open it with firewall-cmd and then issue a systemctl start sshd. No error gets reported on the console but the following is logged in /var/messages
sshd.service: main process exited, code=exited, status=255/n/aNot a very helpful error message. Sounds like I should report a bug?
If you have SELinux enabled, it will block sshd from listening on a port other than what is described in the policy. You can add the additional port by running: semanage port -a -t ssh_port_t -p tcp $PORTNUM (replace $PORTNUM with the new port number you chose)
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos