retain client certs in maj::server::Request #7
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
i noticed that the certs field is always empty, and it would be neat if that were not the case. (i'll prob work on a pull request for it in a bit.)
oh god this is blocked on https://github.com/async-rs/async-tls/issues/33
well i have a change in https://tulpa.dev/boringcactus/maj/src/branch/preserve-client-certs that at least halfway works. the other end is you need a
ClientCertVerifier
that actually handles Gemini client certs well - I wasn't having any luck withAllowAnyAnonymousOrAuthenticatedClient
even though by all rights that should work. i threw together https://git.sr.ht/~boringcactus/gemifedi/tree/main/src/client_cert_fix.rs which technically works but is also an extremely bad idea.I'll take a look, I've been considering ripping out async-std and replacing it with Tokio. I think that its TLS wrapper has client cert support. Thanks!
if y'all find a way to do this without implementing a new ClientCertVerifier, that'd be hella cool. afaik the whole rust-gemini sever ecosystem uses the same hack, or at the very least northstar/kochab and stargazer all do.