Hi,
just read several topics concerning security and privacy that lead me to a couple of questions:
-
does the latest /e/-version already include some kind of firewall?
-
does the latest /e/-version already include some security mechanisms like SELinux, AppArmor or Systrace (app-restriction)? If yes: are they already configured to optimize security and privacy “out-of-the-box”? Or does the user need to adjust anything (besides the usual set-up-GUI)?
-
is the file system completely encrypted? (so that an intruder can only steal encrypted files)
-
would the following process to locally read/edit files in a private way work on an /e/phone:
t.ex. the user has a confidential PDF, DOC or XLS on a USB-Stick and wants to open it in a safe way:
- shut down all kinds of webData/Wifi/Bluetooth/LTE-connections using /e/-setup
- plug-in the USB-stick (mount)
- open the file, view/edit it, later close it
- remove the USB-stick (unmount)
- enable again the usual webData/Wifi/Bluetooth/LTE-connections using /e/-setup
If I did this on a “usual” Phone or PC with mainstream-OS, I would assume that the OS (or the document-view/edit-app) secretly made a hidden copy of that file, e.g. in a temp-directory, and might send at least its metadata home at the next opportunity).
However, I’m not so much concerned about the usual logging-system that somewhere stores the mere fact that the user viewed or edited a file with a certain name/type/time/date. The point is, if there still exists a copy of the file’s content on the /e/phone after removing the USB-stick.
- is pen-testing already part of the development/release-process?
Many thanks for any response in advance!
Best regards & happy 2022
mc21
Regain your privacy! Adopt /e/ the unGoogled mobile OS and online services