Reagan

Yes, I was attempting to do that, but it seems cargo will refuse to have both of them as a dependency (even optional?) because of the `links` field ([doc](https://doc.rust-lang.org/cargo/reference/resolver.html#links)): >...

@NobodyXu thanks, I agree and think that is the best way forward. I'm still confused on how to make liblzma an optional dependency and satisfy cargo - I'll make my...

> I think you can do Thanks! Unfortunately, cargo seems to still complain about the linkage :( (see: https://github.com/rust-lang/cargo/issues/5969#issuecomment-1313225094). I've just pushed my code with the cfg option. Manually adding/removing...

Yeah, I agree. This does seem simpler for cargo to support than linkage conflicts between optional dependencies.

Thanks! Will close this then.

dumpasn1 output ``` 0 5911: SEQUENCE { 4 9: OBJECT IDENTIFIER signedData (1 2 840 113549 1 7 2) 15 5896: [0] { 19 5892: SEQUENCE { 23 1: INTEGER...

Hmmm, it looks like it's wrapped in `ContentInfo`, but I get a new error: ```rust use std::fs::read; use cms::{cert::x509::der::{Decode, Encode}, content_info::ContentInfo, signed_data::SignedData}; use const_oid::db::rfc6268::ID_SIGNED_DATA; fn main() { let cms_string =...

Wow, thank you for your detailed response! It would be nice for me to use the certificate, so I will take a closer look at attempting to parse it. You...

Hmmm, I took a closer look at the standard, and the `dumpasn1` and this caught my eye: ``` ... 4143 727: [1] { 4147 576: SEQUENCE { 4151 1: INTEGER...

Another reason why this would be a good idea: it would be easier to cross compile.