-
Notifications
You must be signed in to change notification settings - Fork 11
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
Certificate issue #12
Comments
@Dado1513 any word? |
@IzzySoft yes in a couple of days I will proceed with the new release. |
Wonderful, thanks! 🤩 |
Hi @IzzySoft, I just released a new version with a valid signature: HideDroid 1.3 |
Thanks! Triggering a pull now…
One more thing: New release will go live here with the next sync. I've also added a "release note" concerning the changed certificate, telling people they'd have to uninstall and reinstall: |
@Dado1513 Could you please clarify the permissions listed in my comment from March? And will the debuggable flag be dropped any time soon – or has the app been abandoned, as there are not even any commits since March? I mean, for an app about privacy and security, those things should be clarified/fixed. What packages does HideDroid want to install? Some folks might be scared away by this. |
Hi @IzzySoft, Apologies for the delayed response. I haven’t had much time to dedicate to personal projects lately. The The |
Thanks Davide! I wasn't aware HideDroid would repackage apps, the description doesn't tell that nor does the Readme mention it – I thought filtering/rewriting of traffic was done via "proxying" (hence the How then will app updates handled? And the app's data? You cannot repack APKs without re-signing them, so the repacked APK would not be accepted as update (hence probably the And last but not least:Shouldn't this be made clear in the description, to avoid "surprises after install"? |
A scan (see here for details and background) just revealed the APKs at your releases are signed using a debug key. As that has security implications, may I ask you to please switch to a proper release key, and provide the corresponding APK signed with it? Thanks in advance!
The text was updated successfully, but these errors were encountered: