Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Add android:usesCleartextTraffic="true" to manifest to allow insecure HTTP traffic #153

Closed
3 tasks done
user622628252416 opened this issue Oct 30, 2023 · 2 comments
Closed
3 tasks done
Labels
Feature request Requesting a new feature that's not implemented yet

Comments

@user622628252416
Copy link

Feature description

On newer api levels, android disallows insecure http traffic by default. This can be changed by setting android:usesCleartextTraffic="true" in the application tag of the manifest. This patch should be universal.

Motivation

I am using FolderSync to, well, sync folders. However it only allows HTTPS. Since I am running the server I want to sync my device with on my local network and connect to it using a local ip address, I can't and needn't use HTTPS.

As far as I can tell, this patch would be pretty much the same as the one making every activity exported, with just a few lines changed. Therefore it should only require minimal effort.

Acknowledgements

  • This request is not a duplicate of an existing issue.
  • I have chosen an appropriate title.
  • All requested information has been provided properly.
@user622628252416 user622628252416 added the Feature request Requesting a new feature that's not implemented yet label Oct 30, 2023
@SodaWithoutSparkles
Copy link
Contributor

Well even IF you patched the xml, the code might not expect a HTTP server and just connect on port 443.

One of the solution is to self-sign a cert, but on android that requires you to create a CA and import it, then it would be very complicated (dont quote me on that)

One of the solution/workaround is to just get a HTTPS cert. Get a subdomain from duckdns, install caddy to reverse-proxy the traffic, then it will get the HTTPS cert for you.

Then just get a local DNS pointing to the server (via a pi-hole or similar).

@oSumAtrIX oSumAtrIX transferred this issue from ReVanced/revanced-patches-template Dec 14, 2023
@revanced-bot revanced-bot transferred this issue from another repository Dec 14, 2023
@oSumAtrIX
Copy link
Member

I think thats now available as a patch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature request Requesting a new feature that's not implemented yet
Projects
None yet
Development

No branches or pull requests

3 participants