Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #12041
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: [PATCH/RFC] do not source/exec scripts on noexec mount points |
| Date | 2015-12-16 15:42 -0500 |
| Message-ID | <mailman.51.1450298563.843.bug-bash@gnu.org> (permalink) |
| References | <1449954086-30408-1-git-send-email-vapier@gentoo.org> <CAJnmqwZcZOTjXAVJO7vixSEQf2eEUuZocBzMKdpK08zAphzbLQ@mail.gmail.com> <20151214051712.GS11489@vapier.lan> <5671C856.5030404@case.edu> <CAAJSdjgkB8i5_jqReMquR0_zpAoX_9YJ4_mcO7m3EjfX3pn=5Q@mail.gmail.com> |
On 12/16/15 3:29 PM, John McKown wrote: > FWIW (not much), I'm going to go with Chet on this. It may be my ignorance > speaking, but what can I do in a BASH shell script which I cannot do (at > all) just by entering the commands by hand? That's where the scope of the proposal makes a difference. If it's intended for captive systems where the user does not have direct access to the shell or the file system, that's a different thing than a general purpose system. Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, ITS, CWRU chet@case.edu http://cnswww.cns.cwru.edu/~chet/
Back to gnu.bash.bug | Previous | Next | Find similar
Re: [PATCH/RFC] do not source/exec scripts on noexec mount points Chet Ramey <chet.ramey@case.edu> - 2015-12-16 15:42 -0500
csiph-web