From 64837579a337a819b91314dfea3694acfb3806b2 Mon Sep 17 00:00:00 2001 From: Daniel Micay Date: Wed, 19 Feb 2020 14:55:49 -0500 Subject: [PATCH] add initial legacy devices section --- static/faq.html | 29 +++++++++++++++++++++++++++++ static/index.html | 2 +- static/redirect.js | 4 ++++ static/releases.html | 1 + static/usage.html | 2 +- 5 files changed, 36 insertions(+), 2 deletions(-) diff --git a/static/faq.html b/static/faq.html index f29fa47e..87da1495 100644 --- a/static/faq.html +++ b/static/faq.html @@ -54,6 +54,7 @@
  • Which devices are recommended?
  • Which devices will be supported in the future?
  • When will more devices be supported?
  • +
  • Why are older devices no longer supported?
  • @@ -191,6 +192,34 @@ and security. Broad device support is the opposite of what the project wants to achieve in the long term.

    +

    + Why are older devices no longer supported? +

    + +

    GrapheneOS aims to provide reasonably private and secure devices. It cannot do that + once device support code like firmware, kernel and vendor code is no longer actively + maintained. Even if the community was prepared to take over maintainance of the open + source code and to replace the rest, firmware would present a major issue, and the + community has never been active or interested enough in in device support to consider + attempting this. Unlike many other platforms, GrapheneOS has a much higher minimum + standard than simply having devices fully functional, as they also need to provide the + expected level of security. It would start to become realistic to provide + substantially longer device support once GrapheneOS controls the hardware and firmware + via custom hardware manufactured for it. Until then, the lifetime of devices will + remain based on manufacturer support. It's also important to keep in mind that phone + vendors claiming to provide longer support often aren't actually doing it and some + never even ship firmware updates when the hardware is still supported by the + vendors...

    + +

    GrapheneOS also has high standards for the privacy and security properties of the + hardware and firmware, and these standards are regularly advancing. The rapid pace of + improvement has been slowing down, but each hardware generation still brings major + improvements. Over time, the older hardware starts to become a substantial liability + and holds back the project. It becomes complex to simply make statements about the + security of the project when exceptions for old devices need to be listed out. The + project ends up wanting to drop devices for this reason but has always kept them going + until the end-of-life date to provide more time for people to migrate.

    +

    Security and privacy

    diff --git a/static/index.html b/static/index.html index 5a06be3a..5fc36dcb 100644 --- a/static/index.html +++ b/static/index.html @@ -114,6 +114,6 @@
  • Reddit
  • - + diff --git a/static/redirect.js b/static/redirect.js index e1387e23..d84bfd78 100644 --- a/static/redirect.js +++ b/static/redirect.js @@ -13,6 +13,10 @@ const redirects = new Map([ ["/#device-support", "/faq#device-support"], ["/usage#default-connections", "/faq#default-connections"], + ["/releases#marlin-stable", "/faq#legacy-devices"], + ["/releases#sailfish-stable", "/faq#legacy-devices"], + ["/releases#marlin-beta", "/faq#legacy-devices"], + ["/releases#sailfish-beta", "/faq#legacy-devices"], ]); function handle_hash() { diff --git a/static/releases.html b/static/releases.html index 2f9b6d6a..277f7417 100644 --- a/static/releases.html +++ b/static/releases.html @@ -1010,5 +1010,6 @@ + diff --git a/static/usage.html b/static/usage.html index a3458c16..a07f1678 100644 --- a/static/usage.html +++ b/static/usage.html @@ -335,6 +335,6 @@
  • Reddit
  • - +