Turns out I have had a script ~/bin/CC in my path since circa 1980. cc plus some pleasant defaults. It has worked from UNIX v6 through v7, Eunice, BSD 4.1, 4.2, 4.3, SVr4, Xenix, Gould UTX, Linux, cygwin... and it failed for the first time on MacOS, infinite recursion.
I wondered if HFS+'s case insensitivity could be exploited for a security hole. Googling reveals that the problem has already been encountered article.gmane.org/gmane.linux.kernel/1853266itworld.com/article/2868393/… January 2015 Although fixed in Git, this is an exploit waiting to happen, for Mac users who have ever installed software from some other UNIX-like case-sensitive system. For that matter, it is probably a potential security hole for code ported from case sensitive iOS to Mac OS X. |
Why would Apple make this a format-time option - requiring a reformat / restore from backup to change?
ReplyDeleteMethinks it should be a per-process option. So it only has to be enabled for broken software such as that from Adobe.
Possibly with a filesystem permissions bit - although probably just as well to have in an executable header.
There seems to be widesopread recognition that developers should enable case sensitivity, to prevent bugs from multiplying.