Data Center Security

Hi, Hope Symantec is aware of this below Microsoft update..

Change in how signatures are verified for binaries signed with the Windows Authenticode signature format Effective from:  August 12, 2014.

After 12th Aug the new default behavior for Windows Authenticode signature verification will no longer allow extraneous information in the WIN_CERTIFICATE structure. Note that after August 12, 2014, Windows will no longer recognize non-compliant binaries as signed.

The Security bulletin for this patch is : https://support.microsoft.com/kb/2893294

Concerned Microsoft Security Advisory : https://technet.microsoft.com/library/security/2915720

 Known issues as of now :

1. Windows server 2003 :  The Remote Desktop Services service may not start – Workaround/ solution as in word doc.
2. For Windows Vista or Windows Server 2008:  After you install this security update on a computer that is running Windows Vista or Windows Server 2008, the computer name might change to "MINWINPC." When this problem occurs, you cannot log on to computer even if you restart the computer. When you try to log on, you may receive an error message that resembles the following:  The username or password is incorrect.

Workaround/ solution as in word doc.

3. For Non MS products : Currently a very non descriptive response has been shared by MS : “In a nut shell, if you are using a components which is not following the standards, it will be considered unsigned.”
4. Information requested from MS for known instance of issues with other products.

Does this affect SDCSS funtionality? or is there any action required from SEP?

Regards,

Sankara Subramanian

Hi All,

Got an update from Microsoft that, we can ignore until further notification from Microsoft.

Thanks,

Please refer the below thread

https://www-secure.symantec.com/connect/forums/sep-vs-change-how-signatures-are-verified-binaries-signed-windows-authenticode-signature-form

By,

Dhasan