A NOTE has been added to this issue. 
====================================================================== 
https://austingroupbugs.net/view.php?id=1435 
====================================================================== 
Reported By:                zackw
Assigned To:                
====================================================================== 
Project:                    1003.1(2016/18)/Issue7+TC2
Issue ID:                   1435
Category:                   System Interfaces
Type:                       Error
Severity:                   Objection
Priority:                   normal
Status:                     New
Name:                       Zack Weinberg 
Organization:               GNU 
User Reference:              
Section:                    exec 
Page Number:                (unknown) 
Line Number:                (unknown) 
Interp Status:              --- 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2020-12-15 14:50 UTC
Last Modified:              2020-12-15 15:45 UTC
====================================================================== 
Summary:                    execlp and execvp should not execute a command
interpreter when other members of the exec family would fail with ENOEXEC
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0001226 shell can not test if a file is text
====================================================================== 

---------------------------------------------------------------------- 
 (0005175) geoffclare (manager) - 2020-12-15 15:45
 https://austingroupbugs.net/view.php?id=1435#c5175 
---------------------------------------------------------------------- 
Re https://austingroupbugs.net/view.php?id=1435#c5174

No, only execl, execle, execv, and execve are expected not to invoke a
shell. The execlp and execvp functions have always invoked a shell if the
file cannot be executed directly and are very much expected to do so.
Changing this would break a huge number of applications which rely on them
executing a shell in cases where the shell script does not start with #! or
the system does not support #!, including every strictly conforming
application that includes a shell script to be executed using execlp or
execvp (since strictly conforming applications cannot use #!) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2020-12-15 14:50 zackw          New Issue                                    
2020-12-15 14:50 zackw          Name                      => Zack Weinberg   
2020-12-15 14:50 zackw          Organization              => GNU             
2020-12-15 14:50 zackw          Section                   => exec            
2020-12-15 14:50 zackw          Page Number               => (unknown)       
2020-12-15 14:50 zackw          Line Number               => (unknown)       
2020-12-15 15:22 geoffclare     Note Added: 0005173                          
2020-12-15 15:22 geoffclare     Relationship added       related to 0001226  
2020-12-15 15:31 zackw          Note Added: 0005174                          
2020-12-15 15:45 geoffclare     Note Added: 0005175                          
======================================================================


  • [1003.1(2016... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group

Reply via email to