full-disclosure - Re: Remove '' subject prefix

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: <4022283F.3070205@bksys.at>
From: bernhard at bksys.at (Bernhard Kuemel)
Subject: Re: Remove '' subject prefix

Bernhard Kuemel wrote:
> Now there's a subject in my message overview that really tells me 
> nothing: '[Full-Disclosure] [RHSA-2004:030-01] Updated ...' (the rest 
> gets cut off because then the sender field begins. I vote for completely 
> removing the '[Full-Disclosure]' subject prefix. I got no response from 
> len@...sys.com so let's see what the subscribers think.

Umm, I probably should have checked first cause this was already
discussed:

http://lists.netsys.com/pipermail/full-disclosure/2003-August/008771.html

On

http://lists.netsys.com/pipermail/full-disclosure/2003-August/008787.html

John Cartwright <johnc@...k.org.uk> writes:

"This has been covered several times... and we certainly *don't*
want this mail coming to the list. Feel free to mail myself or
Len on the subject. Discussions about subject line prefixes are
off-topic for a security list."

So I'm sorry for violating the list policy. Unfortunatly writing
to Len didn't relief the problem, especially as I didn't receive
a response. I'll check what results the thread in the archive
produced.

Bernhard

-- 
Webspace; Low end Serverhousing ab 15 e, etc.: http://www.bksys.at
Linux Admin/Programmierer: http://bksys.at/bernhard/services.html