News for hackers. Stuff that matters.
Re:Maybe: run a command, see what it does to your files with... by gravypod on Saturday February 06, 2016 @07:59PM (#11050947)
THIS IS AMAZING! I would have never imagined seeing something this useful being made in my life.
Re:Maybe: run a command, see what it does to your files with... by throwaway2048 on Sunday February 07, 2016 @01:16AM (#11051903)
I wouldn't rely on it being safe, it makes a lot of assumptions that programs that do destructive things might violate.
Re:Maybe: run a command, see what it does to your files with... by jldugger on Saturday February 06, 2016 @10:16PM (#11051420)
It's actually quite simple. LD_PRELOAD can achieve a similar effect, if the software is using the typical syscall library.
Re:Maybe: run a command, see what it does to your files with... by gravypod on Saturday February 06, 2016 @10:42PM (#11051489)
I know exactly how it was done, I am just amazed that it was done. It's a great idea that I have never come up with, nor would I be able to.
Re:Maybe: run a command, see what it does to your files with... by emmelaich on Saturday February 06, 2016 @11:05PM (#11051545)
Yes, it's a great idea.

A similar idea is used to trace what 'make install' does so that stuff can be uninstalled later - or made into a package (rpm, dpkg etc)

I forget what that tool is called.

Re:Maybe: run a command, see what it does to your files with... by burrows on Saturday February 06, 2016 @11:24PM (#11051593)
Re:Maybe: run a command, see what it does to your files with... by obelisk_ on Sunday February 07, 2016 @04:29AM (#11052300)
Also similar in concept is the tup build system which monitors rule commands run to gain knowledge of additional dependencies.

http://gittup.org/tup/ex_dependencies.html