Shut up llvm's "fortify" about not checking the fscanf() return value.
We already confirm that the sender is another toysh instance (the
ppid!=getppid() line), set the variables to zero before reading (which
should stay zero if it can't read that field, and len 0 causes the loop
to exit), and then we error_exit() if we can't read the requested length.
That should handle the sender exiting unexpectedly (probably via signal).
Outright malicious data going across the pipe could tell the subshell to
"rm -rf ~", that's a "you've already lost" scenario more checks wouldn't help.
1 file changed
