full-disclosure

Open Source and information security mailing list archives

Date: Mon, 14 Mar 2016 17:55:04 -0400
From: Jeffrey Walton <noloader@...il.com>
To: Gustavo Sorondo <gs@...tainfinita.com.ar>
Cc: Full Disclosure List <fulldisclosure@...lists.org>
Subject: Re: [FD] Security contact @ Gigabyte

On Wed, Mar 9, 2016 at 4:15 PM, Gustavo Sorondo <gs@...tainfinita.com.ar> wrote:
> Hi list,
>
> I'd like to know if anyone here know someone working on security at
> Gigabyte (http://www.gigabyte.com/), since we are trying to responsibly
> report a high risk security flaw we found.
>
> We opened a ticket asking to be contacted by their security team, and the
> answer we got was:
>
> "Thanks for your interest, but we already have a security team for our
> websites. Regards, GIGABYTE" (sigh)
>
> So, if any of you knows someone in there, please let us know.
>

According to RFC 2142 (http://www.ietf.org/rfc/rfc2142.txt), MAILBOX
NAMES FOR COMMON SERVICES, ROLES AND FUNCTIONS, you should be able to
use:

   secure@...abyte.com
   security@...abyte.com

I also rummage the WHOIS data and use the Administrative and Technical contacts:

   $ whois gigabyte.com | grep '@'
   Registrant Email: domains@...caria.com
   Admin Email: domains@...caria.com
   Tech Email: domains@...caria.com
   Registrar Abuse Contact Email: abuse@...caria.com

WHOIS data must be correct. Its an ICANN contractual obligation.

Jeff

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

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