You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hledger run does not yet support run commands itself. This prevents the use of re-usable scripts which can be embedded in multiple calls. That said, it may be worth thinking about whether this functionality would open security holes which could be exploited. What could a maliciously constructed (recursive?) run script do, and how would it be protected against?
echo "balance assets" > test.cmd
echo "run test.cmd" > nested.cmd
hledger run test.cmd
hledger run nested.cmd
The text was updated successfully, but these errors were encountered:
adept
added a commit
to adept/hledger
that referenced
this issue
Feb 23, 2025
Thanks, this seems like a straightforward thing to fix. While it is true that a user could construct a series of co-recursive invocations that loop forever, i feel that people should be allowed to shoot themselves in a foot if they want to :)
adept
added a commit
to adept/hledger
that referenced
this issue
Feb 23, 2025
hledger run
does not yet supportrun
commands itself. This prevents the use of re-usable scripts which can be embedded in multiple calls. That said, it may be worth thinking about whether this functionality would open security holes which could be exploited. What could a maliciously constructed (recursive?) run script do, and how would it be protected against?The text was updated successfully, but these errors were encountered: