Bug #7730
Pidgin configuration includes two expired SSL certificates
100%
Description
Pidgin in Tails is shipped with two expired SSL certificates (reported by @scott_ainslie on twitter).
config/chroot_local-includes/etc/skel/.purple/certificates/x509/tls_peers *> certtool -i < irc.indymedia.org |grep After
Not After: Thu May 27 19:54:51 UTC 2010
config/chroot_local-includes/etc/skel/.purple/certificates/x509/tls_peers *> certtool -i < jabber.ccc.de |grep After
Not After: Sun May 16 06:06:57 UTC 2010
Attached is a patch to remove these expired certificates.
Files
Subtasks
Related issues
Related to Tails - Feature #5909: Pidgin should rely on the cached certificates | Confirmed | 2013-07-19 |
History
#1 Updated by intrigeri 2014-08-03 09:09:22
- related to Feature #5909: Pidgin should rely on the cached certificates added
#2 Updated by intrigeri 2014-08-03 09:09:54
- Subject changed from Pidgin w/ Tails includes two expired SSL certs in profile to Pidgin configuration includes two expired SSL certificates
#3 Updated by intrigeri 2014-08-03 09:13:53
- Status changed from New to In Progress
- Target version changed from Tails_1.1.1 to Tails_1.2
- % Done changed from 90 to 50
To the best of my knowledge, the fact that these certificates are expired has no practical impact whatsoever (Feature #5909) unfortunately, so not worth it for 1.1.1 IMO. Retargetting to 1.2. Lowering “% Done” down a bit to leave room for potential review/needs more dev/etc. cycles.
#4 Updated by intrigeri 2014-08-12 13:53:47
- Category set to 213
#5 Updated by anonym 2014-10-08 09:37:34
- Status changed from In Progress to Fix committed
- % Done changed from 50 to 100
- QA Check changed from Ready for QA to Pass
#6 Updated by anonym 2014-10-16 08:10:44
- Status changed from Fix committed to Resolved