Re: Linuxfromscratch.org

From: Brian May <bam@snoopy.apana.org.au>
To: Dale Amon <amon@vnl.com>
Cc: Lukasz Luzar <lluzar@tigeraudits.com>,
	"Carsten P. Gehrke" <Carsten@rollinghorse.com>,
	selinux@tycho.nsa.gov
Subject: Re: Linuxfromscratch.org
Date: Thu, 24 Jul 2003 16:39:49 +1000	[thread overview]
Message-ID: <20030724063949.GC16983@snoopy.apana.org.au> (raw)
In-Reply-To: <20030724002949.GI4900@vnl.com>

On Thu, Jul 24, 2003 at 01:29:49AM +0100, Dale Amon wrote:
> On Wed, Jul 23, 2003 at 10:26:42PM +0200, Lukasz Luzar wrote:
> > > Is this true of the GNU C compiler suite as well?  And if so, would it not 
> > > be possible to remove it from the compiler?  How does it work?  Does it 
> > > look at the code, or is anything called login.c susceptible?  Why has this 
> > > not been removed in the open-source code?  How can I check to see if this 
> > > backdoor exists?
> 
> Of course you could always create a file like this:
> 
> login.c
>   main () { printf ("Hello World\n"); }
> 
> and the hand decompile the binary to see if there
> is anything unexpected present.

Does this proove anything though?

A trojon horse in the compiler could be clever enough not to insert
any back doors on such simple code...
-- 
Brian May <bam@snoopy.apana.org.au>

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.