[prev in list] [next in list] [prev in thread] [next in thread]
List: firewalls-gc
Subject: best-of-security
From: Julian Assange <proff () suburbia ! net>
Date: 1995-08-02 11:05:52
[Download RAW message or body]
This partially a repost.
"best-of-security" had some majordomo/sendmail headaches. With some advise
from Brent Chapman I believe we have ironed these out.
If you have not received mail from b-o-s in the last 24 hours, then it is
most likely that you are not on the list, and need to (re)subscribe.
-Julian Assange.
Best of all available security resources.
_/_/_/ _/_/ _/_/_/
_/ _/ _/ _/ _/
_/_/_/ _/ _/ _/_/
_/ _/ _/ _/ _/
_/_/_/ _/_/ _/_/_/
Best Of Security
"echo subscribe best-of-security|mail best-of-security-request@suburbia.net"
REASONS FOR INCEPTION
---------------------
In order to compile the average security administrator it was found
that the compiler had to parse a foreboding number of exceptionally
noisy and semantically-content-free data sets. This led to
exceptionally high load averages and a dramatic increase in core
entropy.
Further, the number, names and locations of this data appears to
change on an almost daily basis; requiring tedious version control
on the part of the mental maintainer.
OVERVIEW
---------
Best-of-Security is at present an un-moderated list. That may sound
strange given our stated purpose of massive entropy reduction; but
because best often equates with "vital" and the moderator doesn't
have an MDA habit it is important that material sent to this list
be delivered to its subscribers' in as minimal period of time as
is (in)humanly possible.
If you find *any* information from *any* source (including other
mailinglists, newsgroups, conference notes, papers, etc) that fits
into one of the acceptable categories described at the end of this
document then you should *immediately* send it to
"best-of-security@suburbia.net". Do not try and predict whether or
not someone else will send the item in question to the list in the
immediate future. Unless your on a time-delayed mail vector such as
polled uucp or the item has already appeared on best-of-security,
mail the info to the list! Even if it is a widely deployed peice of
information such as a CERT advisory the proceeding argument still
applies. If the information hasn't appeared on this list yet, then
SEND IT. It is far better to run the risk of minor duplication in
exchange for having the information out where it is needed than act
conservatively about occasional doubling up on content.
We do, of course take original posts. In the famous last words of
CORE DIGEST: "meat, we want meat".
Consult the below lists for what we will and will not accept.
WILL WILL WILL WILL WONT WONT WONT WONT
8lgm, cert, ciac, dod and other Any flames.
non-vendor advisories. Any questions.
Vendor advisories of security Any rumors.
weaknesses in own or other products. Sigs with >2 lines of
Vendor new security-product line comercial information.
release or MAJOR upgrade. Minor upgrade information.
Fully disclosed security weaknesses. "there is a hole in X"
Exploitation details. Any advertising.
Exploitation code. Subscription, unsubscription or
Patch code. mailing list queries.
Patch announcements. Any requests.
Hard to obtain or otherwise occulted Vague or incomprehensible
source code or uuencoded executables. statements of dysfuctional
Conference announcements. persons.
Security tools. Opinionated rantings such as
Blond jokes. those on the ethics of full
NEW or hard to obtain security disclose or computer hackers.
documents (ascii), or pointers to Quotes from the Illiad.
the location of such documents/papers. Old or otherwise well known
Announcements of new security archives information or pointers to
or mailinglists. that information.
Human language translations of the above. Nonsense.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic