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

Fix setting file permissions in post-fs-data.sh #2

Closed
wants to merge 1 commit into from
Closed

Conversation

Redjard
Copy link

@Redjard Redjard commented Feb 13, 2022

My certificate got added with permissions 660, because the original file had those permissions. I assume set_perm_recursive didn't work at all and the owner got changed to root because of the cp. Either way, if the cert files in cacerts-custom end up with the default android file permissions 660, the certs don't work because nothing can read them.
I tried the second line, which is copied straight from the Fdroid-Priv extension, because those perms got set correctly on my device, but that didn't work here either.

I assume set_perm_recursive isn't available in post-fs-data scripts, only in install.sh.
chmod and chown work fine for me (Android 11 Magisk 24.1)

My certificate got added with permissions 660, because the original file had those permissions. I assume set_perm_recursive didn't work at all and the owner got changed to root because of the cp. Either way, if the cert files in cacerts-custom end up with the default android file permissions 660, the certs don't work because nothing can read them.
I tried the second line, which is copied straight from  the Fdroid-Priv extension, because those perms got set correctly on my device, but that didn't work here either.

I assume set_perm_recursive isn't available in post-fs-data scripts, only in install.sh.
chmod and chown work fine for me (Android 11 Magisk 24.1)
@ghost
Copy link

ghost commented Feb 13, 2022

@Redjard Thanks for the bug report and the pull request! I ended up building on your idea to fix the issue in 3e8af07.

@ghost ghost closed this Feb 13, 2022
This pull request was closed.
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

Successfully merging this pull request may close these issues.

None yet

1 participant