badhalo.blogg.se - Google chrome os developer mode

The following vulnerabilities have been considered in this design. It's focused on developers who want to install a different operating system on a device that initially shipped with Google Chrome OS. Note that this document is specifically about the developer mode in Google Chrome OS devices, not about other Chromium OS-based devices.

How the implementation protects from vulnerabilities while allowing required use cases.

A proposed implementation of developer mode that provides both openness for developers and security for users.

Use cases we must allow for normal users and developers.

Vulnerabilities to which Google Chrome OS devices may be exposed.

Openings for developers to run modified software easily can also be exploited by attackers. Locking down a device to protect users makes it less useful for developers. These two requirements are somewhat at odds. Developers should not be significantly impaired from using the full capabilities of the device.

Open - developers must be able to install their own builds of a Chromium-based OS, or another operating system (e.g., Ubuntu).

This protection should reasonably extend to inexperienced or naive users.

Secure - users must be protected from attackers.

5.7 User installs prebuilt OS distribution (other than Google Chrome OS).

5.2 Attacker with casual physical access.

5.1 Attacker with complete physical access.

5 How this design addresses vulnerabilities and use cases.4.7 Manufacturer hardware modifications.4.4 Boot errors always trigger recovery mode.4.3 Recovery button always triggers recovery mode.3.3 User installs prebuilt OS distribution (other than Google Chrome OS).2.2 Attacker with casual physical access.2.1 Attacker with complete physical access.