Isn't the problem with this that in order to get the code out, people need
to upgrade and you therefor risk ending up with only notifying the people
that upgrade anyway?
eventually a hard drive fails or the operating system is replaced, and then
a BIND upgrade happens as a side effect. statistically this takes between
five and ten years for a server whose operator doesn't read CERT advisories.
so while the opportunity isn't as frequent as i'd like, it does occur, and
i'd like to slip in some logic that makes subsequent upgrades more frequent.
(several nanoggers have pointed out that the trouble is human nature, not
technology, but that doesn't mean we can't make it easier to do the right