diff --git a/doc-src/_nav.html b/doc-src/_nav.html
index 69175c0ce..91d2118fe 100644
--- a/doc-src/_nav.html
+++ b/doc-src/_nav.html
@@ -31,13 +31,6 @@
$!nav("ssl.html", this, state)!$
$!nav("certinstall/webapp.html", this, state)!$
- $!nav("certinstall/android.html", this, state)!$
- $!nav("certinstall/firefox.html", this, state)!$
- $!nav("certinstall/ios.html", this, state)!$
- $!nav("certinstall/ios-simulator.html", this, state)!$
- $!nav("certinstall/java.html", this, state)!$
- $!nav("certinstall/osx.html", this, state)!$
- $!nav("certinstall/windows7.html", this, state)!$
$!nav("transparent.html", this, state)!$
diff --git a/doc-src/certinstall/android-settingssecurityinstallca.png b/doc-src/certinstall/android-settingssecurityinstallca.png
deleted file mode 100644
index f0f97273e..000000000
Binary files a/doc-src/certinstall/android-settingssecurityinstallca.png and /dev/null differ
diff --git a/doc-src/certinstall/android-settingssecuritymenu.png b/doc-src/certinstall/android-settingssecuritymenu.png
deleted file mode 100644
index fea412fec..000000000
Binary files a/doc-src/certinstall/android-settingssecuritymenu.png and /dev/null differ
diff --git a/doc-src/certinstall/android-settingssecurityuserinstalledca.png b/doc-src/certinstall/android-settingssecurityuserinstalledca.png
deleted file mode 100644
index 1f7717ad4..000000000
Binary files a/doc-src/certinstall/android-settingssecurityuserinstalledca.png and /dev/null differ
diff --git a/doc-src/certinstall/android-shellwgetmitmproxyca.png b/doc-src/certinstall/android-shellwgetmitmproxyca.png
deleted file mode 100644
index 4a4e326f0..000000000
Binary files a/doc-src/certinstall/android-shellwgetmitmproxyca.png and /dev/null differ
diff --git a/doc-src/certinstall/android.html b/doc-src/certinstall/android.html
deleted file mode 100644
index 73fc4d8b5..000000000
--- a/doc-src/certinstall/android.html
+++ /dev/null
@@ -1,53 +0,0 @@
-The proxy situation on Android is [an
-embarrasment](http://code.google.com/p/android/issues/detail?id=1273). It's
-scarcely credible, but Android didn't have a global proxy setting at all until
-quite recently, and it's still not supported on many common Android versions.
-In the meantime the app ecosystem has grown used to life without this basic
-necessity, and many apps merrily ignore it even if it's there. This situation
-is improving, but in many circumstances using [transparent
-mode](@!urlTo("transparent.html")!@) is mandatory for testing Android apps.
-
-We used both an Asus Transformer Prime TF201 (Android 4.0.3) and a Nexus 4
-(Android 4.4.4) in the examples below - your device may differ, but the broad
-process should be similar. On **emulated devices**, there are some [additional
-quirks](https://github.com/mitmproxy/mitmproxy/issues/204#issuecomment-32837093)
-to consider.
-
-
-## Getting the certificate onto the device
-
-The easiest way to get the certificate to the device is to use [the web
-app](@!urlTo("webapp.html")!@). In the rare cases where the web app doesn't
-work, you will need to get the __mitmproxy-ca-cert.cer__ file into the
-__/sdcard__ folder on the device (/sdcard/Download on older devices). This can
-be accomplished in a number of ways:
-
-- If you have the Android Developer Tools installed, you can use [__adb
-push__](http://developer.android.com/tools/help/adb.html).
-- Using a file transfer program like wget (installed on the Android device) to
-copy the file over.
-- Transfer the file using external media like an SD Card.
-
-Once we have the certificate on the local disk, we need to import it into the
-list of trusted CAs. Go to Settings -> Security -> Credential Storage,
-and select "Install from storage":
-
-
-
-The certificate in /sdcard is automatically located and offered for
-installation. Installing the cert will delete the download file from the local
-disk.
-
-
-## Installing the certificate
-
-You should now see something like this (you may have to explicitly name the
-certificate):
-
-
-
-Click OK, and you should then see the certificate listed in the Trusted
-Credentials store:
-
-
-
diff --git a/doc-src/certinstall/firefox.html b/doc-src/certinstall/firefox.html
deleted file mode 100644
index bb9ba05bb..000000000
--- a/doc-src/certinstall/firefox.html
+++ /dev/null
@@ -1,31 +0,0 @@
-## Get the certificate to the browser
-
-The easiest way to get the certificate to the browser is to use [the web
-app](@!urlTo("webapp.html")!@). If this fails, do the following:
-
-
-
- - If needed, copy the ~/.mitmproxy/mitmproxy-ca-cert.pem file to the target.
-
- - Open preferences, click on "Advanced", then select"Certificates":
-
-
-
- - Click "View Certificates", "Import", and select the certificate file:
-
-
-
-
-
-
-## Installing the certificate
-
-
- - Tick "Trust this CA to identify web sites", and click "Ok":
-
-
-
- - You should now see the mitmproxy certificate listed in the Authorities
- tab.
-
-
diff --git a/doc-src/certinstall/index.py b/doc-src/certinstall/index.py
index d6b1e4178..fd422cb3e 100644
--- a/doc-src/certinstall/index.py
+++ b/doc-src/certinstall/index.py
@@ -2,12 +2,5 @@ from countershape import Page
pages = [
Page("webapp.html", "Using the Web App"),
- Page("firefox.html", "Firefox"),
- Page("osx.html", "OSX"),
- Page("windows7.html", "Windows 7"),
- Page("ios.html", "IOS"),
- Page("ios-simulator.html", "IOS Simulator"),
- Page("android.html", "Android"),
- Page("java.html", "Java"),
Page("mitm.it-error.html", "Error: No proxy configured"),
]
diff --git a/doc-src/certinstall/ios-simulator.html b/doc-src/certinstall/ios-simulator.html
deleted file mode 100644
index 9eb981086..000000000
--- a/doc-src/certinstall/ios-simulator.html
+++ /dev/null
@@ -1,23 +0,0 @@
-
-How to install the __mitmproxy__ certificate authority in the IOS simulator:
-
-
-
- - First, check out the ADVTrustStore tool
- from github.
-
- - Now, run the following command:
-
-
./iosCertTrustManager.py -a ~/.mitmproxy/mitmproxy-ca-cert.pem
-
-
-
-
-
-
-Note that although the IOS simulator has its own certificate store, it shares
-the proxy settings of the host operating system. You will therefore to have
-configure your OSX host's proxy settings to use the mitmproxy instance you want
-to test with.
-
diff --git a/doc-src/certinstall/ios.html b/doc-src/certinstall/ios.html
deleted file mode 100644
index c12d65f69..000000000
--- a/doc-src/certinstall/ios.html
+++ /dev/null
@@ -1,27 +0,0 @@
-
-## Getting the certificate onto the device
-
-The easiest way to get the certificate to the device is to use [the web
-app](@!urlTo("webapp.html")!@). In the rare cases where the web app doesn't
-work, you will need to get the __mitmproxy-ca-cert.pem__ file to the device to
-install it. The easiest way to accomplish this is to set up the Mail app on the
-device, and to email it over as an attachment. Open the email, tap on the
-attachment, then proceed with the install.
-
-
-## Installing the certificate
-
-
- - You will be prompted to install a profile. Click "Install":
-
-
-
- - Accept the warning by clicking "Install" again:
-
-
-
- - The certificate should now be trusted:
-
-
-
-
diff --git a/doc-src/certinstall/java.html b/doc-src/certinstall/java.html
deleted file mode 100644
index f64209910..000000000
--- a/doc-src/certinstall/java.html
+++ /dev/null
@@ -1,13 +0,0 @@
-
-You can add the mitmproxy certificates to the Java trust store using
-[keytool](http://docs.oracle.com/javase/6/docs/technotes/tools/solaris/keytool.html).
-On OSX, the required command looks like this:
-
-
-sudo keytool -importcert -alias mitmproxy -storepass "password" \
--keystore /System/Library/Java/Support/CoreDeploy.bundle/Contents/Home/lib/security/cacerts \
--trustcacerts -file ~/.mitmproxy/mitmproxy-ca-cert.pem
-
-
-Note that your store password will (hopefully) be different from the one above.
-
diff --git a/doc-src/certinstall/osx.html b/doc-src/certinstall/osx.html
deleted file mode 100644
index a532d5380..000000000
--- a/doc-src/certinstall/osx.html
+++ /dev/null
@@ -1,16 +0,0 @@
-
-How to install the __mitmproxy__ certificate authority in OSX:
-
-
-
- - Open Finder, and double-click on the mitmproxy-ca-cert.pem file.
-
- - You will be prompted to add the certificate. Click "Always Trust":
-
-
-
-
- - You may be prompted for your password. You should now see the
- mitmproxy cert listed under "Certificates".
-
-
diff --git a/doc-src/certinstall/windows7.html b/doc-src/certinstall/windows7.html
deleted file mode 100644
index 7a4cc3d26..000000000
--- a/doc-src/certinstall/windows7.html
+++ /dev/null
@@ -1,35 +0,0 @@
-
-How to install the __mitmproxy__ certificate authority in Windows 7:
-
-
-
- - The easiest way to get the certificate to the device is to use the web app. If this fails for some
- reason, simply copy the ~/.mitmproxy/mitmproxy-ca-cert.p12 file to the
- target system and double-click it.
-
- -
- You should see a certificate import wizard:
-
-
-
-
- -
- Click "Next" until you're prompted for the certificate store:
-
-
-
-
-
-
- -
-
Select "Place all certificates in the following store", and select "Trusted Root Certification Authorities":
-
-
-
-
-
- - Click "Next" and "Finish".
-
-
-
diff --git a/doc-src/ssl.html b/doc-src/ssl.html
index de45bd29f..cccde1b78 100644
--- a/doc-src/ssl.html
+++ b/doc-src/ssl.html
@@ -87,13 +87,5 @@ You can use your own certificate authority by passing the --confdir o
mitmproxy will then look for mitmproxy-ca.pem in the specified directory. If no such file exists,
it will be generated automatically.
-Installing the mitmproxy CA
----------------------------
-* [Firefox](@!urlTo("certinstall/firefox.html")!@)
-* [OSX](@!urlTo("certinstall/osx.html")!@)
-* [Windows 7](@!urlTo("certinstall/windows7.html")!@)
-* [iPhone/iPad](@!urlTo("certinstall/ios.html")!@)
-* [IOS Simulator](@!urlTo("certinstall/ios-simulator.html")!@)
-* [Android](@!urlTo("certinstall/android.html")!@)
diff --git a/doc-src/tutorials/gamecenter.html b/doc-src/tutorials/gamecenter.html
index 5998f889f..b51b6faf9 100644
--- a/doc-src/tutorials/gamecenter.html
+++ b/doc-src/tutorials/gamecenter.html
@@ -2,9 +2,8 @@
## The setup
In this tutorial, I'm going to show you how simple it is to creatively
-interfere with Apple Game Center traffic using mitmproxy. To set things up, I
-registered my mitmproxy CA certificate with my iPhone - there's a [step by step
-set of instructions](@!urlTo("certinstall/ios.html")!@) elsewhere in this manual. I then
+interfere with Apple Game Center traffic using mitmproxy. To set things up,
+you must install the [mitmproxy root certificate](@!urlTo("certinstall/webapp.html")!@) elsewhere in this manual. I then
started mitmproxy on my desktop, and configured the iPhone to use it as a
proxy.