full-disclosure - Re: FD / lists.grok.org

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: <20090106091911.GA29538@lboro.ac.uk>
Date: Tue, 6 Jan 2009 09:19:11 +0000
From: A.L.M.Buxey@...ro.ac.uk
To: anonymous pimp <anonymouspimp@...il.com>
Cc: full-disclosure@...ts.grok.org.uk
Subject: Re: FD / lists.grok.org - bad SSL cert

Hi,

> It's off topic for this thread. FD, by it's very nature, is designed

I wonder why so much effort is spent discussing a self-signed
web interface for unsubscribing from a mialing list - when
the email headers clearly state how to leave via an email message
and not bother with a web interface at all. most decent email clients
can deal with such mailing list headers.

> Also, don't just change ths subject, please. Make a new thread. Simply
> changing the topic does not make it a new thread, many mail clients
> show it as part of the same thread.

aye. A bane of my life. I wrote a draft RFC which covered 2 mechanisms
to allow email clients to break the message thread (specifically unhook 
the In-Reply-To and Reference headers) if the client detected that a
thread was being hijacked (eg subject deleted with a new one - or the entire 
body of the email deleted (so no reply > lines etc) - unfortunately
there wasnt much support :-|

alan

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/