Cannot access connector_server from yubihsm-shell and connector_server_cli from auth_key by running tmkms yubihsm-server about tmkms HOT 3 CLOSED

This is likely caused by an incompatibility between the latest yubihsm-shell and the connector server built into TMKMS.

One thing that would be helpful for debugging is if you could run the normal yubihsm-connector service and post the response from the /connector/status endpoint.

Otherwise, I will try to find some time to debug this, but it probably won't be soon. If you can get me the /connector/status endpoint response, I can probably look at it sooner.

from tmkms.

• Hi, @tony-iqlusion. Thanks for replying We have started using tmkms for signing Mainnet validators a few days back.
• However, We had to remove the connector_server from the yubihsm_config and run the tmkms server because of critical urgency.
• We are able to perform the signing operations well. But cannot access the yubihsm-shell separately.
• Now we don't have the option to stop the running tmkms server and run the yubihhsm-connector server.
• If we run the yubihsm-connector server. It says USB is busy because of the existing USB allotment with thetmkms server.
• As far as I remember. /connector/status of yubihsm-connector server resulted same as the below-mentioned status.

status
OK
serial
*
version
0.38.0
pid
11319
address
127.0.0.1
port
12345

Hope This will be resolved soon. So that we can use this feature in further HSM devices.
Regards.

from tmkms.

This much suggests that it isn't parsing the status correctly:

[LIB - INF 05:34:31.418719] lib_util.c:139 (parse_status_data): response from connector
[LIB - INF 05:34:31.418755] lib_util.c:140 (parse_status_data): has device: no
[LIB - INF 05:34:31.418778] lib_util.c:141 (parse_status_data): version: 0.0.0
[LIB - INF 05:34:31.418804] lib_util.c:143 (parse_status_data): pid: 0
[LIB - INF 05:34:31.418830] lib_util.c:144 (parse_status_data): address: 
[LIB - INF 05:34:31.418856] lib_util.c:145 (parse_status_data): port: 0

Unfortunately I've just recently moved and I'm not sure where my development YubiHSM is, so I can't easily debug this either.

You might try an older release of the Yubico SDK, i.e. older version of yubihsm-shell, and see if that fixes the problem.

from tmkms.