pull down to refresh
.0
Okay. v13.1.1 is tagged but not marked as release yet for me. That supposedly will fix this issue.
From the commit in there:
scope TLS bypass to .onion HTTPS endpoints
And from the PR @evankaloudis did to the tor dependency I mention above:
Adds atrust_invalid_certs: booleanfield toHttpGetParams,HttpPostParams,HttpPutParams, andHttpDeleteParams. Whentrue, the underlyingreqwest::Clientis built with.danger_accept_invalid_certs(true)so connections to endpoints with self-signed certificates succeed. Defaults tofalse, so existing callers are unaffected.
Perhaps Evan can advice on release timing / downgrading back to v13.0.2
Damn, you are good! Thank you
Maybe one thing you could try in the meantime (this is how I deal with it on my own PKI) is to import your cert into Android and trust it there. Then it should not throw. However, I do this with an actual private CA, not a self-signed thing, and mTLS, so it may be that for simple self-signed, there are issues. Maybe a stacker that uses self-signed certs on Android knows more.
I don't know. If it matters, I run graphene.It's no big deal. The desktop CLN GUI wallet is fine for now
Haha thanks. I review Zeus like I review Signal because I really want to use it again (current live LN wallets are Blixt) so it is my duty to my own security to know everything, because it would touch my money, directly.
Right now it's still too unstable, but I have hope. Evan is doing an awesome job.
There's definitely something changed there. I have been really nervous to update because of the switch to
react-native-nitro-torbecause I have a million process findings on that repo.Are you on v13.1.1? or .0?