Some Background:
The setuid bit:
The setuid bit on a executable file makes it so executables that are run by any user, are run as if they were being run by the owner of the executable. So if setuid is set on a program that is owned by root, no matter who runs it, it will be run with root privileges. It is of course not that simple, see this wikipedia article, or get a copy of Steven's Programing in the Unix Environment.
A Core Dump:
A core dump is a dump of the program's working memory to a file. See this wikipedia article.
suid_dumpable:
This controls if the core can be dumped from a setuid program as described above. See below. This is a kernel tunable, you can change it with:
sudo sysctl -w kernel.suid_dumpable=2
You would find out about this tunable in documentation for your sourcode, which if installed, you might find in a directory like: /usr/src/linux-source-2.6.27/Documentation/sysctl/ . In this case, the reference below is in fs.txt in that directory. Use the uname -a command to find out your kernel version.
Why it Matters:
It could be a security risk:
So the idea is, if there are core dumps and a regular user can read them, they might find out privileged information. If the program is dumped well it had privileged information in memory, and the user can read the dump, they might find out that privileged information.
Reference:
This value can be used to query and set the core dump mode for setuid
or otherwise protected/tainted binaries. The modes are
0 - (default) - traditional behaviour. Any process which has changed
privilege levels or is execute only will not be dumped
1 - (debug) - all processes dump core when possible. The core dump is
owned by the current user and no security is applied. This is
intended for system debugging situations only.
2 - (suidsafe) - any binary which normally not be dumped is dumped
readable by root only. This allows the end user to remove
such a dump but not access it directly. For security reasons
core dumps in this mode will not overwrite one another or
other files. This mode is appropriate when adminstrators are
attempting to debug problems in a normal environment.
This comes close:
stat -l -t "%F %T %z" *
but without the sort, columns don't line up and the nanoseconds aren't included. Plus the syntax for file selection is different and other options for ls aren't available or are different.
This one might be closer:
find . -maxdepth 1 -printf "%M %n %-6u %-6g %6s %TY-%Tm-%Td %TT %TZ %f\n"|sort -k 9
In Mac OSX, gfind is needed (brew install gfind) (and note that the granularity will only be in whole seconds):
gfind . -maxdepth 1 -printf "%M %n %-6u %-6g %6s %TY-%Tm-%Td %TT %TZ
%f\n"|sort -k 9
Best Answer
info ls shows: