| I see this as an instance of a non-conforming environment as described in: It was the case in the past that we did not deal with 0, 1, 2 being closed, but now we do, at least for set*id executables. The fact that the documentation explicitly does not call having argc != 0 and argv[0] pointing to valid memory out *yet* as a requirement does not mean that we should not make the world a safer place and enforce it. I see it simply as putting a check in one place instead of forcing everyone to be check for it. It is good hygiene. Best, christos |
Attachment:
signature.asc
Description: Message signed with OpenPGP