1 # SOME DESCRIPTIVE TITLE
2 # Copyright (C) YEAR Free Software Foundation, Inc.
3 # This file is distributed under the same license as the PACKAGE package.
4 # FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
8 "Project-Id-Version: PACKAGE VERSION\n"
9 "Report-Msgid-Bugs-To: tails-l10n@boum.org\n"
10 "POT-Creation-Date: 2020-04-12 16:10+0200\n"
11 "PO-Revision-Date: 2020-08-14 11:06+0000\n"
12 "Last-Translator: emmapeel <emma.peel@riseup.net>\n"
13 "Language-Team: Portuguese <http://translate.tails.boum.org/projects/tails/"
14 "new_ssl_certificate/pt/>\n"
17 "Content-Type: text/plain; charset=UTF-8\n"
18 "Content-Transfer-Encoding: 8bit\n"
19 "Plural-Forms: nplurals=2; plural=n != 1;\n"
20 "X-Generator: Weblate 3.5.1\n"
24 msgid "[[!meta date=\"Fri, 06 Jan 2012 22:01:54 +0100\"]]\n"
25 msgstr "[[!meta date=\"Fri, 06 Jan 2012 22:01:54 +0100\"]]\n"
29 msgid "[[!pagetemplate template=\"news.tmpl\"]]\n"
30 msgstr "[[!pagetemplate template=\"news.tmpl\"]]\n"
34 msgid "[[!meta title=\"New SSL certificate for tails.boum.org\"]]\n"
39 msgid "[[!tag announce]]\n"
40 msgstr "[[!tag announce]]\n"
44 msgid "[[!toc levels=2]]\n"
45 msgstr "[[!toc levels=2]]\n"
49 "On the same day Tails 0.10 was put out, our website started to use a "
50 "commercial SSL certificate. This new certificate replaces the previous one "
51 "that was delivered by the non-commercial [CACert certificate authority]"
52 "(http://www.cacert.org/)."
57 msgid "What are SSL certificates?"
62 "Using HTTPS instead of plain HTTP to connect to a website allows you to "
63 "encrypt your communication with the server. But encryption alone does not "
64 "guarantee that you are talking with the right server, and not someone "
65 "impersonating it, for example in case of a [[man-in-the-middle attack|doc/"
66 "about/warning#man-in-the-middle]]."
71 "SSL certificates try to solve this problem. A SSL certificate is usually "
72 "issued by a certificate authority to certify the identity of a server. When "
73 "you reach a website your web browser might trust an SSL certificate "
74 "automatically if it trusts the authority that issued it."
79 "Commercial certificate authorities are making a living out of selling SSL "
80 "certificates; they are usually trusted automatically by most of the "
81 "browsers. Other non-commercial authorities, such as [CACert](http://www."
82 "cacert.org/), need to be installed by the operating system or by the user to "
83 "avoid displaying a security warning when visiting the website."
88 msgid "Weaknesses of the system"
93 "But this trust system has proven to be flawed in many ways. For example, "
94 "during 2011, two certificate authorities were compromised, and many fake "
95 "certificates were issued and used in the wild. See [Comodo: The Recent RA "
96 "Compromise](http://blogs.comodo.com/it-security/data-security/the-recent-ra-"
97 "compromise/) and [The Tor Project: The DigiNotar Debacle, and what you "
98 "should do about it](https://blog.torproject.org/blog/diginotar-debacle-and-"
99 "what-you-should-do-about-it)."
104 "It is clear for us that getting an commercial SSL certificate is not enough "
105 "to strongly authenticate our website, and for example authenticity of our "
106 "releases. That's why we always propose you [[stronger ways of "
107 "authenticating our Tails release|install/download#openpgp]] using OpenPGP "
113 msgid "Why get a commercial certificate then?"
118 "Still we decided to get a commercial certificate for the following reasons:"
121 #. type: Bullet: '- '
123 "It makes it harder to setup a simplistic [[man-in-the-middle attacks|doc/"
124 "about/warning#man-in-the-middle]] against the people who didn't use HTTPS so "
125 "far to visit our website."
128 #. type: Bullet: '- '
130 "Our website now is only available with HTTPS enabled. This may be important "
131 "to provide some confidentiality while posting on the forum for example."