[cifs-protocol] [REG:120082121001591] MS-NRPC FullSecureChannelProtection

Jeff McCashland jeffm at microsoft.com
Fri Aug 21 16:43:38 UTC 2020

[DocHelp to BCC, support on CC, SR ID on Subject]

Hello Stefan,

Thank you for sending in your question. While we normally only document out-of-box behavior, we'll investigate to see if a product behavior note is needed. We have created SR 120082121001591 to track this issue. 

I'll research the registry setting, and let you know what I find. 

Best regards,
Jeff McCashland | Senior Escalation Engineer | Microsoft Protocol Open Specifications Team 
Phone: +1 (425) 703-8300 x38300 | Hours: 9am-5pm | Time zone: (UTC-08:00) Pacific Time (US and Canada)
Local country phone number found here: http://support.microsoft.com/globalenglish | Extension 1138300
We value your feedback.  My manager is Natesha Morrison (namorri), +1 (704) 430-4292

-----Original Message-----
From: Stefan Metzmacher <metze at samba.org> 
Sent: Friday, August 21, 2020 7:14 AM
To: Interoperability Documentation Help <dochelp at microsoft.com>; cifs-protocol at lists.samba.org
Subject: [EXTERNAL] MS-NRPC FullSecureChannelProtection

Hi DocHelp,

can you please make sure the exact behavior of HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\FullSecureChannelProtection = 1 is fully documented in MS-NRPC?

This is the change introduced by CVE-2020-1472.


More information about the cifs-protocol mailing list