[gimp-web] Added news item about the windows installer corruption warnings

[Michael Schumacher <schumaml src gnome org>]

commit 95d114bc2c9925c34b86d8d259bb251ff075bee5
Author: Michael Schumacher <schumaml gmx de>
Date:   Thu Mar 17 22:28:21 2016 +0100

    Added news item about the windows installer corruption warnings

 ...016-03-17 Corrupt Windows Installer Warnings.md |   16 ++++++++++++++++
 1 files changed, 16 insertions(+), 0 deletions(-)
---
diff --git a/content/news/2016-03-17 Corrupt Windows Installer Warnings.md b/content/news/2016-03-17 Corrupt 
Windows Installer Warnings.md
new file mode 100644
index 0000000..db46440
--- /dev/null
+++ b/content/news/2016-03-17 Corrupt Windows Installer Warnings.md     
@@ -0,0 +1,16 @@
+Title: Corrupt Windows Installer Warnings
+Date: 2016-03-17
+Category: News
+Authors: Michael Schumacher
+Slug: corrupt-windows-installer-warnings
+Summary: The Windows installer packages for GIMP 2.8.16 are reported as corrupt when downloaded with the 
Microsoft Edge or Internet Explorer 11 browsers. This is due to a policy by Microsoft.
+
+We are receiving reports that some users can't download our [installer packages](//www.gimp.org/downloads/) 
for the Microsoft Windows platforms. Microsoft Edge and Internet Explorer 11 [mark them as 
corrupt](//social.technet.microsoft.com/wiki/contents/articles/32288.windows-enforcement-of-authenticode-code-signing-and-timestamping.aspx#Signature_Verification_Failure_Experience)
 and discourage users from running them.
+
+Turns out this is a policy change by Mircosoft, gone into effect on 2016-01-01, and affecting all kinds of 
security certificates as of specific deadlines - this includes code signing certificates. Jernej Simončič, 
who creates the Windows installer packages, signs them to make their authenticity verifiable, but the way 
this signature is done is no longer considered safe by Microsoft (there are justified technical reasons, 
actually).
+
+Administrators and users of Microsoft Windows systems are well advised to make themselves familiar with the 
implications of this policy; the TechNet article on the subject is available at [Windows Enforcement of 
Authenticode Code Signing and 
Timestamping](//social.technet.microsoft.com/wiki/contents/articles/32288.windows-enforcement-of-authenticode-code-signing-and-timestamping.aspx).
+
+We are working to resolve the issue - this requires a more recent code-signing certificate, and signing the 
installer packages with it. Stay tuned for updates.
+
+As a workaround, you can use other web browsers to download the installer packages.