Merge lp:~andreserl/maas/maas_correct_paths into lp:~maas-committers/maas/trunk
Proposed by
Andres Rodriguez
Status: | Merged |
---|---|
Approved by: | Andres Rodriguez |
Approved revision: | no longer in the source branch. |
Merged at revision: | 1030 |
Proposed branch: | lp:~andreserl/maas/maas_correct_paths |
Merge into: | lp:~maas-committers/maas/trunk |
Diff against target: |
14 lines (+2/-2) 1 file modified
src/maasserver/models/node.py (+2/-2) |
To merge this branch: | bzr merge lp:~andreserl/maas/maas_correct_paths |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Scott Moser (community) | Approve | ||
Review via email: mp+125286@code.launchpad.net |
Commit message
Set correct paths for virsh and ipmipower
To post a comment you must log in.
I grudgingly approve this.
However, the right fix to this problem is to *NOT* specify full paths.
Trust your environment instead. By trusting the PATH environment variable to contain the right paths, you get:
* the ability to easily replace a program with a preferred version in a different path
* the stability to not fail when a program is not in the hard coded path
* no reduced security
I'm sure that the reader of this rant might for some strange reason believe that hard coding paths provides a sense of security. That is, however, extremely flawed belief. If a attacker has influenced the environment of your process, you're already compromised and hard coding strings will not help you. If I could influence the environment of your process, i could set LD_PRELOAD and modify 'open' or 'execve' to do what i wanted.
Please stop doing silly things.