From: Andy Polyakov <appro@openssl.org>
Date: Fri, 9 Jul 2010 14:32:22 +0000 (+0000)
Subject: INSTALL.W32: mention _OPENSSL_isservice() [from HEAD].
X-Git-Tag: OpenSSL_1_0_1-beta1~495
X-Git-Url: https://git.openssl.org/?p=openssl.git;a=commitdiff_plain;h=30dd06812e0ded4f5dd0b3643f1c6e9bc13c589b

INSTALL.W32: mention _OPENSSL_isservice() [from HEAD].
PR: 2194
---

diff --git a/INSTALL.W32 b/INSTALL.W32
index 77441f1ef3..a0886b3d77 100644
--- a/INSTALL.W32
+++ b/INSTALL.W32
@@ -297,7 +297,18 @@
  desktop, which is not available to service processes. The toolkit is
  designed to detect in which context it's currently executed, GUI,
  console app or service, and act accordingly, namely whether or not to
- actually make GUI calls.
+ actually make GUI calls. Additionally those who wish to
+ /DELAYLOAD:GDI32.DLL and /DELAYLOAD:USER32.DLL and actually keep them
+ off service process should consider implementing and exporting from
+ .exe image in question own _OPENSSL_isservice not relying on USER32.DLL.
+ E.g., on Windows Vista and later you could:
+
+	__declspec(dllexport) __cdecl BOOL _OPENSSL_isservice(void)
+	{   DWORD sess;
+	    if (ProcessIdToSessionId(GetCurrentProcessId(),&sess))
+	        return sess==0;
+	    return FALSE;
+	}
 
  If you link with OpenSSL .DLLs, then you're expected to include into
  your application code small "shim" snippet, which provides glue between