Comment 1 for bug 2018911

The release-cycles of Ubuntu 22.04/jammy and opencryptoki weren't very well aligned (during jammy development), and it was decided to take a snapshot of opencryptoki 3.17 "+ commits up to b40982e" as of date 20220202 (which is encoded in the DEB package version as '3.17.0+dfsg+20220202.b40982e').
This can be a bit confusing (since I believe this package is closer to 3.18 than to 3.17) - and we usually avoid creating such snapshot packages, but in this case we wanted to have several new features incl. for 22.04/LTS.
I checked that the strength.conf is not part of the package (but the -example is).
But we can included it and thus ensure that the file permissions are 640.
I'm going to incl. everything that is generated under /etc/opencryptoki to the package and explicitly set strength.conf to 640 for all opencryptoki packages for jammy (which is 3.17+) and newer (up to mantic).