> (1) Root installs the malicious roff source unknowingly.
>
> (2) During the process of building/installing the program,
XXXXX
> at which point the trojan
> horse does it dirty work.
s/XXXXX/configure runs some stuff/
s/XXXXX/Make runs some stuff/
s/XXXXX/shell runs som stuff/
s/XXXXX/some random evil program runs/
Yeah, a troff macro is a little obtuse for the younger
generation, but so what? How many people who run those nifty gnu
autoconf twiddlies do you think are checking beforehand what they are
doing as root? At the risk of further flogging the sticky spot on the
road that used to be a horse, this really shouldn't be a shocker to
anyone on this list. Most anything you run as root can be made to own
you by whoever can change it before you run it.
-Bob
This archive was generated by hypermail 2b30 : Fri Apr 13 2001 - 14:53:39 PDT