Support for transparent SNI proxying about tokio-rustls HOT 4 OPEN

It looks like all you need is a reader that caches the bytes read, which doesn't need to be in tokio-rustls, you can put it in your own crate.

from tokio-rustls.

@quininer can you describe a bit more how that would work? From what I understand of how the LazyConfigAcceptor works, once accept has returned here I'm not able to get the raw IO stream back (via take_io), which means it's not possible with the existing API to get back the raw IO stream while also having access to the ClientHello.

Maybe I could pass a RefCell into the LazyConfigAcceptor though... that could work as a one-off solution. But is this not a use-case the crate would want to support in a cleaner way?

from tokio-rustls.

@mediocregopher see tokio-rs/tls#144 (comment)

We can access &mut IO via Accept, but it would be nice to provide an into_inner to StartHandshake as well.

from tokio-rustls.

Thanks, that makes sense. I've made a new branch with that change here: https://code.betamike.com/micropelago/tokio-rustls/commit/3d462a1d97836cdb0600f0bc69c5e3b3310f6d8c

and moved all the rest of the AsyncRead wrapping code into my application.

from tokio-rustls.