Shell scripts require executable permission - prior ubuntus and unix do not
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
Invalid
|
Undecided
|
Unassigned |
Bug Description
This problem started with 10.10 Beta, It is now in 10.10 RC and I have noticed that latest 10.04 has picked up updates make it behave incorrectly also
I am following up on a possible deficiency of 10.10 RC - in this distribution shell scripts must be set to executable before the context menu offers the 'Open' (with dialog to confirm that you want to execute a script). This is contrary to normal ubuntu and unix practice.
10.10 RC does not offer the 'Open' if the script does not have the executable bit on. The new version does offer the 'Open' and the dialog if the script file is flagged as executable.
The possible package is Nautilus -
I have tried this problem in:
1.OpenSolaris,
2.Ubuntu 9.04
3.Fedora 11.
4.Mandrake 8
5.Suse 11.
6.As well as in the unix compatible MacOS and Windows XP Unix Shells.
What I expect is that scripts with '#!xxxx (xxxx is shell path) should not required to have the executable bit on to offer the 'Open' context menu (with dialog for script execution)
All shell scripts of any kind suffer this problem (perl, python, bash, etc).
What happens instead:
1. the context menu for the file only offers an 'open text edit',
2. when the executable bit is on, may be the dialog should ask for root permission (which should be remembered in a thread of shell calls.
3. Files with .EXE, .COM, .BAT are not required to have the executable bit on and the context menu works. THIS IS A SECURITY VULNERABILITY
On Ubuntu, this is by design. See:
https:/ /wiki.ubuntu. com/SecurityTea m/Policies# Execute- Permission% 20Bit%20Require d
This isn't an issue.