Jacob Schloss

I also was looking at a workflow using `Botan::X509::create_cert_req` and then `Botan::X509_Object::make_signed` with an external PK_Signer, but ran into similar issues with a PKCS11 error. I was planning on using...

The supported mechanism types are 0x00000250 0x00000251 0x00000252 0x00001040 0x00001041 0x00001081 0x00001082 0x00001085 0x00001086 0x00001087 0x00001088 0x0000108A 0x0000108B 0x00001104 0x00001105 eg CKM_ECDSA but not CKM_ECDSA_SHA256

> * Define a new `Private_Key` type which holds internally your `PKCS11_ECDSA_PrivateKey` > * This private key implements `create_signature_op` and returns from there a `PK_Ops::Signature`. Basically this outer/wrapper `Signature` impl...

Got a good verification for the signature now - The inner Botan::PK_Signer needed to use Botan::Signature_Format::DerSequence format, I had Standard.

Bootloader support added in v0.2.1, just need to add the runtime component here.

The current call to include_directories seems to add a non-existent "cryptoauth" dir to the path for this file scope. I assume this isn't needed.

> This issue has been marked as stale - please confirm the issue still exists with the latest version of the library and update the issue if it remains yes

Yes, but this way I do not need to install the library and the list of directories needed is picked up by CMake in my parent project. I am building...

What I mean is using target_include_directories instead of include_directories will make building as a nested cmake project work, which is a common and useful set up especially when dealing with...

I've had some trouble with the cache server seeming to corrupt already-cached repos on client fetch/update with 6 CI machines. I'll try this patch out.