[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 8/8] shell: restrict BASH_SOURCE_PATH when appropriate
From: |
Chet Ramey |
Subject: |
Re: [PATCH v2 8/8] shell: restrict BASH_SOURCE_PATH when appropriate |
Date: |
Wed, 15 May 2024 09:39:37 -0400 |
User-agent: |
Mozilla Thunderbird |
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 environments.
Or, at least, this should be an opt-in
feature that the scripts to set up the
restricted shells need to explicitly turn on
instead of being automatically enabled
through the existence of a variable BASH_SOURCE_PATH.
I think this is a very good idea, especially if we combine it with
the "no defaults" idea.
That would again require everyone to update whatever restricted shell
configuration they have now.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
- Re: [PATCH v2 6/8] builtins/source: use source path in isolated mode, (continued)
[PATCH v2 7/8] variables: define default BASH_SOURCE_PATH, Matheus Afonso Martins Moreira, 2024/05/13
[PATCH v2 8/8] shell: restrict BASH_SOURCE_PATH when appropriate, Matheus Afonso Martins Moreira, 2024/05/13