DICOM @ OFFIS

There is no command line tool in DCMTK that would allow you to do this, but the underlying class library contains everything needed to implement such functionality. Look at the following sample code, which expects a DICOM dataset that has been already loaded ( DcmFileFormat::loadFile() ) and overwri...

The problem is related to the way you are inserting the pixel data into the dataset. Class DcmPixelData, which is used for this attribute, is able to manage both an uncompressed and one or more compressed versions of the same bitmap in memory at the same time. A call to putAndInsertUint8Array() will...

Another factor that limits the network throughput is the serial mode of operation: modality sends a single image (slice) receiver stored that image (perhaps including database operations) receiver send acknowledgement (C-STORE Response) back to modality modality sends second image... The DICOM netwo...

I see. If you can define a logical certificate store in Windows and only access that from your application, that would indeed be very useful as it would address the issue of renewing the certificates in the store before expiration, something for which Windows probably offers an automated solution. Y...

Other members of the DCMTK team (including the author of DcmTLSSCU) may disagree, but I think that we should declare DcmTLSSCU as deprecated and remove it from the toolkit after one or two stable releases. The problem with DcmTLSSCU is that it can only handle TLS connections, whereas DcmSCU can supp...

I have today committed a fix for the BUILD_SINGLE_SHARED_LIBRARY build. If that successfully passes our nightly build, it should be visible on the public git server in a few days. In the interim time, here's the patch: diff --git a/dcmdata/libdcxml/xml2dcm.cc b/dcmdata/libdcxml/xml2dcm.cc index 8454...

I think that in most cases using the Windows certificate store for DICOM TLS connections is an extremely bad idea. The Windows cert store is filled with the root certificates of all kinds of root CAs that should be trusted when Web servers are accessed from Internet Explorer or MS Edge. You don't wa...

I think that the template based mixin just created unneccessary complexity. Actually adding TLS support to a class derived from DcmSCU is quite trivial. There is no example in the public DCMTK yet, but some of the private modules already provide TLS support in DcmSCU based code. Note that this is a ...

I have today committed the fix to our testing branch. It will appear in the public git once it has successfully passed our nightly builds.

ANNOUNCEMENT Version 3.6.7 of the OFFIS DCMTK (DICOM toolkit) software is now available for public release. This release includes the following main changes over the previous version 3.6.6: - DCMTK 3.6.7 builds correctly on older and up-to-date versions of GNU gcc (4.8.5 to 10.2.0) Clang (3.4.2 to 1...

Thank you for the bug report. I have created a corresponding issue in our issue tracker: https://support.dcmtk.org/redmine/issues/1020.
This seems to be fairly straightforward to fix, but I need to test a fix anyway before committing it.

To my knowledge, TLS is used very little so far, and where it is used, it is primarily used for connections between healthcare provides, not within a hospital, although the rise of cybersecurity incidents may change this in the future. Although technically possible, the "anonymous" TLS mode where th...

When you run storescp in verbose mode (-v option), then it should print info messages like this: I: creating new subdirectory for study: ./NAME_20220502_160819943 You can try parsing these messages to identify the precise directory names. By default, these messages are printed to stderr, but you can...

As the author who "invented" that private SOP class 20 years ago, I have to add that at the time I did not see the drawbacks of that approach. Today I would probably do it differently: If you are running the server process (e.g. dcmqrscp or dcmpsrcv) in TLS mode and the certificate expires, you cann...

Hard to say. My guess would be that once you have pruned the Windows Certificate Store to a state that can be considered safe for the usage in the DICOM context, it will cause problems with other tools that use it (e.g. the Edge browser).