View Bug Details

IDProjectCategoryView StatusLast Update
0001888DCP-o-maticBugspublic2021-02-06 19:50 Assigned Tocarl  
PrioritylowSeveritytrivialReproducibilityhave not tried
Status resolvedResolutionfixed 
Platform64 bitOSLinuxOS VersionUbuntu
Product Version2.14.37 
Summary0001888: Minor points regarding exporting keys

This is a follow up to this bug:

I added a comment after it was fixed but probably it was never read - I think these issues still hold:

Thanks. Though there is now another issue: if I save a file as "certificate" (without extension), it gets saved as such. Now when I save another file as "certificate", it alerts me I already have a file like that, but it does not get shown in the file picker (only .dom files are shown. I think either 1) always add the .pem extension or 2) also allow non .dom files to be shown in the file picker.

a couple of another very minor points:

a.1) For the default name, should not it maybe include the Creator and Issuer fields from Preferences>General?
a.2)Also adding the word "leaf" to the "export KDM decription certificate" might make sense.
a.3)And the advanced submenus do not have default names (at least there the leaf/intermediate/root in the filename would make a lot of sense to me).

b) And regarding that, maybe Creator should be set by default to DCP-o-matic if this is to be trusted: ).

c) Oh, and regarding issuer and creator, maybe the followint line in the manual:
With these controls you can set the issuer and creator strings that will be put into the DCPs which you create.
should read something as:
With these controls you can set the issuer (typically you or your organization) and creator (application used to author the DCP, i.e. DCP-o-matic) strings that will be put into the DCPs which you create.

d)And I also believe that the line in the manual
<DCPIssuer> — Creator text to write into CPL files.
should be
<DCPCreator> — Creator text to write into CPL files.

(I hope you also see comments on closed bugs)

TagsNo tags attached.
Estimated weeks required
Estimated work required



2021-02-06 19:50

administrator   ~0004123

Hi, thanks for reporting all these things! They should all be fixed in v2.15.127, which will be uploaded in the next few days (at a guess).

@carl b43fa17ece8aacb7cbe85d62f055a50a6858ce0d and nearby stuff.

Bug History

Date Modified Username Field Change
2020-12-16 19:08 New Bug
2021-02-06 19:50 carl Assigned To => carl
2021-02-06 19:50 carl Status new => resolved
2021-02-06 19:50 carl Resolution open => fixed
2021-02-06 19:50 carl Note Added: 0004123