'ls' does not report info on root directory '/' about sliver HOT 5 CLOSED

I must be missing something obvious, but your listing of / (last snippet) shows the permissions and last modified time of the directories in the / directory. What do you think is missing exactly?

from sliver.

What is missing is the permissions and modified time of the ‘/‘ directory itself. Not the things inside it.

For example, it’s not currently known if ‘/‘ is world writable.

from sliver.

Ok I get it now, I was confused by the additional info not showing any difference between the two examples (/ vs /etc/rsyslog.d). Right now we're calling os.ReadDir() on the provided path (well, when it's a directory), which doesn't return anything for the root element of the path itself.
For a quick sanity check, I just tested with /bin/ls on MacOS and /usr/bin/ls on an Ubuntu 22.04 box and I'm not getting any details about the root element either when doing /bin/ls /. So at least we seem to be consistent with the system's ls binary, unless once again I'm missing some context here.

When you say:

It should be possible to see modified time of '/' directory using ls and not relying on something like execute.

Do you have an example of the command you're using with execute to get a different result than what the built-in ls command does?

EDIT: nevermind I'm not fully awake yet, ls -la will not ignore . and this is the way to get the info with the system's ls binary.

from sliver.

A potential solution could be to add a . entry on Unix/Linux systems that fetches the info of the inode matching the requested directory entry (top/root level).

from sliver.

Adding the '.' entry would be awesome! It would prevent needing additional runs of 'ls' and should be easy to parse.

from sliver.