full-disclosure - Subject prefix changing! READ THIS! SURVEY!!

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]

Message-ID: <001801c36815$0e070990$2b02a8c0@dcopley>
From: dcopley at eeye.com (Drew Copley)
Subject: Subject prefix changing! READ THIS! SURVEY!!


> -----Original Message-----
> From: full-disclosure-admin@...ts.netsys.com 
> [mailto:full-disclosure-admin@...ts.netsys.com] On Behalf Of 
> Chris Cappuccio
> Sent: Thursday, August 21, 2003 10:43 AM
> To: full-disclosure@...ts.netsys.com
> Subject: [Full-Disclosure] Subject prefix changing! READ 
> THIS! SURVEY!!
> 
> 
> Hey folks,
> 
> ALL LIST MEMBERS ARE ENCOURAGED TO RESPOND AND MAKE A CHOICE 
> AS TO HOW THEY WANT THIS BASIC FUNCTION OF THE LIST TO 
> CONTINUE OPERATING. 
> 
> The subject header is going to change.
> 
> This is a survey to see whether people want:
> 
> 1. To have no subject prefix, that is, we remove 
> [Full-Disclosure] or 2. To shorten the subject prefix from 
> [Full-Disclosure] to [FD] or 

[FD] would be fine.

> 3. Do nothing
> 
> 1. The first choice is preferable for me and, I would hope, 
> for most folks. 
> Len says he didn't really want it when he started the list 
> anyways.  So we are actually going to change it now.
> 
> 2. Choice two may be preferable for people who can only 
> filter their incoming messages based on the subject prefix.  
> So, if you WANT there to continue to be a subject prefix, SPEAK UP!!!

Regardless, it is much easier to filter based on subject line. 


> 
> 3. Choice three sucks and if anyone wants this SPEAK UP so we 
> know just how many people want this.  This is the least 
> preferrable as it clutters the Subject header and makes the 
> list harder to read through for those of us using a text 
> based e-mail client.
> 
> For those of you using procmail or a compatible filter, a 
> good match for Full-Disclosure that relies on headers you 
> will always see in list messages goes like this:
> 
> :0:
> * ^Sender.*full-disclosure-admin@...ts\.netsys\.com
> full-disclosure
> 
> That matches this header:
> 
> Sender: full-disclosure-admin@...ts.netsys.com
> 
> Alternately, you can tell your Pegasus/Mozilla/Outlook/OE/Whatever
> to match on this header.
> 
> -- 
> Nullum magnum ingenium sine mixtura dementiae fuit -- Seneca
> 
> _______________________________________________
> Full-Disclosure - We believe in it.
> Charter: http://lists.netsys.com/full-disclosure-charter.html
>