Mercurial > hg > orthanc-book
comparison Sphinx/source/faq/dicom-tls.rst @ 759:94f5fc38b927
clarifications
author | Sebastien Jodogne <s.jodogne@gmail.com> |
---|---|
date | Sat, 28 Aug 2021 10:21:27 +0200 |
parents | 980ffad93dc5 |
children | a714c5fdc4cf |
comparison
equal
deleted
inserted
replaced
758:77496fd36a96 | 759:94f5fc38b927 |
---|---|
84 | 84 |
85 **Important:** `DCMTK 3.6.4 seems to have an issue with DICOM TLS | 85 **Important:** `DCMTK 3.6.4 seems to have an issue with DICOM TLS |
86 <https://forum.dcmtk.org/viewtopic.php?t=5073>`__, which produces the | 86 <https://forum.dcmtk.org/viewtopic.php?t=5073>`__, which produces the |
87 errors ``DUL secure transport layer: no suitable signature algorithm`` | 87 errors ``DUL secure transport layer: no suitable signature algorithm`` |
88 (in the DICOM SCP) and ``DUL secure transport layer: sslv3 alert | 88 (in the DICOM SCP) and ``DUL secure transport layer: sslv3 alert |
89 handshake failure`` (in the DICOM SCU). Make sure to use either DCMTK | 89 handshake failure`` (in the DICOM SCU). This problem is not specific |
90 3.6.2 or DCMTK 3.6.6. In particular, Debian Buster (10) will use DCMTK | 90 to Orthanc, as it also occurs between two command-line tools of the |
91 3.6.4 and should be avoided in non-static builds of Orthanc, or if | 91 DCMTK 3.6.4 suite. Make sure to use either DCMTK 3.6.2 or DCMTK |
92 using the DCMTK command-line tools. | 92 3.6.6. In particular, Debian Buster (10) uses DCMTK 3.6.4 and should |
93 be avoided in non-static builds of Orthanc, or if using the DCMTK | |
94 command-line tools. | |
93 | 95 |
94 | 96 |
95 | 97 |
96 Examples | 98 Examples |
97 -------- | 99 -------- |