Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #14740 > unrolled thread
| Started by | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| First post | 2018-10-28 21:30 -0400 |
| Last post | 2018-10-28 21:30 -0400 |
| Articles | 1 — 1 participant |
Back to article view | Back to gnu.bash.bug
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [minor] umask 400 causes here-{doc,string} failure Chet Ramey <chet.ramey@case.edu> - 2018-10-28 21:30 -0400
| From | Chet Ramey <chet.ramey@case.edu> |
|---|---|
| Date | 2018-10-28 21:30 -0400 |
| Subject | Re: [minor] umask 400 causes here-{doc,string} failure |
| Message-ID | <mailman.2979.1540776612.1284.bug-bash@gnu.org> |
On 10/28/18 6:05 PM, Martijn Dekker wrote: > Unless I'm missing something, there should be no reason for an internal > temp file to have any permissions other than 0600 (user readable/writable), > so it seems to me that an fchmod call straight after creating the file and > before returning the fd is the simplest way of fixing the bug; this makes > the permissions of internal temp files entirely independent of the umask. That doesn't work for the same reason as discussed in http://lists.gnu.org/archive/html/bug-bash/2018-03/msg00074.html. It's unlikely that someone will set his umask to 400 and expect no ill effects, but I suppose it's better not to fail in the face of that kind of behavior. -- ``The lyf so short, the craft so long to lerne.'' - Chaucer ``Ars longa, vita brevis'' - Hippocrates Chet Ramey, UTech, CWRU chet@case.edu http://tiswww.cwru.edu/~chet/
Back to top | Article view | gnu.bash.bug
csiph-web