full-disclosure - How to Report a Security Vulnerability toMicrosoft

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: <425A9950.2080508@agent.co.il>
Date: Mon Apr 11 16:36:07 2005
From: sysadmin at agent.co.il (Ag. System Administrator)
Subject: How to Report a Security
	Vulnerability	toMicrosoft



Airey, John wrote:
>>-----Original Message-----
>>From: full-disclosure-bounces@...ts.grok.org.uk 
>>[mailto:full-disclosure-bounces@...ts.grok.org.uk] On Behalf 
>>Of Microsoft Security Response Center
>>Sent: 08 April 2005 20:21
>>To: bugtraq@...urityfocus.com; 
>>ntbugtraq@...tserv.ntbugtraq.com; full-disclosure@...ts.grok.org.uk
>>Subject: [Full-disclosure] How to Report a Security 
>>Vulnerability toMicrosoft
>>
>>-----BEGIN PGP SIGNED MESSAGE-----
>>Hash: SHA1
>>
>>Hello!
>>
>>The Microsoft Security Response Center investigates all 
>>reports of security vulnerabilities sent to us that affect 
>>Microsoft products.
>>If you believe you have found a security vulnerability 
>>affecting a Microsoft product, we would like to work with you 
>>to investigate it.
>>
>>We are concerned that people might not know the best way to 
>>report security vulnerabilities to Microsoft. You can contact 
>>the Microsoft Security Response Center to report a 
>>vulnerability by emailing secure@...rosoft.com directly, or 
>>you can submit your report via our web-based vulnerability 
>>reporting form located at:
>>https://www.microsoft.com/technet/security/bulletin/alertus.aspx.
>>
>>Sincerely,
>>Microsoft Security Response Center 
> 
> [snip]
> 
> Unless there's something wrong at my end (I hope not), this message
> doesn't appear to have been signed with the key at
> http://www.microsoft.com/technet/Security/bulletin/pgp.mspx.
> 
> Am I right or not?
> 
not.

Key Id: 0xAA55BC66 / Signed on: 04/08/2005 10:17 PM

It's them...


Have fun,
Dan