🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: comp.security.unix
Article #108

Re: [8lgm]-Advisory-13.UNIX.SCO-login.15-Apr-1994

#108
From: merlin
Date: Wed, 14 Dec 1994 08:30
41 lines
2996 bytes
>Full disclosure by 8lgm once got my machine broken into ...

Surely some legal genius could come up with a credible threat of
civil or criminal liability against 8lgm message originators for
something like aiding and abetting a specific identifiable crime
(e.g. the system breakin described above).  In my opinion, there
should be a reasonable embargo period before such announcements
-- and no broadcast public announcement should contain script or
other information sufficient to accomplish a system penetration.

I personally, based on over 20 years of professional experience
working in and managing computer centers for academic, business,
and government organizations, would request 8lgm stop publishing
system penetration aids for public broadcast.  I would classify
such tools as virtual burglar tools -- akin to virus codes -- to
be banned from public archival sites and broadcast transmission.

Please stop publishing system penetration aids.  Notify contact
people in the appropriate vendor organization.  Notify CERT and
other credible discrete computer security organizations.  But,
never broadcast enough information to compromise anyone's system.

This is not a matter of security by obscurity.  This is a matter
of simple common sense.  Not everyone has some full time security
person or even system management personnel available to support
their systems.  Moreover, even if such personnel were available
not everyone can stay up to date with every security accouncement
from every tiny self appointed security organization on the net.

I know CERT.  I trust their methods and announcements.  I don't
know 8lgm.  I certainly don't appreciate their public broadcasts.

------------------------------------------------------------------------------
Alexander-James Annala
Principal Investigator
Neuroscience Image Analysis Network
HEDCO Neuroscience Building, Fifth Floor
University of Southern California
University Park
Los Angeles, CA 90089-2520
------------------------------------------------------------------------------
Technical Details
Message-ID: <3cmafr$7di@neuro.usc.edu>
Path: arc1-ca.pugleaf.net!nntp.gmd.de!newsserver.jvnc.net!howland.reston.ans.net!usc!usc!not-for-mail
References: <3bca3q$6dh@eldborg.rhi.hi.is> <3bdgml$ana@usenety1.news.prodigy.com> <3bg70j$78h@zikzak.apana.org.au>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 10952f,baa596e4a440876b
X-Google-Attributes: gid10952f,public
X-Google-Thread: 1122ea,baa596e4a440876b
X-Google-Attributes: gid1122ea,public
X-Google-Thread: 134180,baa596e4a440876b
X-Google-Attributes: gid134180,public
X-Google-ArrivalTime: 1994-12-14 00:30:51 PST
Path: arc1-ca.pugleaf.net!nntp.gmd.de!newsserver.jvnc.net!howland.reston.ans.net!usc!usc!not-for-mail
From: merlin@neuro.usc.edu (merlin)
Newsgroups: comp.security.unix,biz.sco.general,biz.sco.opendesktop
Subject: Re: [8lgm]-Advisory-13.UNIX.SCO-login.15-Apr-1994
Date: 14 Dec 1994 00:30:51 -0800
Organization: University of Southern California, Los Angeles, CA
Lines: 42
Sender: merlin@neuro.usc.edu
Message-ID: <3cmafr$7di@neuro.usc.edu>
References: <3bca3q$6dh@eldborg.rhi.hi.is> <3bdgml$ana@usenety1.news.prodigy.com> <3bg70j$78h@zikzak.apana.org.au>
NNTP-Posting-Host: neuro.usc.edu