-
-
Notifications
You must be signed in to change notification settings - Fork 167
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
Question on permissions #257
Comments
Btw, looks like the package name has changed:
Shall I move to the new one? that would mean everyone had to uninstall/reinstall of course. Updater here is pinned to |
|
Yeah we need to migrate to |
I've added it, can you have a test? |
Local WebDAV I assume? Because in the "open net" it should always be SSL. Package and storage permissions are clear then (the former I already had added to the green list). Done so for the storage perms as well then.
OK, will do so now so the new package should show up with the next sync around 6 pm UTC. Thanks for disabling the blob – I've sent the file through the scanner and it didn't complain. |
Not only local, we also support remote server |
I meant |
Nope, there's no any check for that, maybe I can add a warning about it. |
That would be good I'd say. Meanwhile, I'll add the flag to the "green list": usesCleartextTraffic: intended for connections within the local network should match I guess? |
Yes! |
I just received a report from the IoD scanners:
Could you please clarify?
android.permission.QUERY_ALL_PACKAGES
is clear for a backup app of course – but what cleartext connections are needed? I guess the storage should be clear as well (needed to access the data to be backed up/restored), but a confirmation is welcome.As for
DEPENDENCY_INFO_BLOCK
, that can easily be avoided with a tiny adjustment in yourbuild.gradle
:For some background: that BLOB is supposed to be just a binary representation of your app's dependency tree. But as it's encrypted with a public key belonging to Google, only Google can read it – and nobody else can even verify what it really contains. More details can be found e.g. here: Ramping up security: additional APK checks are in place with the IzzyOnDroid repo.
Thanks in advance!
The text was updated successfully, but these errors were encountered: