full-disclosure - Re: Announcing new security mailing list

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

From: madduck at madduck.net (martin f krafft)
Subject: Re: Announcing new security mailing list

also sprach Ron DuFresne <dufresne@...ternet.com> [2002.07.11.2010 +0200]:
> > BTW, spewing "[full-disclosure]" into the subject line is a very annoying
> > thing for a list to do.
> >
> 
> Actually, it makes it quite easy for procmail recipies and certain mail
> readers to filter and categorize the messages.

there are many other headers one may use. e.g., i use:

  * ^List-Id:.*full-disclosure\.lists\.netsys\.com

i do consider [Full-Disclosure] in the subject line rather annoying
because it wastes valuable subject space. good mailing lists have
subject lines that allow the pre-elimination of anything that doesn't
concern one. especially if it's high traffic, this is something more
than necessary. i vote to take the subject prefix off.

it would also be nice to have received headers cut off when the
listprocessor starts its job on such a public mailing list.

-- 
martin;              (greetings from the heart of the sun.)
  \____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@...duck

wind catches lily,
scattering petals to the ground.
segmentation fault.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 240 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20020713/635409e3/attachment.bin