Replicant

h1. GalaxyS3I9300PrivacySecurityEvaluation

Note that this information may or may not be exhaustive.

It also may or may not contain all known issues or good point about this device.

h2. General freedom issues on the Galaxy S 3 (I9300):

* The bootloader is proprietary and signed. It's only possible to replace part of it.

* The bootloader also loads a proprietary OS on the main CPU, in "TrustZone":https://en.wikipedia.org/wiki/Trusted_execution_environment. See "this analysis":https://sensepost.com/blog/2013/a-software-level-analysis-of-trustzone-os-and-trustlets-in-samsung-galaxy-phone/ for more details on the precise implementation for the Galaxy SIII.

* Some peripherals do require proprietary firmwares to work.

** See [[GalaxyS3I9300LoadedFirmwares|some of which have to be loaded by the system]]. 

** See also the "Missing without non-free firmwares" status in [[ReplicantStatus]].

* The bootrom is the first code that is executed, it's stored in a read-only memory: see "freedom-privacy-security-issues":https://www.replicant.us/freedom-privacy-security-issues.php for more details.

* The hardware is proprietary, and we are not aware if any complete schematics is available somewhere on the Internet.

h2. Modem related:

The modem runs non-free software, which is loaded but not shipped by Replicant.

* When using flight mode, The main CPU has to ask the modem to power itself off.

* The modem is isolated:

** It doesn't use shared memory to communicate with the main CPU, instead it uses HSIC, which is a version of USB 2.0 meant to interface chips together directly. Here the modem also cannot change USB IDs without having the main CPU reset the HSIC bus.

** We are not aware of it being able to access the GPS, but it wouldn't be surprising if it still could (by having a direct connection to it: since no schematics are publicly available we have easy no way to check).

** It has no access to the other CPU peripherals.

* "Terminal profile":https://terminal-profile.osmocom.org/decode.php?tp=ffffffff7f1f00dfff00001fa2010a860749000000000000000000000010

h2. TODO:

* Investigate its terminal profile

* Investigate device factory reset security in both Replicant and its recovery (Does it really wipe files?)

* Investigate the flash layout, EMMC partitions, EMMC firmware

* The Exynos 4412 reference manual says that the PMIC firmware can be reflashed (see the IROM_DATA_REG0 register in the subsection 8.8.1.45 of the Chapter 8 (Power Management Unit)).