linux-kernel - Re: [PATCH] Documentation/process: Change Microsoft contact for embargoed hardware issues

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]

Date:   Wed, 5 Feb 2020 17:01:07 -0500
From:   Sasha Levin <sashal@...nel.org>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     corbet@....net, linux-kernel@...r.kernel.org, kys@...rosoft.com,
        jamorris@...rosoft.com
Subject: Re: [PATCH] Documentation/process: Change Microsoft contact for
 embargoed hardware issues

On Wed, Feb 05, 2020 at 09:47:16PM +0000, Greg KH wrote:
>On Wed, Feb 05, 2020 at 04:36:21PM -0500, Sasha Levin wrote:
>> Remove Sasha Levin as the Microsoft contact. A new contact will be
>> assigned by Microsoft.
>>
>> Signed-off-by: Sasha Levin <sashal@...nel.org>
>> ---
>>  Documentation/process/embargoed-hardware-issues.rst | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/Documentation/process/embargoed-hardware-issues.rst b/Documentation/process/embargoed-hardware-issues.rst
>> index 33edae654599..a6f4f6e5c78b 100644
>> --- a/Documentation/process/embargoed-hardware-issues.rst
>> +++ b/Documentation/process/embargoed-hardware-issues.rst
>> @@ -250,7 +250,7 @@ an involved disclosed party. The current ambassadors list:
>>    Intel		Tony Luck <tony.luck@...el.com>
>>    Qualcomm	Trilok Soni <tsoni@...eaurora.org>
>>
>> -  Microsoft	Sasha Levin <sashal@...nel.org>
>> +  Microsoft
>
>That's fine, but when will that contact "be assigned"?  I'd rather not

Hopefully "soon" :)

>go without one at all for no good reason other than "people need to
>figure their stuff out" :)

There's not much I can do on behalf of Microsoft anymore, so leaving me
there will be misleading.

-- 
Thanks,
Sasha