CPANEL-35592 - Jailed shell users can't access manual pages.
When a jailed shell user try access a man page, like:
$ man ls man: can't open the manpath configuration file /etc/man_db.conf
I don't think this is a problem with permissions:
$ ls -la /etc/man_db.conf -rw-r--r-- 1 root root 5.1K Oct 30 2018 man_db.conf
I can't figure out why an jailed shell user can't access manual pages.
-
Hey there! Thank you for bringing this to our attention. It appears that jailed shell users are unable to access the manual pages as /etc/man_db.conf is not included in the default VirtFS configuration. We've filed an internal case regarding this issue with our development team, CPANEL-35592. You can find updates regarding this case in our changelogs: 0 -
It's possible I make changes on this VirtFS configuration? Because maybe I can put another files on this configurations, like /etc/nanorc, or another global file configurations to jailed users. 0 -
It is possible to make changes to the VirtFS configuration, although this would require the use of custom jailed shell mounts. We do have some documentation on setting up custom jailed shell mounts here:
Thank you, I already voted on this feature request. I had also seen the custom moint points, thanks, but like already said on comment: create a custom mount point just for add some global configuration files on /etc, like: nanorc, toprc, or another unimportant but useful configuration file it's the worst kind "work around" solution. I'll try await for this feature =)0 -
The issue with the man pages has been resolved and will be included as part of cPanel version 94 :D 0 -
It still exists or has reappeared in version 100, or at least I have a web hosting account with SSH Access using jail shell and I don't have "man". 0 -
It still exists or has reappeared in version 100, or at least I have a web hosting account with SSH Access using jail shell and I don't have "man".
Can you confirm the exact steps necessary to replicate this issue? I put my cPanel user in a jailed shell on version 100, then attempted to run the "man" command. It seems to work just fine for me.0
Please sign in to leave a comment.
Comments
7 comments