I must admit that I don't entirely grasp the scope of the issue you're raising with /home living on a networked filesystem (sorry).
* Is your concern a security one, where a malicious user gaining access to the network file server could potentially inject badness in various users ~/bin?
* Or is it a performance concern, in that we're adding a search in PATH on a remote filesystem?
* ...?
In the mean time, I have a simple, one-line patch that adds ~/bin to the end of the initial PATH definition in /etc/environment.
Depending on Kees' explanation of his concerns, I can add some additional logic to libpam-modules.postinst to affirm that no user's ~bin is on a networked filesystem at /etc/environment creation time.
Hey Kees-
I must admit that I don't entirely grasp the scope of the issue you're raising with /home living on a networked filesystem (sorry).
* Is your concern a security one, where a malicious user gaining access to the network file server could potentially inject badness in various users ~/bin?
* Or is it a performance concern, in that we're adding a search in PATH on a remote filesystem?
* ...?
In the mean time, I have a simple, one-line patch that adds ~/bin to the end of the initial PATH definition in /etc/environment.
Depending on Kees' explanation of his concerns, I can add some additional logic to libpam- modules. postinst to affirm that no user's ~bin is on a networked filesystem at /etc/environment creation time.
:-Dustin