On 5/14/24 6:22 PM, Matheus Afonso Martins Moreira wrote:
Or you could simply ignore BASH_SOURCE_PATH in restricted mode.
Then the restricted shells will not have access to this new functionality.
I thought it could be useful if properly integrated.
It would require updating all restricted en
> Or you could simply ignore BASH_SOURCE_PATH in restricted mode.
Then the restricted shells will not have access to this new functionality.
I thought it could be useful if properly integrated.
> Or, at least, this should be an opt-in
> feature that the scripts to set up the
> restricted shells n
2024年5月15日(水) 4:55 Chet Ramey :
> On 5/13/24 6:37 AM, Matheus Afonso Martins Moreira wrote:
> > Make the BASH_SOURCE_PATH variable read-only and unsettable
> > when the shell is operating in restricted mode. This variable
> > should be restricted for the same reasons why PATH is restricted.
>
> Or
On 5/13/24 6:37 AM, Matheus Afonso Martins Moreira wrote:
Make the BASH_SOURCE_PATH variable read-only and unsettable
when the shell is operating in restricted mode. This variable
should be restricted for the same reasons why PATH is restricted.
Or you could simply ignore BASH_SOURCE_PATH in re
Make the BASH_SOURCE_PATH variable read-only and unsettable
when the shell is operating in restricted mode. This variable
should be restricted for the same reasons why PATH is restricted.
Signed-off-by: Matheus Afonso Martins Moreira
---
shell.c | 1 +
1 file changed, 1 insertion(+)
diff --git
