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

question on permissions #221

Open
IzzySoft opened this issue Jan 1, 2025 · 2 comments
Open

question on permissions #221

IzzySoft opened this issue Jan 1, 2025 · 2 comments

Comments

@IzzySoft
Copy link

IzzySoft commented Jan 1, 2025

Our scanners got extended since your last release, so on the current one they reported:

! repo/com.m3u.androidApp_144.apk declares sensitive permission(s):
  android.permission.READ_EXTERNAL_STORAGE
! repo/com.m3u.androidApp_144.apk contains signature block blobs: 0x504b4453 (DEPENDENCY_INFO_BLOCK; GOOGLE)

I guess READ_EXTERNAL_STORAGE is used to access local media files (but what is WRITE_EXTERNAL_STORAGE needed/used for then)? Concerning DEPENDENCY_INFO_BLOCK, thats easily avoided with a little addition to your build.gradle`:

android {
    dependenciesInfo {
        // Disables dependency metadata when building APKs.
        includeInApk = false
        // Disables dependency metadata when building Android App Bundles.
        includeInBundle = false
    }
}

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!

@oxyroid
Copy link
Owner

oxyroid commented Jan 2, 2025

These two permissions are used to save and restore the backup files.

@IzzySoft
Copy link
Author

IzzySoft commented Jan 2, 2025

These two permissions are used to save and restore the backup files.

Thanks! Added that to the "green list" of your app. Just out of curiosity: the app only supports Android 8+ – and backups just need access to a single directory. Any reason you don't use SAF instead?

And btw, will you address that blob?

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