Date: Wed, 12 Oct 2005 14:58:12 +0400 From: "Andrew P." <infofarmer@gmail.com> To: Jonathon McKitrick <jcm@freebsd-uk.eu.org> Cc: freebsd-questions@freebsd.org Subject: Re: Implementing software licensing in FreeBSD Message-ID: <cb5206420510120358y74caae44l3062248ae9a14b47@mail.gmail.com> In-Reply-To: <20051012104241.GA34129@dogma.freebsd-uk.eu.org> References: <20051012104241.GA34129@dogma.freebsd-uk.eu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/12/05, Jonathon McKitrick <jcm@freebsd-uk.eu.org> wrote: > > Setting aside opinions on copy protection and licensing, suppose I wanted= to > implement such a scheme. > > The key itself might be a network license, or an encrypted file containin= g > license info and system-specific info. But the real issue is how to prot= ect > the code that accesses the key. I know that 'wrappers' don't have much o= f an > application in Unix, and are actually impractical. But what techniques c= ould > be implemented within a library or archive that would make it difficult f= or > someone to trace the algorithm and/or make changes to the code to remove = the > protection checks? > > jm > -- > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o= rg" > No matter what the platform is, one of the most effective tricks is to check different checksums (CRC, MD5, SHA256...) of different parts of different binaries at different (random) points by inline functions. Failure to verify a binary integrity should lead to immediate program termination. I don't see a single reason for this question being asked here.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?cb5206420510120358y74caae44l3062248ae9a14b47>