Commands execution from php, idea(s) how to restrict from code consumer's scope
Open
Nobody has claimed this yet.
Feature
Status: Needs Triage
- Dominant language
- C
- Stars
- 40.4k
- Forks
- 8.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 96
Description
Description
The original discussion stemmed from there.
Basically how to, more effectively, restrict php process user access to system commands. Albeit the implementation idea had been rejected, for valid reasons, it should not stop to improve in this area. Note that calls like execvP allows to enforce specific search paths but is even less standard than execvpe.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Begin with the linked externals.io discussion and the issue's references to execvP and execvpe. Compare the stated goal of restricting PHP process access to system commands with the limitations of these APIs, then document a concrete, technically justified direction and its scope.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, php
- Domain
- operating-systems, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100