From: Larry McVoy <lm@bitmover.com>
To: "Richard B. Tilley (Brad)" <rtilley@vt.edu>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Verifying Kernel source
Date: Wed, 27 Nov 2002 09:28:18 -0800 [thread overview]
Message-ID: <20021127092818.Q24374@work.bitmover.com> (raw)
In-Reply-To: <1038408874.12143.14.camel@oubop4.bursar.vt.edu>; from rtilley@vt.edu on Wed, Nov 27, 2002 at 09:54:34AM -0500
> What is the proper way to verify the kernel source before compiling?
> There have been too many trojans of late in open source and free
> software and I, for one, am getting paranoid.
If it's in BK you can be pretty sure that it is what was checked in,
BK checksums every diff in every file. It's not at all impossible
to fool the checksum but it is very unlikely that you can cause
semantic differences in the form of a trojan horse and still fool
the checksums.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2002-11-27 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 14:54 Verifying Kernel source Richard B. Tilley (Brad)
2002-11-27 16:46 ` Jason Cook
2002-11-27 17:28 ` Larry McVoy [this message]
2002-11-27 22:29 ` Geert Uytterhoeven
2002-11-28 2:30 ` Larry McVoy
2002-11-28 9:54 ` Helge Hafting
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=20021127092818.Q24374@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rtilley@vt.edu \
/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.