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: <1301893222980.20030821220227@gmx.net>
From: 8tImER at gmx.net (8tImER)
Subject: Subject prefix changing! READ THIS! SURVEY!!

My vote goes to choice #1. :]

-- 
Greetz,
 8tImER                            mailto:8tImER@....net
                                   GPG Key-ID: 0xADD46137

Originaltext:
Am 21.08.2003 um 19:43:02 hast du geschrieben:

> 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 
> 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!!!

> 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.