Greetings all, I'm really new to GrapheneOS. But after considerable study, experimentation and general poking around, it seems to me that obtaining any existing .7z archiving app, or side loading an APK for the same from any available app store that doesn't compromise my anonymity (only F-Droid and Aurora Store as far as I know)--or worse, directly hand over my identity and data to Google again by means of immediately re-chaining me to the same Play Store which I have recently worked so hard to escape--is just about impossible. At this point I'm under the impression that the only practical workarounds for the situation might be to either modify an existing APK that presently contains said unwanted tracking baggage, or compile a new one from source. I have very little relevant experience or understanding applicable to either route, but I'm beginning to think perhaps I should try to educate myself and give it a whirl. Is it all really this bleak, or am I just unaware and overlooking something simple or obvious that someone might be able and willing to enlighten me about? Tom BTW, I have two profiles in my phone setup. The privileged 'Owner' administrative profile is Google free. The second 'user' profile has the Google Play Store and all the dependencies and other Android crap that I either don't know how to or am unwilling or unable to do away with yet. I suppose I could reverse all this if it would help, but I expect it would just be letting Google back in through the back door if I allowed both profiles access to Play Store dependent apps. The way things are now, I'm apparently able to spend much less time in a Google contaminated environment. That in itself is a desirable achievement. At least this is my current understanding.
Hi Tom, Tom Ashcraft writes:
I'm really new to GrapheneOS. But after considerable study, experimentation and general poking around, it seems to me that obtaining any existing .7z archiving app, or side loading an APK for the same from any available app store that doesn't compromise my anonymity (only F-Droid and Aurora Store as far as I know)--or worse, directly hand over my identity and data to Google again by means of immediately re-chaining me to the same Play Store which I have recently worked so hard to escape--is just about impossible.
Sometimes it takes some searching to find an app with the features you want because it doesn't advertise those features well. Forum posts seem to indicate that file managers often support compression formats without necessarily saying so. Unfortunately I'm currently phoneless so I can't test out any potential 7zip extracting apps for you. But perhaps try one of these: https://f-droid.org/en/packages/org.brandroid.openmanager/ https://f-droid.org/en/packages/me.zhanghai.android.files/ https://github.com/mahmoudgalal/ZeeArchiver-Android If you don't mind doing command-line stuff on your phone, Termux should be able to install p7zip from its package repos: https://f-droid.org/en/packages/com.termux/
At this point I'm under the impression that the only practical workarounds for the situation might be to either modify an existing APK that presently contains said unwanted tracking baggage, or compile a new one from source.
If all else fails, Android and GrapheneOS have strong app sandboxing features. You should be able to install a proprietary app, and before opening it for the first time, go into the operating system's app settings and remove all permissions it doesn't need (particularly network, location, and microphone), leaving perhaps only storage permissions. -- Anthony J. Bentley
Does the default LZMA compression format of a 7z archive *imply* AES256 encryption? That is, is AES256 just an ordinary integral aspect of the LZMA compression algorithm, or must one obtain and specify the type of encryption from elsewhere when using the 7z or 7za command at the command line interface? This stuff is all Greek to me as I've previously only created and manipulated archives via linux distro GUIs, and not really worried too much about "what's under the hood".
participants (2)
-
Anthony J. Bentley -
Tom Ashcraft