[...]
downloads lots of stuff & patches it with insecure shiznit,
Be fair now -- what
makes it insecure and your stuff secure?
Understanding. (While I didn't write any of the above, I share enough
of the views expressed to feel moderately confident I share the mindset
behind it.)
Rule of thumb: if you don't understand what your machine is running, it
isn't secure. The converse is, unfortunately, not as true as I'd wish,
but at least you know where your security holes are. In many
circumstances, knowing what your exposure is is almost as good as
closing it. In the case of my home machines, for example, I've made a
conscious decision to ignore threats posed by people with physical
access to my machines' consoles. I am hopelessly insecure against such
threats - but I know it, I find the benefits outweigh the costs, and I
keep it in mind when, for example, leaving other people in my place in
my absence.
Well, who in their right mind would run qmail???
Amen. Not open source, connection-bombs recipient mailhosts by
default, nonstandard bounces that don't even have message-IDs(!)...and
now this
Last I checked, messages in the queue must have
filenames that match
their inode numbers
which I hadn't heard of before.
Yet quite a number of otherwise apparently sane people do, and appear
totally impervious to clue provision. I really don't get it. (To be
fair, there are also a number that *are* at least somewhat
clue-pervious, though there's one - a really nice guy in most respects,
both online and in person - with whom I've had several go-rounds over
the connection-bombing misbehaviour, who just can't seem to grasp the
concept of politeness as applied to other people's resources.)
/~\ The ASCII der Mouse
\ / Ribbon Campaign
X Against HTML mouse at rodents.montreal.qc.ca
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B