DRAFT: apple network extension support in rama#836
Draft
Conversation
GlenDC
added
enhancement
- still very rough (rough in the diamond ;)) - still waiting on apple for proper team entitlements *sigh* wall - need to still start on proc-macro crate for making contract layer invisible - need to still write documentation - a lot more testing... like al ot more - still need to improve this and underlying code further... but we are starting to get somewhere
also hugely simplify and refactor tcp connector using the new capabilities in dns (streaming + happy eyeball auto resolver next step: use it also in UDP for some new helpers there
also split tproxy exmaple in sub files to make more clear what is custom ... soon we'll make it even better with the proc macro
also drop direction... transparent proxy can only be outbound.. d'uh...
and decouple prefix from network rule
... will need to do better ping-pong of protocols between c, p and s to do well
next up: make such socks5 proxy relay a reusable block, as it is easily shared, making it: a. easier to update for all when we support more auth flows b. harder to make mistakes, given the surface becomes fairly small
can be used to glue two worlds together, in case you do not have an egress stream, but do want to start bridging....
it now is once again a nice service stack now that we made Bridging a first-class concept... woohoo including bridging io to bridgeIo... bridge-ception
leakage will need to be fixed properly in future... not priority now though
makes clearer the intent, similar to how we split of Io earlier of from stream
plus rename related type
credits for original impl in https://github.com/sfackler/tokio-io-timeout/blob/master/src/lib.rs
including http relay integration, which uses also the hijack and HTTP Proxy Connect MITM middleware layers... removed the hop-by-hop removal layers as a tproxy, should not do these explicitly, given it is supposed to be invisible, any headers that are forbidden on either say will be removed implicitly by the backend http logic
no longer works with actual required API... and anyway probably a bad idea, instead make it explicit clear how we are binding
probably not needed, and anyway unreliable as this is different than KepA
full flow works!
+ make proxy conn checker a rama-http-type utility
we now once again should have proxy connect that works
next step: actual WS relay...
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bindings and support for https://developer.apple.com/documentation/networkextension in rama.