full-disclosure - Re: Re: Empty emails example

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20040229233209.GK22426@uriel.eclipsed.net>
From: gr at eclipsed.net (gabriel rosenkoetter)
Subject: Re: Re: Empty emails example

On Sun, Feb 29, 2004 at 04:47:31PM -0500, Bill Royds wrote:
>   I was disclosing a possible reconnaissance of compromised hosts. Perhaps
> you don't like full disclosure of attacks, only exploits?

I approve of disclosure of those attacks, but I don't think that
Full-Disclosure is the appropriate place for it. From the list's
charter, which is referenced in the footer of every piece of list
mail:

  Any information pertaining to vulnerabilities is acceptable, for
  instance announcement and discussion thereof, exploit techniques and
  code, related tools and papers, and other useful information.

"Vulnerabilities" does not imply "misuse of functional networks".

Discussion of the type you want belongs on, and takes place
regularly on, the incidents@...urityfocus.com mailing list.

-- 
gabriel rosenkoetter
gr@...ipsed.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 186 bytes
Desc: not available
Url : http://lists.grok.org.uk/pipermail/full-disclosure/attachments/20040229/939d9e1e/attachment.bin