From: Hank Leininger <linux-kernel@progressive-comp.com>
To: linux-kernel@vger.kernel.org
Subject: Re: please kindly get back to me
Date: Tue, 4 Jun 2002 00:26:23 -0400 [thread overview]
Message-ID: <200206040426.g544QNA28367@marc2.theaimsgroup.com> (raw)
On 2002-06-03, J Sloan <joe@tmsusa.com> wrote:
> The thing with linux/unix "virii" is, they
> are actually for the most part trojans -
> they've been in labs for years, the problem
> is that there is no suitable transport vector!
> You'd have to dupe an unwitting superuser
> (now there's a dangerous combination) into
> running the "virus" by hand - sort of like
> the "honor system" virus....
...You mean like, get them to run './configure' ?[1][2]
...Or installing an RPM with trojanned binaries or install-time scripts,
without checking a signature?[3]
Unfortunately that's all too easy. Viruses, no. Malware, you bet. We
can't get too complacent while laughing at the virus phenomenon.
[1] http://marc.theaimsgroup.com/?l=bugtraq&m=102233939226053&w=2
http://marc.theaimsgroup.com/?l=bugtraq&m=102285523803434&w=2
[2] They don't have to do this as root, either. If they do it from an
account that can escalate privileges (i.e. is allowed to su or sudo)
then it's game over anyway, albeit with more steps.
[3] And of course signatures are useless if the signer was owned first.
Probably major distros are reasonably safe[4], but not Joe Random who
produces packages and distributes them...
[4] They're not out to get you; they've already got you:
http://www.acm.org/classics/sep95/
--
Hank Leininger <hlein@progressive-comp.com>
ALL YOUR BASE ARE BELONG TO KEN THOMPSON
next reply other threads:[~2002-06-04 4:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 4:26 Hank Leininger [this message]
2002-06-04 18:36 ` [OT] " J Sloan
2002-06-04 20:24 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-06-04 21:49 Jesse Pollard
2002-06-04 2:04 Matt_Domsch
2002-06-04 3:17 ` J Sloan
2002-06-03 15:46 JOSEPH EDWARD.
2002-06-03 15:33 Holzrichter, Bruce
2002-06-03 19:00 ` Matti Aarnio
2002-06-03 19:06 ` Larry McVoy
2002-06-03 19:23 ` Matti Aarnio
2002-06-03 19:43 ` stoffel
2002-06-04 0:37 ` Alan Cox
2002-06-04 7:10 ` Rik van Riel
2002-06-04 8:11 ` J Sloan
2002-06-03 19:50 ` H. Peter Anvin
2002-06-03 20:16 ` Davide Libenzi
2002-06-03 20:03 ` M. Edward (Ed) Borasky
2002-06-03 20:08 ` Gerhard Mack
2002-06-03 23:11 ` J Sloan
2002-06-04 0:20 ` Austin Gonyou
2002-06-04 20:25 ` Michael H. Warfield
2002-06-03 20:54 ` Rik van Riel
2002-06-03 20:58 ` Herman Oosthuysen
2002-06-03 22:51 ` J Sloan
2002-06-04 14:25 ` Pavel Machek
2002-06-03 15:26 JOSEPH EDWARD.
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=200206040426.g544QNA28367@marc2.theaimsgroup.com \
--to=linux-kernel@progressive-comp.com \
--cc=hlein@progressive-comp.com \
--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®