On Tuesday February 28 2017 22:34:46 Jeremy Huddleston Sequoia wrote: >> Oddly enough, no. You can even copy /bin/sh to a different path and run it >> and it will lose many of its protections (recent MacPorts trace mode even >> knows and uses this!). An example of what I said above. Seems an odd way to >> do things to me, and I'm far from being a security expert. > >You can also install /usr/local/bin/sh (as zsh or some newer GPLv3 bash or >pdksh if that's your schtick) and setup your scripts to use '#!/usr/bin/env >sh' instead of '#!/bin/sh'
In terms of getting stuck, I did that almost a lifetime on tcsh. I was quite thrilled to see an update to it, a month or so ago. I built the shell from port:tcsh, but then copied it and its dependencies to /usr/local and used install_name_tool so everything works as if it were meant to be installed under /usr/local, and then made it my login shell. IIRC I had to add the executable to a file, possibly /etc/shells. Would that approach still work under newer OS versions? If so one ought to be able to do the same with bash. > Interesting idea. File a radar. I suspect that it's been mentioned before, > but +1 never hurts. Roger, I'll add it to the list of radars to file. I'd hope indeed that someone else thought of this before, anyone who's ever got a bit hands-on with MS Windows must have encountered this kind of approach. R. _______________________________________________ Do not post admin requests to the list. They will be ignored. X11-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/x11-users/archive%40mail-archive.com This email sent to [email protected]
