Moving Sshd Listen Port
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%5/n/a
Not a very helpful error message. Sounds like I should report a bug?
Thanks, Mike
—–BEGIN PGP SIGNATURE—
Recommended
Recent Posts
Recent Comments
- igor on LibGLU.so.1
- Hussein on NBDE, Clevis And Tang For Non-root Disk
- João M. S. Silva on CentOS 7.6 1810 Vs. VirtualBox : Bug With Keyboard Layout Selection
- Jim Plumb on Spamassassin Vs. SELinux Trouble
- woodiskingser on Off Topic – Need Help Registering To The Smplayer Forum
Archives
- April 2024
- March 2024
- February 2024
- January 2024
- December 2023
- November 2023
- September 2023
- August 2023
- July 2023
- June 2023
- May 2023
- April 2023
- March 2023
- February 2023
- January 2023
- December 2022
- November 2022
- October 2022
- September 2022
- August 2022
- July 2022
- June 2022
- May 2022
- April 2022
- March 2022
- February 2022
- January 2022
- December 2021
- November 2021
- October 2021
- September 2021
- August 2021
- July 2021
- June 2021
- May 2021
- April 2021
- March 2021
- February 2021
- January 2021
- December 2020
- November 2020
- October 2020
- September 2020
- August 2020
- July 2020
- June 2020
- May 2020
- April 2020
- March 2020
- February 2020
- January 2020
- December 2019
- November 2019
- October 2019
- September 2019
- August 2019
- July 2019
- June 2019
- May 2019
- April 2019
- March 2019
- February 2019
- January 2019
- December 2018
- November 2018
- October 2018
- September 2018
- August 2018
- July 2018
- June 2018
- May 2018
- April 2018
- March 2018
- February 2018
- January 2018
- December 2017
- November 2017
- October 2017
- September 2017
- August 2017
- July 2017
- June 2017
- May 2017
- April 2017
- March 2017
- February 2017
- January 2017
- December 2016
- November 2016
- October 2016
- September 2016
- August 2016
- July 2016
- June 2016
- May 2016
- April 2016
- March 2016
- February 2016
- January 2016
- December 2015
- November 2015
- October 2015
- September 2015
- August 2015
- July 2015
- June 2015
- May 2015
- April 2015
- March 2015
- February 2015
- January 2015
- December 2014
- November 2014
- October 2014
- September 2014
- August 2014
- July 2014
- June 2014
- May 2014
- April 2014
- February 2014
- January 2014
- April 2013
- December 2012
17 thoughts on - Moving Sshd Listen Port
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)
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
—–BEGIN PGP SIGNATURE—
SELinux is not running. Any other ideas?
Mike
—–BEGIN PGP SIGNATURE—
SELinux is not running. Any other ideas?
Mike
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
Not using IPTables. Using firewalld and yes, I opened the new port there as well.
Mike
Checking the firewall is useful, but it sounds like you can’t get the service to start in the first place.
It might be helpful if you gave us the full error output. Do you get more information by running:
systemctl status -l sshd.service
… after running the systemctl start?
Hi Mike
Can you run sshd manually in debugging mode and paste the output please:
$ /usr/sbin/sshd -d
It’s worth looking at the output of strace that may help here:
$ strace /usr/sbin/sshd
-V
Nothing more than what was in messages namely ‘code=exited, status%5/n/a’ which looks an awful lot like a printf of an uninitialized variable…
Mike
Had to dig back in my notes:
policycoreutils-python
Are you sure? (It’s enabled by default.)
What does ‘getenforce’ say?
/usr/sbin/sshd -d seems to work properly and accept connections at the new port. So does typing /usr/sbin/sshd, which daemonizes and runs manually. It now appears that it will not start as a service if I change the port, even after a reboot.
Mike
# yum provides ‘*/semanage’
It’s in policycoreutils-python.
Well, getenforce says enforcing but ‘systemctl status selinux’ says
‘Active: inactive (dead)’ ?
Mike
Yum will tell you:
yum provides */semanage
Sounds like you have SELinux enabled. It’s not a service. If you look at the line right above the Active line you pasted, you’d see a line that said:
“Loaded: not-found (Reason: No such file or directory)”
It’ll say that about anything that doesn’t actually exist:
# systemctl status selinux selinux.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
# systemctl status asasdklfjhaskdfhj asasdklfjhaskdfhj.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)
I suggest installing the policycoreutils-python package and run the semanage command I mentioned earlier.
What does ‘journalctl -u sshd.service’ say?