On 5/18/24 8:57 PM, Robert Elz wrote:
Date: Sat, 18 May 2024 23:00:41 +0000 From: Matheus Afonso Martins Moreira <math...@matheusmoreira.com> Message-ID: <dR9S605H035mFA4Mw-zMDA14EDUmIvWa1o1gFU_od76uOQJmf-y7ovpEAdpXWttQemhpexDfs3-1oL3PKJlRgT2MwLoTiMvIv4q_WfNUOPY=@matheusmoreira.com>| If you resolve the path, you're just reinventing the source builtin. Nonsense, the real work of the source ('.' really) utility is to read the file, parse it, and execute it. None of the proposed solutions here do that. What file names work for this purpose is an irrelevant consideration. | It also depends on source actually accepting the absolute path | which renders it incompatible with restricted shells. That's the only point here that has any merit. And a better solution to that would be to remove that restriction, which has no purpose that I can imagine.
It's present because it's always been part of restricted shells. The
historical Bourne shell and Korn shell lines both have it.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU c...@case.edu http://tiswww.cwru.edu/~chet/
OpenPGP_signature.asc
Description: OpenPGP digital signature
