Date: Wed, 20 Feb 2008 17:26:39 -0800 From: Tim Kientzle <kientzle@freebsd.org> To: Thiago Damas <tdamas@gmail.com> Cc: freebsd-hackers@freebsd.org Subject: Re: encrypted executables Message-ID: <47BCD34F.7010309@freebsd.org> In-Reply-To: <f8e3d83f0802200451r463f188bn881268b9b2768846@mail.gmail.com> References: <86068e730802181718s1ad50d3axeae0dde119ddcf92@mail.gmail.com> <47BA3334.4040707@andric.com> <86068e730802181954t52e4e05ay65e04c5f6de9b78a@mail.gmail.com> <20080219040912.GA14809@kobe.laptop> <f8e3d83f0802200451r463f188bn881268b9b2768846@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Thiago Damas wrote: > And if you make a wrapper, and execute like a shell script: > > #!/usr/local/bin/mysecyritywrapper > <...encryted code goes where...> > > In this way. it'll be hard to use truss, ktrace, strace etc... No, not really. All of those tools can trace through to sub-processes, so whenever the code gets decrypted and starts executing (whether it's in the main process or in a sub-process), they'll be able to follow the system calls it makes. The key fact about DRM is that it is theoretically impossible. Of course, that's what makes it such an interesting problem in practice. ;-) Cheers, Tim Kientzle
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47BCD34F.7010309>