Mercurial > hg > orthanc-book
comparison Sphinx/source/faq/security.rst @ 546:7c4ef4411992
stunnel
author | Sebastien Jodogne <s.jodogne@gmail.com> |
---|---|
date | Wed, 18 Nov 2020 20:17:14 +0100 |
parents | d7ec7ea133b8 |
children | 4f3a6145ae34 |
comparison
equal
deleted
inserted
replaced
545:931052bd5a53 | 546:7c4ef4411992 |
---|---|
200 **Remark:** As of Orthanc 1.8.0, `DICOM TLS encryption | 200 **Remark:** As of Orthanc 1.8.0, `DICOM TLS encryption |
201 <https://www.dicomstandard.org/using/security/>`__ is not supported | 201 <https://www.dicomstandard.org/using/security/>`__ is not supported |
202 yet. As a temporary workaround, `it has been reported | 202 yet. As a temporary workaround, `it has been reported |
203 <https://www.digihunch.com/2020/11/medical-imaging-web-server-deployment-pipeline/>`__ | 203 <https://www.digihunch.com/2020/11/medical-imaging-web-server-deployment-pipeline/>`__ |
204 that the "*SSL Termination for TCP Upstream Servers*" feature of nginx | 204 that the "*SSL Termination for TCP Upstream Servers*" feature of nginx |
205 can be used to emulate DICOM TLS. We are looking for :ref:`an | 205 can be used to emulate DICOM TLS. Another option is to use `stunnel |
206 industrial sponsor <contributing>` to implement DICOM TLS, as it is | 206 <https://www.stunnel.org/>`__. We are looking for :ref:`an industrial |
207 useful in enterprise and cloud environments. | 207 sponsor <contributing>` to implement DICOM TLS in the core of Orthanc, |
208 as this feature is dedicated to enterprise and cloud environments. |