Re: trace mode by default

Hi, On Fri, Jan 12, 2018 at 02:42:06PM +0100, db wrote: > I gave it a try just to see where it would stop or what clues would I > get in the logs and it didn't even extract, although from a glimpse > into porttrace.tcl the program used (AFAIR) should have been in the > allowed system directories.

Re: lib dependency confusion

On Jan 12, 2018, at 3:27 PM, Dave Horsfall wrote: > Whether Apple wants to admit that its machines can crash and thereby cream > the filesystem is another question... presumably that's what macOS Recovery is for: https://support.apple.com/en-us/HT201314 -- Daniel J. Luke

Re: lib dependency confusion

On Jan 12, 2018, at 5:22 PM, Bill Cole wrote: > All very well and good for a machine running an OS version that got the > ShellShock update from Apple. people probably shouldn't be running an OS version that hasn't been patched for a 4 year old

Re: lib dependency confusion

On Jan 11, 2018, at 11:31, Vincent Habchi wrote: > Alternatively to what Ryan just mentioned, you can statically link the > executable, which means that you embed all the code the executable and its > dependencies need into the main code. This result in a bigger executable > (more code) but