I added

PermitRootLogin no

to my /etc/ssh/sshd_config file and I can still log in via root without issues. I restarted services and even rebooted.

Anyone have any help for me?

ssh daemon searches include /root and /home/name so if you have them....disable them with root powers.

And I assume you editted your /etc/ file with root powers?

Explain what you mean by that exactly.

Yes I edited the /etc/ file while logged in as root.

I am not sure what you mean by disable /root and /home/name with root powers, can you go into a bit more detail for me?


aus9:
I can still directly ssh into my box using the root credentials. I want to disable direct root logins for security purposes. I would like to only be able to log in via a user the be able to su - or sudo if needed.

You say you added this; did you remove any lines that contradicted it? Check for other PermitRootLogin lines.

I checked and there are none. Any other ideas?

As root, edit the file /etc/sshd_config. Add a line that says:

AllowUsers yourusername

Make sure there is no line that says:

AllowUsers root


Hope this helps! :-)

No it did nothing... Just to let you know this happened after following the chrootjail instructions here:
http://adamsworld.name/chrootjail.php

Did you restart ssh with /etc/init.d/ssh restart?

Not exactly, there is not such file


[root@bighat ~]# /etc/init.d/ssh restart
-bash: /etc/init.d/ssh: No such file or directory
[root@bighat ~]# /etc/init.d/sshd restart
Stopping sshd: [ OK ]
Starting sshd: [ OK ]
[root@bighat ~]#


I dont know if there is a different between ssh and sshd


And I can still log in via ssh with root credentials.

This is probably an important clue as to why the problem is occurring.

Note that only the PermitRootLogin no directive is required to prevent ssh root@some.host from working. The additional AllowUsers directive is fine, but it is not necessary since there is already a directive that should do exactly what you want.

It's likely that your sshd daemon inside the chrooted environment is not properly reading its /etc/ssh/sshd_config file. (In fact, I question that howto; I don't see that he is moving any sshd_config file into the chrooted environment.)

My short answer is: Don't bother chrooting the sshd daemon. It's a subpar 'security' feature. A better alternative is to put sshd in a Linux-VServer if you want to contain users.

You do not need to move the sshd_config file into the chrooted environment. The user does not need access to this file or any other binaries or config files.
Because this only allows for SFTP, they do not need access to such things.

The user will see the dir structure as something like this(will vary depending on what you let them do with it)

Thats it. They don't need anything else.

Also the original problem here is that the tutorial doesnt use the 'stock' install version of openssh. It installs into the /opt directory and therefore all paths would now be relative to that.

If you notice anything blatantly wrong please let me know as I am not an expert, its just that there wasn't enough information about how to do this easily so I copied my working procedure (and tested it).

-Adam