-
Notifications
You must be signed in to change notification settings - Fork 3
libsiguldry_pkcs11.so is rather verbose #172
Copy link
Copy link
Open
Description
By default, it logs at INFO level to stderr.
This means while using it from tools like pesign you'll see something like:
>>> INFO siguldry_pkcs11: return=0
>>> INFO C_Initialize{pInitArgs=0x5619b00be620}: siguldry_pkcs11: new
>>> INFO C_Initialize{pInitArgs=0x5619b00be620}:new{socket_path="/run/siguldry-client-proxy/siguldry-client-proxy.socket"}: siguldry::client::proxy: new
>>> INFO C_Initialize{pInitArgs=0x5619b00be620}:new{socket_path="/run/siguldry-client-proxy/siguldry-client-proxy.socket"}: siguldry::client::proxy: close
>>> INFO C_Initialize{pInitArgs=0x5619b00be620}:list_keys: siguldry::client::proxy: new
>>> INFO C_Initialize{pInitArgs=0x5619b00be620}:list_keys: siguldry::client::proxy: close
>>> ERROR C_Initialize{pInitArgs=0x5619b00be620}: siguldry_pkcs11: Failed to retrieve a list of keys from the server via the proxy error=channel closed
>>> INFO C_Initialize{pInitArgs=0x5619b00be620}: siguldry_pkcs11: return=6
>>> INFO C_Initialize{pInitArgs=0x5619b00be620}: siguldry_pkcs11: close
It should maybe default to WARN. It might also be best to emit to the systemd journal by default, too.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels