Date: Sat, 16 May 1998 20:13:26 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: peter@netplex.com.au (Peter Wemm) Cc: dyson@FreeBSD.ORG, kkennawa@physics.adelaide.edu.au, current@FreeBSD.ORG Subject: Re: libc corruption Message-ID: <199805162013.NAA08439@usr02.primenet.com> In-Reply-To: <199805160829.QAA29907@spinner.netplex.com.au> from "Peter Wemm" at May 16, 98 04:29:32 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > Those are symbols created from the kernel list of system calls. > > It's times like this that I'd really like to have a *seperate* list of > syscalls and numbers stored in lib/libc explicitly. I've blown holes in > my feet over this so many times that I don't have much of my feet left. :-] [ ... ] > To make it a little easier, perhaps have libc's syscall tables explicitly > generated from the kernel sources and committed. That should make it > a no-brainer to keep them in sync and yet will stop accidental leakage > from the kernel into libc. Consider that with ELF and a dynamically linked binary, you could dlopen the kernel (copy on write, of course), and have a special ELF section whose intent is to provide the libc system call mappings. Similarly, you could provide kernel-specific libkvm routines, so that you never has ps/w/netstat/ifconfig/etc. problems ever again, *without* screwing up the ability to run various programs against a dump image. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199805162013.NAA08439>