|
From: | James Youngman |
Subject: | [Bug-cssc] [bug #36269] "sccs create" loses execute permissions |
Date: | Mon, 28 Jul 2014 00:30:40 +0000 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.153 Safari/537.36 |
Update of bug #36269 (project cssc): Status: None => Fixed _______________________________________________________ Follow-up Comment #4: I reconsidered my previous position. It's least astonishing for us to treat execute bits as we do read bits; if the umask permits, the gotten file is world-readable; the previous mode of other files doesn't affect it. Hence if the history file is executable it's least surprising for the gotten file to be mode 0777 (modified by the umask). This is the Solaris behaviour. Setting world-execute permissions on the gotten file is unlikely to grant additional access to anybody since (subject to umask) they can read the gotten file anyway (hence copy it and chmod it themselves). I've implemented the feature: http://git.savannah.gnu.org/cgit/cssc.git/commit/?id=cb5e4ca42dc01103228d662911be5144da4cb2d5 _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?36269> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |