From: Dale Amon <amon@vnl.com>
To: Lukasz Luzar <lluzar@tigeraudits.com>
Cc: "Carsten P. Gehrke" <Carsten@rollinghorse.com>, selinux@tycho.nsa.gov
Subject: Re: Linuxfromscratch.org
Date: Thu, 24 Jul 2003 01:29:49 +0100 [thread overview]
Message-ID: <20030724002949.GI4900@vnl.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0307232139200.9324-100000@chaos.tigeraudits.com>
On Wed, Jul 23, 2003 at 10:26:42PM +0200, Lukasz Luzar wrote:
> Hello,
>
> > 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.
--
------------------------------------------------------
IN MY NAME: Dale Amon, CEO/MD
No Mushroom clouds over Islandone Society
London and New York. www.islandone.org
------------------------------------------------------
--
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.
next prev parent reply other threads:[~2003-07-24 0:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-22 1:42 Linuxfromscratch.org Charlie Watts
2003-07-22 20:06 ` Linuxfromscratch.org Russell Coker
2003-07-22 20:49 ` Linuxfromscratch.org Dean Anderson
2003-07-23 15:09 ` Linuxfromscratch.org Carsten P. Gehrke
2003-07-23 15:44 ` Linuxfromscratch.org Russell Coker
2003-07-23 20:01 ` Linuxfromscratch.org Dale Amon
2003-07-23 21:24 ` Linuxfromscratch.org Dean Anderson
2003-07-23 19:34 ` Linuxfromscratch.org karlm
2003-07-23 22:08 ` Linuxfromscratch.org Dean Anderson
2003-07-24 14:06 ` Linuxfromscratch.org Dale Amon
2003-07-24 14:16 ` Linuxfromscratch.org Dale Amon
2003-07-24 14:18 ` Linuxfromscratch.org Dale Amon
2003-07-24 17:40 ` Linuxfromscratch.org Colin Walters
2003-07-24 18:52 ` Linuxfromscratch.org Dean Anderson
2003-07-27 15:28 ` Linuxfromscratch.org Tom
2003-07-27 20:13 ` Linuxfromscratch.org Colin Walters
2003-07-28 17:17 ` Linuxfromscratch.org Tom
2003-07-24 19:42 ` Linuxfromscratch.org Russell Coker
2003-07-27 15:19 ` Linuxfromscratch.org Tom
2003-07-23 20:26 ` Linuxfromscratch.org Lukasz Luzar
2003-07-24 0:29 ` Dale Amon [this message]
2003-07-24 6:39 ` Linuxfromscratch.org Brian May
2003-07-24 12:32 ` Linuxfromscratch.org Dale Amon
2003-07-23 1:17 ` Linuxfromscratch.org Carsten P. Gehrke
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030724002949.GI4900@vnl.com \
--to=amon@vnl.com \
--cc=Carsten@rollinghorse.com \
--cc=lluzar@tigeraudits.com \
--cc=selinux@tycho.nsa.gov \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.