From: "Richard B. Tilley " "(Brad)" <rtilley@vt.edu>
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Verifying Kernel source
Date: 27 Nov 2002 09:54:34 -0500 [thread overview]
Message-ID: <1038408874.12143.14.camel@oubop4.bursar.vt.edu> (raw)
Hello,
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.
Thank you,
Brad
next reply other threads:[~2002-11-27 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-27 14:54 Richard B. Tilley (Brad) [this message]
2002-11-27 16:46 ` Jason Cook
2002-11-27 17:28 ` Larry McVoy
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=1038408874.12143.14.camel@oubop4.bursar.vt.edu \
--to=rtilley@vt.edu \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®