As a new subscriber to the firewalls list I have been following the
discussion on the creation and maintenance of a hacker's list with great
interest. At the risk of inviting flameout I offer my (and only my) opinion.
I tend to agree with the general concept of a "hacker's list". But, from a
different perspective. Look at it like a quality survey or an airline's
on-time reporting. If JD Power or Consumer Report's rates a product poorly.
It is pretty reasonable that the maker of that product will: a) correct the
problem with great fanfare and a label of "New and Improved" ;-) , or b)
live with the idea that theirs is not the best of products and it is
reasonable for consumers to go elsewhere :-( . Why should the I-net be any
different? If a company, university or commercial carrier were to
consistently show up as the origin of trouble makers, what is wrong with
making that information public? If someone wants to use that information to
choose who can and cannot be allowed access to their network, so be it.
Public embarassment has proven to be an effective means for improving auto
quality over the last 10 years. Why couldn't the "hacker list" be used to
highlight sites that seem to create more problems than their peers. Staying
off that list would be a powerful lure to making sure that "my" site is
clean and trustable.
Lest I be labelled a heathen or worse, let me further postulate that the
probability of this list ever coming to fruition is miniscule. Who would
want the administrative headaches? Not me that's for sure.
Mike Papais : Chrysler Information Services
I-Net : MJPapais-0 @
is .
chrysler .
com
|
|
