1/21 So is the motd just dgies, ausman, jrleek, emarkp, and a few others
talking to each other? Or is there some great unwashed mass of non
motdedit people out there?
\_ How could you forget tom? -emarkp
\_ I represent that remark
\_ I resemble that.
\_ Already, the Kay report identified dozens of weapons of mass
destruction-related program activities and significant amounts
of equipment that Iraq concealed from the United Nations.
\_ about half the motd people don't use motdedit, if that gives you
any idea of the number of users.
\_ and how do you know that...
\_ ps -auxwww|grep motd.p
\_ That doesn't show even a small fraction of it. I've got
this down to a near-science. I know who the censors are.
I know who writes from the right, left, center, and the
outfield. I know who writes opposing views based on some
seemingly random factors unknown to me. And if your
scripting fu was at the near god like levels of mine you
would know too.
\_ ok, God, why don't you say which anon. people are who
and we'll tell you how far off you are. Who am I?
\_ Or I!
\_ he's bullshitting. short of having root, the
existence of file-related bugs in the os (that
he knows how to exploit), or very few users
in an unidle state, there's no way to reliably tell.
\_ If he cared enough and spent enough effort, he
could correlate process behavior of motd file
access. Certainly not reliably. I read a local
copy of the motd so he'd have to catch my 'cp'.
\_ Most of us don't care that much.
\_ what if I simply do a "cp /tmp/motd.public a; vi a;
cp a /tmp/motd.public"? Then the only chance to catch it
is during the moment I do cp, which is only probabilistic. |
http://csua.com/feed/