In 2.10.1: Applying a wrong KDM first results in a decoding error shown below the progress bar. Then, when I click that encrypted content again, the app crashes. See screenshots.

I believe this is fixed now: please add a note if not.

The crash still occurs in 2.11.36 OS X - the behavior is as in the screenshots above - as long as an initial 'Needs KDM' is indicated in content list, a right click on the content/dcp is possible. After a wrong KDM has been assigned, the status bar in the lower right shows 'Error - could not decrypt KDM (...)'. So far, so good.
When I right click the content again to assign another, hopefully working KDM, DOM crashes.

• Carsten

Should be fixed by db19d69c0c33fe64cf60ec85bf59c4c15ec37383

Hmm, this seems to be a tough one - in 2.11.38, I can now right-click->Assign KDM as often as I want without crashing - that solves the issue should someone use a wrong KDM initially, then want's to correct his choice.
However, if I left-click on the encrypted DCP afterwards (still with 'Needs KDM' flagged), I still get the same crash as before.

Not such a big deal. Personally, I wish there would be a nice dialog saying 'Sorry, this KDM doesn't match the content you tried to assign it to', but, for now, it allows to select another, possibly working KDM.

• Carsten

That other crash should be fixed by 160a401d16e3962b10f3105e00992936a8188424 in 2.11.39.

Closing this again; the nicer-error idea is in 0001161.