🚀 go-pugleaf

Tony Lawrence aka apl@world.std.com wrote:
{ Ken Gunther (kgunther@delphi.com) wrote:
{ :    There have been a number of suggestions that the only people allowed on
{ : the list are those who are identified as the technical contact. Perhaps I'm
{ : paranoid but I believe that there are governments and commercial
{ : institutions that have something to gain by sponsoring some crackers. The
{ : cover of government or commercial enterprise lends legitimacy to these
{ : crackers making them appear quite trustworthy since they are supported by a
{ : large organization. 

{ :    I agree with those that state that full disclosure should only come AFTER
{ : the patch is available.

{ At this moment, I would guess that 80-90% of the SCO market is totally
{ unaware of this problem.  Yes, I said UNaware.

{ Disclosure will eventually filter out to everyone in the tech support
{ and hacker community, but I bet even 5 years from now there will be
{ SCO users who never heard a peep about this.

{ So those people will remain vulnerable, because they won't be patched.

{ I see no reason for disclosure.  Why the heck do I need to know how to
{ exploit this?  Why does anyone?  To check that it's been fixed completely?
{ Maybe, but it opens up vulnerability for a whole bunch of people.

{ --
{ Tony

Now that I know what it is, I can explain it to my customers.  They'll be 
much more comfortable knowing that I've taken the time and effort to 
worry about their systems for them.  If I'd just given them a patch and 
said "It's to fix a security hole. What's the hole? Uh, I don't know."  
it wouldn't do as much good. 

Maybe not everyone will hear about this problem.  It's their fault.  If 
you have a system that's capable of being cracked and you don't do what 
you can to learn how to keep it safe then it's YOUR problem.  Keeping 
your head in the sand won't help.  Thinking that it'll only happen to the 
other guy won't help.  If you don't want to know, fine.  I DO.
-- 
gburnore@garys.arasmith.com
--------------------------------------------------------------------------
                How you look depends on where you go.
--------------------------------------------------------------------------
                                     | �۳�ݳ޳�ݳ�۳�ݳ޳�ݳݳ޳�ݳ����
Gary L. Burnore                      | �۳�ݳ޳�ݳ�۳�ݳ޳�ݳݳ޳�ݳ����
Director, Programming & Development  | �۳�ݳ޳�ݳ�۳�ݳ޳�ݳݳ޳�ݳ����
Myers Information Systems, Inc.      | �۳ 3 4 1 4 2 �ݳ޳ 6 9 0 6 9 ���
                                     |     Official Proof of Purchase
==========================================================================