summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2013-12-11 06:20:58 +0000
committerGravatar admin <admin@branchable.com>2013-12-11 06:20:58 +0000
commit23fcd3b8d1d3ba1c71f67447f7beef5eb6bb5ea3 (patch)
treeca5422d7a45e3987b037626d4b9263f8f3314913
parent7a622d1871f92c25a1cadc2e82a14cee256d209c (diff)
Added a comment
-rw-r--r--doc/bugs/Automatic_upgrades_should_be_cryptographically_signed/comment_1_37ed871c82879a31c2d8cfc7d9736548._comment10
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/bugs/Automatic_upgrades_should_be_cryptographically_signed/comment_1_37ed871c82879a31c2d8cfc7d9736548._comment b/doc/bugs/Automatic_upgrades_should_be_cryptographically_signed/comment_1_37ed871c82879a31c2d8cfc7d9736548._comment
new file mode 100644
index 000000000..8deae448c
--- /dev/null
+++ b/doc/bugs/Automatic_upgrades_should_be_cryptographically_signed/comment_1_37ed871c82879a31c2d8cfc7d9736548._comment
@@ -0,0 +1,10 @@
+[[!comment format=mdwn
+ username="http://joeyh.name/"
+ ip="209.250.56.87"
+ subject="comment 1"
+ date="2013-12-11T06:20:57Z"
+ content="""
+The links to the builds use https. The automatic upgrades use https (and wget or curl, which will reject an invalid SSL certificate).
+
+So, it is cryptographically signed. Of course SSL certificates are only as secure as the CAs. But using a gpg key that most users have no particular reason to trust would not add a lot of security.
+"""]]