Subj : certtool --import fails with CryptLib error -43 (CRYPT_ERROR_NOTFOUND)
To   : GitLab note in main/sbbs
From : Randy Blodgett
Date : Sat Aug 08 2026 15:28:35

https://gitlab.synchro.net/main/sbbs/-/issues/1216#note_10074

Hi Deuce,

Thanks for taking a look. I want to make sure I understand the relationship before dropping this — the two reports have different error codes and different input paths:

* #1111: CryptLib error **-22**, importing a PKCS12 container (built via `openssl` with legacy `PBE-SHA1-3DES`) using `certtool.js --import-pkcs12`
* #1216 (this one): CryptLib error **-43 (CRYPT_ERROR_NOTFOUND)**, importing a combined PEM file (key+cert+chain, matching the wiki's documented example) using plain `certtool --import`

Could you help me understand how these trace back to the same underlying cause? If it's a shared code path in cryptlib's import handling that just surfaces different error codes depending on the input format, that's good to know — I just want to make sure the PEM-import case (which seems like the more common/documented path per the wiki) isn't getting lost if it turns out to be a distinct issue.

Thanks for your time on this.
--- SBBSecho 3.37-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.