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:05+0000\n"
12 "Last-Translator: emmapeel <emma.peel@riseup.net>\n"
13 "Language-Team: LANGUAGE <LL@li.org>\n"
16 "Content-Type: text/plain; charset=UTF-8\n"
17 "Content-Transfer-Encoding: 8bit\n"
18 "Plural-Forms: nplurals=2; plural=n != 1;\n"
19 "X-Generator: Weblate 3.5.1\n"
23 msgid "[[!meta date=\"Fri, 06 Jan 2012 22:01:54 +0100\"]]\n"
24 msgstr "[[!meta date=\"Fri, 06 Jan 2012 22:01:54 +0100\"]]\n"
28 msgid "[[!pagetemplate template=\"news.tmpl\"]]\n"
29 msgstr "[[!pagetemplate template=\"news.tmpl\"]]\n"
33 msgid "[[!meta title=\"New SSL certificate for tails.boum.org\"]]\n"
38 msgid "[[!tag announce]]\n"
39 msgstr "[[!tag announce]]\n"
43 msgid "[[!toc levels=2]]\n"
44 msgstr "[[!toc levels=2]]\n"
48 "On the same day Tails 0.10 was put out, our website started to use a "
49 "commercial SSL certificate. This new certificate replaces the previous one "
50 "that was delivered by the non-commercial [CACert certificate authority]"
51 "(http://www.cacert.org/)."
56 msgid "What are SSL certificates?"
61 "Using HTTPS instead of plain HTTP to connect to a website allows you to "
62 "encrypt your communication with the server. But encryption alone does not "
63 "guarantee that you are talking with the right server, and not someone "
64 "impersonating it, for example in case of a [[man-in-the-middle attack|doc/"
65 "about/warning#man-in-the-middle]]."
70 "SSL certificates try to solve this problem. A SSL certificate is usually "
71 "issued by a certificate authority to certify the identity of a server. When "
72 "you reach a website your web browser might trust an SSL certificate "
73 "automatically if it trusts the authority that issued it."
78 "Commercial certificate authorities are making a living out of selling SSL "
79 "certificates; they are usually trusted automatically by most of the "
80 "browsers. Other non-commercial authorities, such as [CACert](http://www."
81 "cacert.org/), need to be installed by the operating system or by the user to "
82 "avoid displaying a security warning when visiting the website."
87 msgid "Weaknesses of the system"
92 "But this trust system has proven to be flawed in many ways. For example, "
93 "during 2011, two certificate authorities were compromised, and many fake "
94 "certificates were issued and used in the wild. See [Comodo: The Recent RA "
95 "Compromise](http://blogs.comodo.com/it-security/data-security/the-recent-ra-"
96 "compromise/) and [The Tor Project: The DigiNotar Debacle, and what you "
97 "should do about it](https://blog.torproject.org/blog/diginotar-debacle-and-"
98 "what-you-should-do-about-it)."
103 "It is clear for us that getting an commercial SSL certificate is not enough "
104 "to strongly authenticate our website, and for example authenticity of our "
105 "releases. That's why we always propose you [[stronger ways of "
106 "authenticating our Tails release|install/download#openpgp]] using OpenPGP "
112 msgid "Why get a commercial certificate then?"
117 "Still we decided to get a commercial certificate for the following reasons:"
120 #. type: Bullet: '- '
122 "It makes it harder to setup a simplistic [[man-in-the-middle attacks|doc/"
123 "about/warning#man-in-the-middle]] against the people who didn't use HTTPS so "
124 "far to visit our website."
127 #. type: Bullet: '- '
129 "Our website now is only available with HTTPS enabled. This may be important "
130 "to provide some confidentiality while posting on the forum for example."