Documentation/binfmt-misc.rst: Specify aux vector for "O" flag description
Subsystems (3)
PATCH 1/1 Documentation/binfmt-misc.rst: Specify aux vector for "O" flag description
Instead of replacing the file path in the argument vector, the file descriptor is passed as AT_EXECFD in the auxilary vector. This appears to have been the case at least since the git port, update the documentation to reflect this.
Signed-off-by Charlie Jenkins <[email protected]>
--- Documentation/admin-guide/binfmt-misc.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
Documentation/admin-guide/binfmt-misc.rst +4 -4
@@ -68,10 +68,10 @@ Here is what the fields mean: Legacy behavior of binfmt_misc is to pass the full path of the binary to the interpreter as an argument. When this flag is included, binfmt_misc will open the file for reading and pass its - descriptor as an argument, instead of the full path, thus allowing - the interpreter to execute non-readable binaries. This feature - should be used with care - the interpreter has to be trusted not to - emit the contents of the non-readable binary. + descriptor into the auxilary vector with the key "AT_EXECFD", thus + allowing the interpreter to execute non-readable binaries. This + feature should be used with care - the interpreter has to be trusted + not to emit the contents of the non-readable binary. ``C`` - credentials Currently, the behavior of binfmt_misc is to calculate the credentials and security token of the new process according to
---
base-commit: 028ef9c96e96197026887c0f092424679298aae8
change-id: ${change-id}
- Charlie
Quoted 9 lines · Charlie Jenkins
Instead of replacing the file path in the argument vector, the file descriptor is passed as
AT_EXECFDin the auxilary vector. This appears to have been the case at least since the git port, update the documentation to reflect this.Signed-off-by Charlie Jenkins <[email protected]>--- Documentation/admin-guide/binfmt-misc.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
Applied, thanks.
jon