Merge pull request #236 from daira/2725.timezone-test.0

[tahoe-lafs/tahoe-lafs.git] / docs / backdoors.rst

diff --git a/docs/backdoors.rst b/docs/backdoors.rst
index e75a19f9a3b00e406cd7734fb599895ea8824041..97716fcadf83122ed7fd3678fab5e762760bf736 100644 (file)
--- a/docs/backdoors.rst
+++ b/docs/backdoors.rst
@@ -1,3 +1,5 @@
+.. -*- coding: utf-8-with-signature -*-
+
 Statement on Backdoors
 ======================
 
@@ -10,7 +12,7 @@ to encrypted data.
 
 (login required; username/password pairs available at `bugmenot`_).
 
-.. _recently reported: http://www.nytimes.com/2010/09/27/us/27wiretap.html
+.. _recently reported: https://www.nytimes.com/2010/09/27/us/27wiretap.html
 .. _bugmenot: http://www.bugmenot.com/view/nytimes.com
 
 Commentary by the `Electronic Frontier Foundation`_, `Peter Suderman /
@@ -22,16 +24,16 @@ Reason`_, `Julian Sanchez / Cato Institute`_.
 
 The core Tahoe developers promise never to change Tahoe-LAFS to facilitate
 government access to data stored or transmitted by it. Even if it were
-desirable to facilitate such access—which it is not—we believe it would not
-be technically feasible to do so without severely compromising Tahoe-LAFS'
-security against other attackers. There have been many examples in which
-backdoors intended for use by government have introduced vulnerabilities
-exploitable by other parties (a notable example being the Greek cellphone
-eavesdropping scandal in 2004/5). RFCs `1984`_ and `2804`_ elaborate on the
-security case against such backdoors.
+desirable to facilitate such access -- which it is not -- we believe it would
+not be technically feasible to do so without severely compromising
+Tahoe-LAFS' security against other attackers. There have been many examples
+in which backdoors intended for use by government have introduced
+vulnerabilities exploitable by other parties (a notable example being the
+Greek cellphone eavesdropping scandal in 2004/5). RFCs `1984`_ and `2804`_
+elaborate on the security case against such backdoors.
 
-.. _1984: http://tools.ietf.org/html/rfc1984
-.. _2804: http://tools.ietf.org/html/rfc2804
+.. _1984: https://tools.ietf.org/html/rfc1984
+.. _2804: https://tools.ietf.org/html/rfc2804
 
 Note that since Tahoe-LAFS is open-source software, forks by people other
 than the current core developers are possible. In that event, we would try to
@@ -39,7 +41,7 @@ persuade any such forks to adopt a similar policy.
 
 The following Tahoe-LAFS developers agree with this statement:
 
-David-Sarah Hopwood
+David-Sarah Hopwood [Daira Hopwood]
 
 Zooko Wilcox-O'Hearn