ad-assurance - [AD-Assurance] FW: http://support.microsoft.com/kb/811833
Subject: Meeting the InCommon Assurance profile criteria using Active Directory
List archive
- From: Brian Arkills <>
- To: "" <>
- Subject: [AD-Assurance] FW: http://support.microsoft.com/kb/811833
- Date: Fri, 8 Mar 2013 19:02:54 +0000
- Accept-language: en-US
- Authentication-results: sfpop-ironport03.merit.edu; dkim=neutral (message not signed) header.i=none
I sent the following question off to the DS MVPs and AD product team representatives. I've gotten a response back that there is a special FIPS mailing list within Microsoft where my question has been sent along
to. I'll let folks know if/when I get something back on this. From: Brian Arkills
Does anyone know whether this FIPS setting also affects the encryption used by Active Directory for password encryption (and for the PEK encryption)? I suspect it doesn't, but I'd be really happy to learn that it does. :) If it doesn't, I think the KB should be modified to note that it doesn't affect all encryption processes that Windows uses so it isn't misleading. -B |
- [AD-Assurance] FW: http://support.microsoft.com/kb/811833, Brian Arkills, 03/08/2013
- [AD-Assurance] RE: http://support.microsoft.com/kb/811833, Capehart,Jeffrey D, 03/08/2013
- Re: [AD-Assurance] RE: http://support.microsoft.com/kb/811833, David Walker, 03/08/2013
- [AD-Assurance] RE: http://support.microsoft.com/kb/811833, Capehart,Jeffrey D, 03/08/2013
Archive powered by MHonArc 2.6.16.