Comment 17 for bug 2028936

Following up on the regression testing discussion and desire,
I like the hint to base the regression testing on the pkey kernel module modifications.
So using the libzpc tests (directly from upstream) is a good option:
https://github.com/opencryptoki/libzpc#Testing

libzpc's runtest runs by default 140 tests from 13 test suites
and allows to explicitly enable EC test in combination with EP11 using the env. var.
ZPC_TEST_EC_KEY_TYPE=ZPC_EC_KEY_TYPE_EP11

These are the additional steps that are needed on Ubuntu to get the test suite going:
  ~$ git clone https://github.com/opencryptoki/libzpc
  ~$ sudo apt install libjson-c-dev cmake
  ~$ cd libzpc/
  ~/libzpc$ mkdir build && cd build
  ~/libzpc/build$ cmake -DBUILD_TEST=ON ..
  [ in case a proxy is required, like in our case: $ export https_proxy="http://your.proxy:3128/" ]
  ~/libzpc/build$ make
  ~/libzpc/build$ ./runtest

Notice that this is currently not possible with the libzpc package we have in 'noble',
since it req. commits that are not yet included in a published version.

But it's planned to release a new version of libzpc in time for 'noble' feature freeze,
that will allow me to version bump libzpc to that new and upcoming version (even if not strictly needed for the regression test here, however it's nice and clean to have it in the archive).

I'll update the SRU justification in the Bug description with these add. steps for regression testing and update the status from Incomplete again to New.