View Bug Details

IDProjectCategoryView StatusLast Update
0002837DCP-o-maticBugspublic2024-09-04 14:45
ReporterwalkerW Assigned Tocarl  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
Platform64-bitOSWindowsOS Version10
Product Version2.16.86 
Summary0002837: KDM and DKDM
Description

I made an encryption DCP on [PC-1] and made "KDM-2" (which is NOT DKDM) for [PC-2].

Then I added the "KDM-2" above into KDM Creator in [PC_2] without error.

And then I created "KDM-3" on [PC-2] for [PC-3] and the DCP play with "KDM-3" on [PC-3] without any problem.

That process chain works but my question is: it that should be works in that way?

Becuse I think KDM Creator should only accept "DKDM", not "KDM".

Otherwise clients can use the "KDM" from me and produce more KDMs to others within themselve.

Please let me know if any steps I might be wrong or anything I misunderstood. Thanks!

TagsNo tags attached.
Branch
Estimated weeks required
Estimated work required

Activities

carl

2024-06-27 15:46

administrator   ~0006456

As I understand it this is all working as intended - once you give somebody else a KDM targeted at a system for which they know the private key (i.e. for a computer, not a projection system) you give them the encryption keys, and so you have to trust them. I don't think there's much we can do about that.

Are you suggesting that DCP-o-matic prevents people making new KDMs using a KDM that is not explicitly marked as a DKDM? Since there is no difference between DKDM and KDM (except for what system it is targeted at) this would be difficult, and easy to work around.

Did I misunderstand something?

walkerW

2024-06-27 15:52

reporter   ~0006457

My bad, I am omitted the part of "computer and projection system".

I understand now. Thank you for explaining.

Good day and appreciate your efforts!

carl

2024-06-27 15:55

administrator   ~0006458

No problem!

Bug History

Date Modified Username Field Change
2024-06-27 15:41 walkerW New Bug
2024-06-27 15:46 carl Assigned To => carl
2024-06-27 15:46 carl Status new => feedback
2024-06-27 15:46 carl Note Added: 0006456
2024-06-27 15:52 walkerW Note Added: 0006457
2024-06-27 15:52 walkerW Status feedback => assigned
2024-06-27 15:55 carl Note Added: 0006458
2024-06-27 15:55 carl Status assigned => resolved
2024-06-27 15:55 carl Resolution open => no change required
2024-09-04 14:45 carl Status resolved => closed