# HG changeset patch
# User Sebastien Jodogne <s.jodogne@gmail.com>
# Date 1605169584 -3600
# Node ID d7ec7ea133b8e738e5b6073ece09da6f956e2a5d
# Parent  fd340103904cf502a6d3017e926a67cd9048a8e4
note about nginx to emulate dicom tls

diff -r fd340103904c -r d7ec7ea133b8 Sphinx/source/faq/security.rst
--- a/Sphinx/source/faq/security.rst	Mon Nov 09 16:19:15 2020 +0100
+++ b/Sphinx/source/faq/security.rst	Thu Nov 12 09:26:24 2020 +0100
@@ -199,6 +199,9 @@
 
 **Remark:** As of Orthanc 1.8.0, `DICOM TLS encryption
 <https://www.dicomstandard.org/using/security/>`__ is not supported
-yet. We are looking for :ref:`an industrial sponsor <contributing>` to
-get this feature implemented, as it is useful in enterprise and cloud
-environments.
+yet. As a temporary workaround, `it has been reported
+<https://www.digihunch.com/2020/11/medical-imaging-web-server-deployment-pipeline/>`__
+that the "*SSL Termination for TCP Upstream Servers*" feature of nginx
+can be used to emulate DICOM TLS. We are looking for :ref:`an
+industrial sponsor <contributing>` to implement DICOM TLS, as it is
+useful in enterprise and cloud environments.