barower

`cargo install --locked cargo-outdated` still gives this error

Thanks! I've looked there and it seems like compiling `libp11` without linking it to `libcrypto.so` in theory could do the trick: https://github.com/openssl/openssl/issues/11294#issuecomment-597010961 https://github.com/openssl/openssl/issues/11294#issuecomment-598106303 If I'm not mistaken [it would not...

>This comment describes a very special theoretical scenario where your statically linked application exposes all the OpenSSL symbols that are needed by your engine. I don't think your application does...

After quick looking I've noticed that OpenSSL 3.0.2 is already the default on my Ubuntu 22.04, and this is what I've been compiling `libp11` against so far ``` $ ldd...

I've set breakpoint at [this line](https://github.com/OpenSC/libp11/blob/master/src/eng_front.c#L92), stepped few instructions and landed at address 0x7ffff7bbcf70, where ``` (gdb) info files ... 0x0000000000402000 - 0x00000000007fe034 is .text ... 0x00007ffff7ab4000 - 0x00007ffff7d10e22 is...

I've tried to recreate roughly what `rk_sign_tool` would do: ```c #include #include int main(int argc, char *argv[]) { ENGINE *engine; if (argc != 2) { printf("Usage: %s \n", argv[0]); return...

I've come back to this issue just recently and I can confirm that @frestr's solution works on RK3588. Thank you for finding this! As a side note, to anyone struggling...

I'd like to prefer using my own `rust-analyzer`'s version of choice, but it seems like `rustup` knows better 🤷 It's weird and confusing, because the binary in `~/.cargo/bin/` is created...