On 05/04/2018 04:42 PM, John Florian wrote:
On 2018-05-04 09:33, Stephen John Smoogen wrote:
I would do so for the following reasons:
1. Even though the security arguments are weak, they are going to be
checkmarks on audits which can't be changed for years.
2. When someone gets a "remove this and find out why the OS did this"
it helps if they can point to an "official" change versus an email.
This is an excellent point. Chasing the history of such changes through
myriad email is always frustrating, especially since it's often
inconclusive of what actually did happen.
Just checking my own PATH, I see some surprising things at the front:
$ echo $PATH
/usr/libexec/python3-sphinx:/usr/lib64/qt-3.3/bin:/usr/lib64/ccache:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin
I love Sphinx and Qt, but what are they doing there ... at the front?
Ditto. And *libexec* at that. libexec by definition is "internal
binaries that are not intended to be executed directly by users or shell
scripts", so it really does not belong in anybodys PATH.
- Panu -
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
