I have updated PermitRootLogin in /etc/ssh/sshd_config to no and issued a service ssh restart (multiple times) and I can still login via SSH as root using a public key. This should be blocked correct?
I have read the related Q&As here and various others from a Google Search. As far as I can tell I’ve done the right thing but I can still login.
root@infra:~# cat /etc/ssh/sshd_config | grep PermitRootLogin
PermitRootLogin no
# the setting of "PermitRootLogin yes
root@infra:~#
Restarting ssh returns no errors, etc.
root@infra:~# service ssh restart
root@infra:~#
PasswordAuthentication is also set to no (although root never had a password – started with a pub key installation) and for good measure UsePAM is set to no.
Love any suggestions!
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Accepted Answer
FYI re. a solution. Restarting the service didn’t cause the new settings to take effect. Rebooting the server did. No idea why that is the case.
for me, i had
ControlMaster auto
ControlPath ~/.ssh/sockets/%r@%h-%p
set in my ~/.ssh/config deleting the control path directory fixed the issu
OK, even stranger … I delete the .ssh directory from the root user using my sudo user. I can still login in as root on that machine even after a service ssh restart.
Mystified!
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.