Re: Application segfaults after upgrade from 3.0.11 to 3.0.13

On Tue, 16 Jul 2024 14:40:59 -0400 Neil Horman wrote: > Can you post the stack trace of the segv here? Sure: Core was generated by `osslsigncode sign -pkcs11module /usr/lib/librtpkcs11ecp.so -pkcs11cert pkcs11:o'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x7fe9e87862

Re: Application segfaults after upgrade from 3.0.11 to 3.0.13

Can you post the stack trace of the segv here? On Tue, Jul 16, 2024 at 12:43 PM Victor Wagner wrote: > Hi! > > I'm using osslsigncode application on Debian 12 system (amd64) to sign > stuff with RSA key stored on hardware token with PKCS11 interface. > > osslsigncode (https://github.com/mtrojnar

Application segfaults after upgrade from 3.0.11 to 3.0.13

Hi! I'm using osslsigncode application on Debian 12 system (amd64) to sign stuff with RSA key stored on hardware token with PKCS11 interface. osslsigncode (https://github.com/mtrojnar/osslsigncode) seems to be well-behaved openssl application, which uses digest BIO and PKCS7 API, does no poking i