Add list-profiles sub-command to p11-kit cmd tool

[ZoltanFridrich]

Adds list-profiles command for listing profiles that are supported by a token
usage: p11-kit list-profiles pkcs11:token

[coveralls]

Coverage: 70.448% (+0.07%) from 70.38% when pulling 877dadc on ZoltanFridrich:zfridric_devel4 into 3f2c94f on p11-glue:master.

[ueno]

I think this PR really deserves a test case. The below is what I used for testing it locally, but ideally there should be a test integrated into the test suite:

1. Modify p11-kit/mock-module-ep.c

diff --git a/p11-kit/mock-module-ep.c b/p11-kit/mock-module-ep.c
index 4324433..4845dcd 100644
--- a/p11-kit/mock-module-ep.c
+++ b/p11-kit/mock-module-ep.c
@@ -39,6 +39,14 @@
 
 #include "mock.h"
 
+static CK_RV
+override_initialize (CK_VOID_PTR init_args)
+{
+       CK_RV rv = mock_C_Initialize (init_args);
+       mock_module_add_profile (MOCK_SLOT_ONE_ID, CKP_PUBLIC_CERTIFICATES_TOKEN);
+       return rv;
+}
+
 #ifdef OS_WIN32
 __declspec(dllexport)
 #endif
@@ -47,6 +55,7 @@ C_GetFunctionList (CK_FUNCTION_LIST_PTR_PTR list)
 {
        mock_module_init ();
        mock_module.C_GetFunctionList = C_GetFunctionList;
+       mock_module.C_Initialize = override_initialize;
        if (list == NULL)
                return CKR_ARGUMENTS_BAD;
        *list = &mock_module;

2. Build

meson setup _build -Dprefix=/usr
meson compile -C _build

4. Copy mock-one.so and one.module

cp _build/p11-kit/mock-one.so /usr/lib64/pkcs11
cp p11-kit/fixtures/system-modules/one.module /usr/share/p11-kit/modules

5. Run p11-kit list-profiles

_build/p11-kit/p11-kit list-profiles 'pkcs11:model=TEST%20MODEL;manufacturer=TEST%20MANUFACTURER;serial=TEST%20SERIAL;token=TEST%20LABEL'

[ueno]

One way to test this would be to create a separate p11-kit executable for testing (e.g., p11-kit-testable), which links to libp11-kit-testable.a. The it should be able to access the mock modules installed under p11-kit/fixtures/.

[ZoltanFridrich]

One way to test this would be to create a separate p11-kit executable for testing (e.g., p11-kit-testable), which links to libp11-kit-testable.a. The it should be able to access the mock modules installed under p11-kit/fixtures/.

I thought that I might do it similar to test-iter where I would include the list-profiles.c and supply my own argv argc to the p11_kit_list_profiles, then I would redirect the stdout through pipe and read whether it contains correct profiles.

[ueno]

I thought that I might do it similar to test-iter where I would include the list-profiles.c and supply my own argv argc to the p11_kit_list_profiles, then I would redirect the stdout through pipe and read whether it contains correct profiles.

I'm not sure if it makes sense to test commands in C rather than simple shell scripts, given we intend to add more subcommands (e.g., #394). With shell script, you can simply diff the output against the expected one.