Sorry for spamming the list with a series of short messages this afternoon,
I was trying to keep up with Larry durning debugging...
Here is where we stand:
1) geoserver-2.10.0.exe has been signed with a SHA256 key
2) It is available from both ares
<http://ares.opengeo.org/geoserver/release/2.10.0/> and SF
<https://sourceforge.net/projects/geoserver/files/GeoServer/2.10.0/>
3) We expect to remain "unknown" to smarscreen - because it is not an
executable windows has seen before because it is brand new. This will
gradually be corrected as more people try the application ...
4) We can tell Microsoft about this new executable, using a "WACK" tool
that checks the installer and produces a report. When we run this tool we
fail a couple tests, and have to ask for an exception...
5) Why do we not pass - check the report attached to GEOS-7808
<https://osgeo-org.atlassian.net/browse/GEOS-7808>. Most of it amounts to
the uninstaller not being signed, and Larry has a workaround in mind.
How you can help?
- Download and run geoserver-2.10.0.exe so Microsoft can learn to trust it!
Even filling in a report for Microsoft only adds to our trust score...
- We have some extra metadata to fill in about our application in the
windows registry
--
Jody Garnett
------------------------------------------------------------------------------
The Command Line: Reinvented for Modern Developers
Did the resurgence of CLI tooling catch you by surprise?
Reconnect with the command line and become more productive.
Learn the new .NET and ASP.NET CLI. Get your free copy!
http://sdm.link/telerik
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
