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] [day] [month] [year] [list]
Message-ID: <CAH8yC8mYR=CEn8=+58xp44W7ZQu9TJj0v-ActOZGxXP9FAd2ZQ@mail.gmail.com>
Date: Mon, 14 Mar 2016 19:29:25 -0400
From: Jeffrey Walton <noloader@...il.com>
To: Fyodor <fyodor@...p.org>
Cc: Full Disclosure Mailing List <fulldisclosure@...lists.org>
Subject: Re: [FD] Security contact @ Gigabyte

> Yeah, the general FD list policy is to reject requests for vendor contacts
> unless they also include full disclosure of the bug details:
>
> https://secwiki.org/w/FD_Moderation#Requests_for_vendor_security_contacts
>
> It's not that there is anything wrong with the more limited disclosure and
> vendor pre-disclosure approaches, but those aren't full disclosure and so
> probably belong on a different list.

Maybe FunSec (http://lists.linuxbox.org/cgi-bin/mailman/listinfo/funsec)
would be a better place to ask for hep finding the contact:

    Funsec -- Fun and Misc security discussion for OT posts.

Jeff

_______________________________________________
Sent through the Full Disclosure mailing list
https://nmap.org/mailman/listinfo/fulldisclosure
Web Archives & RSS: http://seclists.org/fulldisclosure/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ