Date: Sat, 22 Aug 1998 10:09:52 -0500 (CDT) From: Joel Ray Holveck <joelh@gnu.org> To: jb@cimlogic.com.au Cc: rabtter@aye.net, hackers@FreeBSD.ORG Subject: Re: I want to break binary compatibility. Message-ID: <199808221509.KAA04791@detlev.UUCP> In-Reply-To: <199808220003.KAA16116@cimlogic.com.au> (message from John Birrell on Sat, 22 Aug 1998 10:03:55 %2B1000 (EST)) References: <199808220003.KAA16116@cimlogic.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
>> What I want to do, if possible is build a uniq system such that >> binaries from other systems will not run on it and vice versa. Is >> this possible? > Since you have all the sources to the kernel, you have control over > what executable formats the kernel will recognize. Why not try your > own binary format that differs in a way known only by you? You could > create a tool that converts an aout or elf executable into your > proprietary format. Note that if the crackers get wise to this, then they could analyze the new format. Same goes for jmb's idea of scrambling syscalls, although since rtld is failing rather than exec, it's likely to be harder to discover the problem (since exec will, unless modified, report a useful error message; rtld won't since it can't access write()). It may also be useful to, for each filesystem FOO, mount FOO either read-only or noexec. Best, joelh -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808221509.KAA04791>