Wiktor Kwapisiewicz

Hmm... Yeah, it looks problematic. I'm not the author of this code but I assume the intention is to allow multiple threads access through Arc to the Impl struct and...

Thanks for the updates! I did take some time to add the iterator API on top of it: https://github.com/wiktor-k/rust-cryptoki/commit/1c00f377a10e45260375fcd811ab566209498d00 *Edit*: I've added the no-compile test to test for the case...

Closing, as this has already been implemented. Thanks for your time! 👋

I'm not sure if you can query these attributes directly. IIUC you need to first get the X.509 certificate object from the card (for example using this object class: https://docs.rs/cryptoki/latest/cryptoki/object/struct.ObjectClass.html#associatedconstant.CERTIFICATE)...

I think you used [`Attribute::Value`](https://docs.rs/cryptoki/latest/cryptoki/object/enum.Attribute.html#variant.Value) right? (In general it's good to paste your solution for the next person that has the same problem :sweat_smile: )

Yep, most certainly! I was just today casually browsing documentation and the lack of doctests saddens me 😔 I think adding examples to functions would be the best. Just in...

Just out of curiosity what would be the use case? Cryptoki frequently needs PKCS11 driver anyway and you'd have to be able to access the device somehow (eg. via pcsclite).

I agree with this change although I remember someone (@ionut-arm) had concerns about bumping version from v2.4 to v3.0. This PR seems to solve issues reported with the previous approach:...

I don't mind v3.0 but Parsec, that's a main client of this crate, may. Let's wait to see what Ionut has to say (to fast lane it we could ask...

Ough! That's bad! Yep, then definitely as it stands it cannot go through... :cry: