scsh get error #95

Closed
opened 2025-05-23 10:53:10 +08:00 by IsayIsee · 1 comment

I encountered the following error when importing p12 . Once this error occurs, the KeyManager cannot be loaded again unless the HSM is reinitialized or delete import data

GPError: Card (CARD_INVALID_SW/24834) - "Unexpected SW1/SW2=6102 (Normal processing: 2 additional bytes available) received" in D:\Program Files\scsh\scsh\sc-hsm\SmartCardHSM.js#650
at D:\Program Files\scsh\scsh\sc-hsm\SmartCardHSM.js#650
at D:\Program Files\scsh\scsh\sc-hsm\SmartCardHSM.js#1899
at D:\Program Files\scsh\keymanager\keymanager.js#1246
at D:\Program Files\scsh\keymanager\keymanager.js#1653
at D:\Program Files\scsh\keymanager\keymanager.js#300
at D:\Program Files\scsh\keymanager\keymanager.js#40
at D:\Program Files\scsh\keymanager\keymanager.js#3280

From then on, every time I attempt to load the KeyManager, the same error is reported

I encountered the following error when importing p12 . Once this error occurs, the KeyManager cannot be loaded again unless the HSM is reinitialized or delete import data GPError: Card (CARD_INVALID_SW/24834) - "Unexpected SW1/SW2=6102 (Normal processing: 2 additional bytes available) received" in D:\Program Files\scsh\scsh\sc-hsm\SmartCardHSM.js#650 at D:\Program Files\scsh\scsh\sc-hsm\SmartCardHSM.js#650 at D:\Program Files\scsh\scsh\sc-hsm\SmartCardHSM.js#1899 at D:\Program Files\scsh\keymanager\keymanager.js#1246 at D:\Program Files\scsh\keymanager\keymanager.js#1653 at D:\Program Files\scsh\keymanager\keymanager.js#300 at D:\Program Files\scsh\keymanager\keymanager.js#40 at D:\Program Files\scsh\keymanager\keymanager.js#3280 From then on, every time I attempt to load the KeyManager, the same error is reported

I have attempted to generate and import numerous certificates, but I was unable to reproduce the issue. Since the problematic certificate is a CA certificate currently in use, it cannot be uploaded. However, I found that shortening the name of the certificate during import allowed it to be imported successfully. I also tried creating certificates with longer names, and they imported without any issues. I am unsure where the exact problem lies. Additionally, I discovered that creating an AES KEY in scsh with the name "TTTTTTTTTTTTT" triggers the same error. All tests were conducted after initializing the HSM with pico-hsm-tool.py

if i use pkcs11-tool --module sc-hsm-pkcs11.dll -l --pin 123456 --keygen --key-type AES:16 --id 1 --label "TTTTTTTTTTTTT" the aes key can be gen

I have attempted to generate and import numerous certificates, but I was unable to reproduce the issue. Since the problematic certificate is a CA certificate currently in use, it cannot be uploaded. However, I found that shortening the name of the certificate during import allowed it to be imported successfully. I also tried creating certificates with longer names, and they imported without any issues. I am unsure where the exact problem lies. Additionally, I discovered that creating an AES KEY in scsh with the name "TTTTTTTTTTTTT" triggers the same error. All tests were conducted after initializing the HSM with pico-hsm-tool.py if i use pkcs11-tool --module sc-hsm-pkcs11.dll -l --pin 123456 --keygen --key-type AES:16 --id 1 --label "TTTTTTTTTTTTT" the aes key can be gen
Sign in to join this conversation.