net: add HSTS and pinning for Dropbox.

net/http/transport_security_state_static.json

 // Copyright (c) 2012 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // This file contains the HSTS preloaded list in a machine readable format.
 
 // The top-level element is a dictionary with two keys: "pinsets" maps details
 // of certificate pinning to a name and "entries" contains the HSTS details for
 // each host.
 //
@@ skipping 133 matching lines @@
       "static_spki_hashes": [
         "DigiCertEVRoot",
         "CryptoCat1"
       ]
     },
     {
       "name": "lavabit",
       "static_spki_hashes": [
         "Libertylavabitcom"
       ]
+    },
+    {
+      "name": "dropbox",
+      "static_spki_hashes": [
+        "DigiCertAssuredIDRoot",
+        "DigiCertGlobalRoot",
+        "DigiCertEVRoot",
+        "EntrustRootEC1",
+        "Entrust_G2",
+        "Entrust_EV",
+        "Entrust_2048",
+        "GeoTrustGlobal",
+        "GeoTrustPrimary_G2",
+        "GeoTrustPrimary_G3",
+        "GeoTrustPrimary",
+        "TheGoDaddyGroupClass2",
+        "GoDaddyRoot_G2",
+        "GoDaddySecure",
+        "ThawtePremiumServer",
+        "ThawtePrimaryRootCA_G2",
+        "ThawtePrimaryRootCA_G3",
+        "ThawtePrimaryRootCA"
+      ]
     }
   ],
 
   "entries": [
     // Dummy entry to test certificate pinning.
     { "name": "pinningtest.appspot.com", "include_subdomains": true, "pins": "test" },
 
     // (*.)google.com, iff using SSL, must use an acceptable certificate.
     { "name": "google.com", "include_subdomains": true, "pins": "google" },
 
@@ skipping 615 matching lines @@
     { "name": "tinfoilsecurity.com", "mode": "force-https" },
     { "name": "www.tinfoilsecurity.com", "mode": "force-https" },
     { "name": "imouto.my", "mode": "force-https" },
     { "name": "vocaloid.my", "include_subdomains": true, "mode": "force-https" },
     { "name": "sakaki.anime.my", "include_subdomains": true, "mode": "force-https" },
     { "name": "reviews.anime.my", "include_subdomains": true, "mode": "force-https" },
     { "name": "miku.hatsune.my", "include_subdomains": true, "mode": "force-https" },
     { "name": "webcollect.org.uk", "include_subdomains": true, "mode": "force-https" },
     { "name": "www.capitainetrain.com", "mode": "force-https" },
     { "name": "accounts.firefox.com", "include_subdomains": true, "mode": "force-https" },
+    { "name": "dropbox.com", "mode": "force-https", "pins": "dropbox" },
+    { "name": "www.dropbox.com", "include_subdomains": true, "mode": "force-https", "pins": "dropbox" },

[Ryan Sleevi, 2014/07/01 03:03:58]

Weird to include sub-domains for www, but I can see no harm.

 
     // Entries that are only valid if the client supports SNI.
     { "name": "gmail.com", "mode": "force-https", "pins": "google", "snionly": true },
     { "name": "googlemail.com", "mode": "force-https", "pins": "google", "snionly": true },
     { "name": "www.gmail.com", "mode": "force-https", "pins": "google", "snionly": true },
     { "name": "www.googlemail.com", "mode": "force-https", "pins": "google", "snionly": true },
     { "name": "google-analytics.com", "include_subdomains": true, "pins": "google", "snionly": true },
     { "name": "googlegroups.com", "include_subdomains": true, "pins": "google", "snionly": true },
     { "name": "mykolab.com", "include_subdomains": true, "mode": "force-https", "snionly": true },
     { "name": "semenkovich.com", "include_subdomains": true, "mode": "force-https", "snionly": true }
   ]
 }