From 9b8d8083f0c4e5d9997bde56a054c7de7a96d16d Mon Sep 17 00:00:00 2001
From: NextTurn <45985406+NextTurn@users.noreply.github.com>
Date: Thu, 17 Oct 2019 00:00:00 +0800
Subject: [PATCH] Remove offline mode section from installation guide
---
doc/installation.md | 19 -------------------
1 file changed, 19 deletions(-)
diff --git a/doc/installation.md b/doc/installation.md
index 0b5100e..a3accb0 100644
--- a/doc/installation.md
+++ b/doc/installation.md
@@ -95,22 +95,3 @@ One way to deal with this is to ensure that .NET Framework 2.0 is installed thro
The way the runtime finds this file is by naming convention, so don't forget to rename a file based on your actual executable name (e.g. *myapp.exe*).
For more information, see [How to: Configure an App to Support .NET Framework 4 or later versions](https://docs.microsoft.com/dotnet/framework/migration-guide/how-to-configure-an-app-to-support-net-framework-4-or-4-5).
None of the other flags are needed.
-
-### WinSW Offline mode and Authenticode
-
-To work with UAC-enabled Windows, winsw ships with a digital signature.
-This causes Windows to automatically verify this digital signature when the application is launched.
-This adds some delay to the launch of the service, and more importantly, it prevents winsw from running in a server that has no internet connection.
-This is because a part of the signature verification involves checking certificate revocation list.
-
-To prevent this problem, create *myapp.exe.config* in the same directory as *myapp.exe* (renamed *WinSW.exe*) and put the following in it:
-
-```xml
-
-
-
-
-
-```
-
-For more information, see [\ Element](https://docs.microsoft.com/dotnet/framework/configure-apps/file-schema/runtime/generatepublisherevidence-element).