Hi, [email protected] wrote (26 Oct 2013 06:25:08 GMT) : > If users are looking for maximum security/privacy from Tails at the possible > sacrifice of stability, are they better off habitually using the latest stable > version of Tails, or the latest release candidate?
You're right that, on the short run, the latest RC fixes security issues first, and that's quite obvious why when one thinks of it: we release a RC before the corresponding stable release. But on the long run, I am much more confident in recommending the latest stable release if what you want is more security. We produce release candidates for a reason: to give the to-be-released code more exposure to testing, and to discover issues before it's declared stable and good for the masses. One of these days, a critical security issue will be discovered thanks to a RC (I don't remember if it happened already), and then everyone will be happy to have used it for testing only. > I also looked at the list of known issues for any release candidates listed > on the > news page. There were no security-related issues listed there, though that > could be > an exercise in caution on the part of Tails contributors not to announce known > security issues, rather than a lack of known security issues. We simply don't do security announces for RC. > Also, only 0.21~rc1 and 0.20~rc1 were included on this page. This page only lists the N last months or so of news. The full history is in Git. > On the Tails security page [2], there are no headings that call out release > candidate > versions specifically, but it's not clear that they would necessarily be > included on > this page. We only do security announces for actual releases. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc _______________________________________________ Tails-support mailing list [email protected] https://mailman.boum.org/listinfo/tails-support
