From: Dale Amon <amon@vnl.com>
To: Dale Amon <amon@vnl.com>, Lukasz Luzar <lluzar@tigeraudits.com>,
"Carsten P. Gehrke" <Carsten@rollinghorse.com>,
selinux@tycho.nsa.gov
Subject: Re: Linuxfromscratch.org
Date: Thu, 24 Jul 2003 13:32:20 +0100 [thread overview]
Message-ID: <20030724123220.GB25756@vnl.com> (raw)
In-Reply-To: <20030724063949.GC16983@snoopy.apana.org.au>
On Thu, Jul 24, 2003 at 04:39:49PM +1000, Brian May wrote:
> > 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...
There are some safe assumptions we can make:
* The trojan is not arbitrarily complex as
it must have compiled into the size of
the early gcc.
* It is not arbitrarily specific or else
it would only have worked on the earliest
login.c and thus we can escape it simply
by changing the login.c code.
So it is either simple minded or there are certain
features in a login.c that all C programmers will
recreate even if starting from a blank emacs windows
and no knowledge of the original login.c other than
a minimal functional requirement doc.
So get 100 junior programmers to write one hundred
login.c's from scratch and see what they have in
common.
But I'll short circuit it. If I were coding this
in C back in 1977, I'd have done a string compare
on Username: and Password:.
--
------------------------------------------------------
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 12:32 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 ` Linuxfromscratch.org Dale Amon
2003-07-24 6:39 ` Linuxfromscratch.org Brian May
2003-07-24 12:32 ` Dale Amon [this message]
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=20030724123220.GB25756@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.