summaryrefslogtreecommitdiff
path: root/data/extensions/https-everywhere-eff@eff.org/chrome/locale/es_AR/ssl-observatory.dtd
diff options
context:
space:
mode:
authorRuben Rodriguez <ruben@gnu.org>2016-11-21 14:41:08 -0500
committerRuben Rodriguez <ruben@gnu.org>2016-11-21 14:41:08 -0500
commit1aecd18e5cc9d8b9dfd4063e749ce61eb0077e2a (patch)
tree67c72d47420617f9420c36eedd3489803dae35bc /data/extensions/https-everywhere-eff@eff.org/chrome/locale/es_AR/ssl-observatory.dtd
parentd05c3f23b8e31db1d3f112557bd4f66f364d32b9 (diff)
https-everywhere updated to 5.2.7
Diffstat (limited to 'data/extensions/https-everywhere-eff@eff.org/chrome/locale/es_AR/ssl-observatory.dtd')
-rw-r--r--data/extensions/https-everywhere-eff@eff.org/chrome/locale/es_AR/ssl-observatory.dtd4
1 files changed, 2 insertions, 2 deletions
diff --git a/data/extensions/https-everywhere-eff@eff.org/chrome/locale/es_AR/ssl-observatory.dtd b/data/extensions/https-everywhere-eff@eff.org/chrome/locale/es_AR/ssl-observatory.dtd
index 46b004b..305afcc 100644
--- a/data/extensions/https-everywhere-eff@eff.org/chrome/locale/es_AR/ssl-observatory.dtd
+++ b/data/extensions/https-everywhere-eff@eff.org/chrome/locale/es_AR/ssl-observatory.dtd
@@ -13,7 +13,7 @@ and auditing the certificates being presented to your browser. Would you like
to turn it on?">-->
<!ENTITY ssl-observatory.popup.title
-"Should HTTPS Everywhere use the SSL Observatory?">
+"¿Deberia HTTPS Everywhere usar el Observatorio SSL?">
<!ENTITY ssl-observatory.popup.yes "Si">
@@ -27,7 +27,7 @@ se encuentre en una red corporativa muy invasiva:">
"Seguro, a menos que utilice una red corporativa con nombres secretos de servidor de intranet:">
<!ENTITY ssl-observatory.prefs.alt_roots
-"Submit and check certificates signed by non-standard root CAs">
+"Aplicar y verificar los certificados firmados por CAs no estandar">
<!ENTITY ssl-observatory.prefs.alt_roots_tooltip
"It is safe (and a good idea) to enable this option, unless you use an intrusive corporate network or Kaspersky antivirus software that monitors your browsing with a TLS proxy and a private root Certificate Authority. If enabled on such a network, this option might publish evidence of which https:// domains were being visited through that proxy, because of the unique certificates it would produce. So we leave it off by default.">