You'll notice
Useful3 Signal2
Bash commands reading from a file with < no longer trigger a separate read-permission prompt.
What's wrong with this entry?
Anonymous. No account, no email.
What
The Bash permission path no longer inspects < input redirection targets. The loop that skipped /dev/null and evaluated each redirection source as a file read, along with its deny and ask messages, is gone.
Details
- "Input redirection from" appeared three times in the previous build and does not appear here; the matching "Output redirection to" checks are unchanged.
- Whether an equivalent read check now runs somewhere else in the permission path is not determinable from the shipped code.
Evidence
Input redirection from
Strings lifted out of the shipped bundle, so the claim above can be checked against them.