"Android 17 blocks cross-profile loopback traffic for all apps, breaking cross-profile localhost proxy" thing, what if there may be a way ? :-) (feature suggestion / research suggestion)

Hi! So, basically, there has been some discussion of this in Graphene github https://github.com/GrapheneOS/os-issue-tracker/issues/4772#issuecomment-4743173488 And it appears that in order to do a "cross profile loopback comms" thing a non-root / non-system app on a non-modified system would need to pull off the following: have USE_LOOPBACK_INTERFACE permission have a INTERACT_ACROSS_PROFILES OR INTERACT_ACROSS_USERS permission This app has apparently been able to fix its localhost woes this way https://github.com/VentralDigital/InterProfileSharing This opens two possible avenues for restoring the cross-profile/user proxy feat 1) a small "helper app" that is present in both users, has relevant permissions, will listen on localhosts in both profiles and ferry the traffic in-between (which would mean a small amount of additional complexity and some minor battery drain and performance loss due to all the proxying and whatnot) 2) Assuming (ASSUMING, I didn't check) android doesn't actually check who or what talks to localhost as long as relevant ticks are checked, Exclave itself could have those permissions, be present in both users/profiles, but actually run in only one of the profiles THEN if the app that wants to use the proxy also does the "cross profile localhost dance" to grant itself "cross profile localhost" rights it could talk to Exclave (this would not need a whole helper app but would require explicit support both from Exclave and the app that wants to use Exclave, and of course this assumes android doesn't have some clever eBPF thing or whatever tracking whether the app doing "cross profile localhosting" is talking to its "same named brother" in the other profile or some other unrelated app)