From f5434ed563e4cb01c950d83aa4e179e2811a8612 Mon Sep 17 00:00:00 2001
From: Soren Stoutner
Date: Wed, 13 Sep 2017 16:42:29 -0700
Subject: [PATCH] Update SSL Certificate Guide.
---
app/build.gradle | 4 ++--
...ficate_pinning.html => guide_ssl_certificates.html} | 5 +++--
app/src/main/assets/en/about_changelog.html | 10 ++++++++++
...ficate_pinning.html => guide_ssl_certificates.html} | 5 +++--
...ficate_pinning.html => guide_ssl_certificates.html} | 0
...ficate_pinning.html => guide_ssl_certificates.html} | 0
.../privacybrowser/activities/GuideActivity.java | 2 +-
.../privacybrowser/fragments/GuideTabFragment.java | 2 +-
app/src/main/res/values-es/strings.xml | 2 +-
app/src/main/res/values-it/strings.xml | 2 +-
app/src/main/res/values/strings.xml | 2 +-
build.gradle | 3 +++
12 files changed, 26 insertions(+), 11 deletions(-)
rename app/src/main/assets/de/{guide_ssl_certificate_pinning.html => guide_ssl_certificates.html} (90%)
rename app/src/main/assets/en/{guide_ssl_certificate_pinning.html => guide_ssl_certificates.html} (90%)
rename app/src/main/assets/es/{guide_ssl_certificate_pinning.html => guide_ssl_certificates.html} (100%)
rename app/src/main/assets/it/{guide_ssl_certificate_pinning.html => guide_ssl_certificates.html} (100%)
diff --git a/app/build.gradle b/app/build.gradle
index 8764284e..399adf0b 100644
--- a/app/build.gradle
+++ b/app/build.gradle
@@ -55,10 +55,10 @@ android {
dependencies {
compile fileTree(include: ['*.jar'], dir: 'libs')
- compile 'com.android.support:design:25.3.1'
+ compile 'com.android.support:design:25.4.0'
// Only compile `com.google.firebase:firebase-ads:9.8.0` for the free flavor.
- freeCompile 'com.google.firebase:firebase-ads:9.8.0'
+ freeCompile 'com.google.firebase:firebase-ads:11.2.2'
}
// Google's documentation says the following line is required for `firebase-ads` but things work correctly without it. I have no interest in applying the Google Mobile Services plugin in the standard flavor if I don't have to.
diff --git a/app/src/main/assets/de/guide_ssl_certificate_pinning.html b/app/src/main/assets/de/guide_ssl_certificates.html
similarity index 90%
rename from app/src/main/assets/de/guide_ssl_certificate_pinning.html
rename to app/src/main/assets/de/guide_ssl_certificates.html
index 8fb49250..1a228fe3 100644
--- a/app/src/main/assets/de/guide_ssl_certificate_pinning.html
+++ b/app/src/main/assets/de/guide_ssl_certificates.html
@@ -49,7 +49,7 @@
Android has a list of trusted certificate authorities, and will accept any of their certificates for any website.
It isnât supposed to be possible for an organization to acquire an SSL certificate for a domain they do not control, but in practice many governments and large corporations have been able to do so.
- The purpose of SSL certificate pinning is to tell the browser that only one specific SSL certificate is to be trusted for a particular domain. Any other certificate, even if it is valid, will be rejected.
+ Pinning an SSL certificate tells the browser that only one specific SSL certificate is to be trusted for a particular domain. Any other certificate, even if it is valid, will be rejected.
@@ -60,6 +60,7 @@
SSL certificates can be pinned in Domain Settings.
- Besides protecting against MITM attacks, pinning a self-signed certificate for a device like a wireless router or access point will remove the error message that is normally presented every time its website is loaded.
+ Besides protecting against MITM attacks, pinning a self-signed certificate for a device like a wireless router or access point will remove the error message that is normally presented every time its website is loaded.
+ To view the current website SSL certificate, tap on the favorite icon next to the URL bar.