-
Notifications
You must be signed in to change notification settings - Fork 272
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
Put android-vts on F-droid #38
Comments
👍 (don't have Google Play Services on my device) |
👍 or, in a first time, a link to download the APK will be nice. |
I removed the binary from the repo, but I can add it back for this purpose until an F-Droid release happens. |
Binary located here: https://github.com/nowsecure/android-vts/blob/master/bin/androidVTS.apk |
Thanks a lot ! |
Nice suggestion. Moved release to here: https://github.com/nowsecure/android-vts/releases/tag/v.3 |
Someone propose it in F-droid : https://f-droid.org/forums/topic/android-vts-vulnerability-test-suite-2/ |
+1 on this |
Awesome, I just wanted to propose this since it solves #101. Thanks for aleady doing so, @mimi89999! |
💯 |
idk if this issue is still up-to-date but after asking f-droid maintainers problem is built-in binaries (like the zip) |
@dweinstein @Fuzion24 |
I no longer have the resources to maintain this project. The source for the binaries inside assets is in the repo. However, just recompiling and redistributing this application on F-Droid is not sufficient. It takes a non-negligible amount of time and effort to choose critical CVEs and develop effective tests for them which can happen inside the restricted app sandbox. It's a fair assumption that any device which isn't running the latest Android version and has the latest security patch level is insecure. |
Hi, I just setup an alternative fdroid repo. Still need some changes. Feels free to comment/report issues repo here. For AndroidVTS devs: If it is a problem that I build and release your app contact me and I will remove everything. |
No description provided.
The text was updated successfully, but these errors were encountered: