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

Android: Put the application on the app store #92

Open
noseshimself opened this issue Jun 3, 2023 · 3 comments
Open

Android: Put the application on the app store #92

noseshimself opened this issue Jun 3, 2023 · 3 comments

Comments

@noseshimself
Copy link

... for those who can't or do not want to side-load stuff.

@pymq
Copy link
Member

pymq commented Jun 4, 2023

Hi @noseshimself, thanks for asking

Do you have any specific app store in mind?

There are already two issues about google play store and F-Droid: #39 #31

@noseshimself
Copy link
Author

The Google Play Store.

I did not give sufficient detail, sorry. Background:

I'm using ChromeOS. Due to the security model (I guess they took a lot of hints from Qubes, lately even more -- ANYTHING they do not have under control is forbidden in the ChromeOS host itself and if you damage their security model (e. g. by adding random Android packages which you may do) going back to full "secure end user mode" requires you to completely wipe the device. Actually a good idea if every piece of Android software (or Linux software) you can install inside virtual machines was able and willing to export their configuration. Linux containers can be backed up. Android... not.

One major detail of this security model is "you either load Android apps from the Play Store or you enter developer mode and permit side-loading via ADB but if you enable that the Play Store will not consider this a validated device". Of course; the Android (formerly a container within ChromeOS itself) has certain rights that permit it to bypass some ChromeOS security.

As long as your android Application is correctly declaring all required abilities in its manifest ChromeOS will accept it as valid VPN solution (just like everything else from OpenVPN to Wireshark). Which reminds me to ask for a feature: Exportable configuration file(s), just in case. I fyou encrypt them well you can even put them permanently on Google Drive (or, my favorite, NextCloud).

@pymq
Copy link
Member

pymq commented Jun 11, 2023

Thanks for this detailed background! I didn't know that ChromeOS is such a restricted system.

to ask for a feature: Exportable configuration file(s), just in case

Yes, I too thought about how it could be hard to move to a new device, so I have already added this feature, it's available from GUI

About publishing in stores, I'm willing to do this, but not until awl reaches critical user base mass. I don't have google's developer account, it costs money (not much, but still), also publishing in google play is not that easy, too. For me it's not worth it, yet, unfortunately

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants