Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [PATCH] make sure internal temp files are user readable and writeable
- X-seq: zsh-workers 42535
- From: Stephane Chazelas <stephane.chazelas@xxxxxxxxx>
- To: Martijn Dekker <martijn@xxxxxxxx>
- Subject: Re: [PATCH] make sure internal temp files are user readable and writeable
- Date: Mon, 26 Mar 2018 18:00:44 +0100
- Cc: Zsh hackers list <zsh-workers@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=qEiV+CBXnjJeIKQh1dxfvgTL+JdvEpAQuEhI0aEwj9o=; b=aoF5IsU8EB37+3R117utKKj9WPATJqA6zSV2JxMmMokU8+V+JHZ+hkEvOhett+K/mq au4G+VT+86rx57nvzQmtNDGA4GOmi/N5yxibqfEo9rUtomesyQYhHuFTjMArHymEtGcJ 7gOOr5/OOCdkIb2yTsGK8uqNMEobjyE0KRhHuZep+jCc410U7KeJx7DPIPxLEIjnLYiv hdKfD6qOX7y4+EdefamLLijKzpJDgl6Np8uE2R2oFI5EJm0bNX0Vmp+hm+N0gXAAJCin zzXA5t+O4LxPK2OzGAJjvBE03Wx5eBXx6xC4xcNgINS9OVGILsK5Rlq5ijfWTFjwQ7rH x2zg==
- In-reply-to: <581009fe-372c-641a-cf5f-87e6a2a68dbb@inlv.org>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- List-unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
- Mail-followup-to: Martijn Dekker <martijn@xxxxxxxx>, Zsh hackers list <zsh-workers@xxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <581009fe-372c-641a-cf5f-87e6a2a68dbb@inlv.org>
2018-03-26 18:45:23 +0200, Martijn Dekker:
> Here-documents fail if the umask does not allow user reading.
>
> $ zsh -c $'umask u-r; cat <<EOF\nEOF'
> zsh:1: can't create temp file for here document: permission denied
[...]
> + mode_t old_umask = umask(0177);
[...]
Thanks. See also 42446
(https://www.zsh.org/mla/workers/2018/msg00252.html)
with other suggested options.
There I mentioned the potential need to block signals between
the time the umask is changed temporarily and when it's restored
(to avoid traps running with the wrong umask (0177 instead of
the user's requested one)).
--
Stephane
Messages sorted by:
Reverse Date,
Date,
Thread,
Author