Feature #11809
Deal with tails.b.o's X.509 certificate expiring early 2017
Start date:
2016-09-19
Due date:
% Done:
100%
Description
Let’s expect that it’ll be renewed in December, possibly before Tails 2.8 (2016-12-13) or shortly after. If the certificate’s CA changes, then we need to have the new CA added by config/chroot_local-hooks/58-create-tails-website-CA-bundle in Tails 2.7 (2016-11-08).
Subtasks
| Feature #11810: Have our website CA bundle trust Let's Encrypt CA | Resolved | 100 |
|||
| Feature #11811: Remove AddTrust_External_Root.pem from our website CA bundle | Resolved | 100 |
|||
| Feature #11814: Have DAVE also trust Let's Encrypt CA | Resolved | 100 |
History
#1 Updated by intrigeri 2016-09-19 07:24:41
- Target version deleted (
Tails_2.7)
(Subtasks track their own deadlines.)
#2 Updated by sajolida 2016-09-19 08:21:41
If boum.org changes their certificate authority, then we’ll also have to update DAVE, no?
#3 Updated by intrigeri 2016-09-20 03:49:25
> If boum.org changes their certificate authority, then we’ll also have to update DAVE, no?
Right, good catch! I’ve filed Feature #11814 about it.
#4 Updated by intrigeri 2016-11-05 14:22:53
- Target version set to 284
(The last bit should be completed in Tails 2.9.)
#5 Updated by anonym 2016-11-25 10:56:54
- Target version changed from 284 to Tails 2.10
#6 Updated by intrigeri 2016-12-26 11:18:24
- Status changed from Confirmed to In Progress
Apparently we’re there: our website is now using a Let’s Encrypt certificate.
#7 Updated by intrigeri 2016-12-28 08:45:13
- Assignee changed from intrigeri to anonym
- QA Check set to Ready for QA
The only remaining subtask is on anonym’s plate.
#8 Updated by anonym 2017-01-10 14:19:13
- Status changed from In Progress to Fix committed
- Assignee deleted (
anonym) - QA Check changed from Ready for QA to Pass
#9 Updated by anonym 2017-01-24 20:42:45
- Status changed from Fix committed to Resolved