[Tails-dev] Relative security of Debian unstable / testing / stable
The current official Debian position on security regarding unstable and stable: Q: How is security handled for unstable? A: The short answer is: it's not. Unstable is a rapidly moving target and the security team does not have the resources needed to properly support it. If you want to have a secure (and stable) server you are strongly encouraged to stay with stable. http://www.debian.org/security/faq.en.html But my empirical observations are that this has not been true for several years now: Debian unstable has been promptly supported with security fixes. Is anybody aware of any research regarding the relative security of Debian unstable / testing / stable or similar Linux distributions? Cheers, Andreas ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Logo: some ideas
On 07/09/13 14:44, carmie wrote: I'm sorry for my silence, I'm not speaking english very well, to write you all is impressive for me and I was busy in august. Hi again, I'm sorry you feel impressed! I find your English perfectly fine for us to communicate. Here [1] is the last version of the cat I drawned, I just simplify the line in inkscape. I read your comments, I found them very constructive, I also thought I should have wrote you a little something with the proposition to explain a bit more my choices, I'm sorry I took some times to reply. Cats are quiet, indeed, and this one have 3 rings on his tail, like wild european cat [2] This kind of cats are sadly rare nowadays. They can't be domesticated. They lives anonymously in the woods. I like that idea. I did not made other details, and maybe it's not easily understable. The body of the cat is maybe too dark to notify the rings. I thought dark gray would sound more anonymous, but it did not seems to work, none of you seemed to noticed it. Using gray looks like a good idea. Adding more contrast between the body and the rings might make them more visible. I didn't notice them as something of importance at first. I'm not sure I would find light gray to look less anonymous than dark gray. I choosed a stretching pose because it can be contain in a square, or a circle, to be readable in a very little icon, like a favicon. That's also the reason I avoided gradient, I'm not sure it would be readable in icons. The idea of erasing tracks is not clear either in my proposition, and, maybe, it could be improve with a background of color, and a white line instead of this purple one, or maybe if the purple lines was the beginning of the word Tails, hidden by the tail of the cat. Something like that.. I didn't think about the importance of the geometry of the drawing to fit into a square. That makes total sense. The exemple cat pose that Sajolida give is imo very interesting, reflecting more discret move, but it doesn't fit in a square :/ Maybe could we find another pose, with a similar idea? I think we can spend some more time thinking about a different pose and see what comes out of that. signature.asc Description: OpenPGP digital signature ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Contribute section of the website: some ideas
I fear that OS developer may be too specific and needlessly excluding many people who don't identify as OS developers. Software developer, perhaps? Good idea. We don't have anything to put under Designer for the moment but we might at some point. We do, see my previous email :) I'm not sure which email you are referring to. Are you talking about the page Improve the Tails website that we could put under this role? signature.asc Description: OpenPGP digital signature ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Contribute section of the website: categories
On 14/09/13 17:06, Alan wrote: I think we must find a way to group this, as a category with only one item is kindof useless. I think that a category should have 2 to 4/5 items. I disagree here. I don't see this work are try only trying to come up with categories to order a bunch of links. Now I am more trying to identifying roles or skills, that possible contributors can identify with, and point them to the relevant tasks. If a role only points to one task, then that's fine with me. A stronger, but somehow related, limitation for me would be to stick to a number of roles that good enough to structure and present our roles. - Content writer - Improve documentation - Translator - Improve Tails in your own language I really think we should group these into Have language skills or something like that. I disagree, and Fedora also seem to find it important to differentiate between people who feel like writing things, and people who feel list translating what is already been written. - Server administrator - Setup a BitTorrent seed - Setup a HTTP mirror It have been suggested in a previous email to group these two. We might also want to group the two previous categories (developer and administrator) into one Have computer skills as you suggested before. I'm however unsure whether it would be less appealing to sysadmins. I'd don't really care about how well this section is classified. We don't have problems to get mirrors, and people are already pointed to that page before that and more systematically, from the download page. * Have language skills - Improve documentation - Improve Tails in your own language * Have computer skills - Fix a bug - Implement a new feature - Setup a mirror * People Person - Spread the word * Designer - Improve the website design - contribute/how/website It seems me nice but the to last one-itemed categories. So I created two mockups which both our proposals on the blueprint. Here they are: https://tails.boum.org/blueprint/contribute_section/ Make sure local.css is reloaded. signature.asc Description: OpenPGP digital signature ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Relative security of Debian unstable / testing / stable
intrigeri: Andreas Kuckartz wrote (16 Sep 2013 08:04:44 GMT) : But my empirical observations are that this has not been true for several years now: Debian unstable has been promptly supported with security fixes. Well, yes and no. It is correct that Debian unstable is not supported by the security team. But this does not mean that it's in a bad shape security-wise: it's just hard to predict and rely upon. Security fixes in unstable generally do happen fast (and certainly faster than in testing since the secure-testing effort faded out), *but* it all depends on the package maintainers. Hoping it helps :) Yes, thanks. That is in line with what I have observed. If it all depends on package maintainers that might imply that unstable is generally more secure than stable. And upstream developers generally are more interested in maintaining the most recent versions of their software. If you are interested to go on with this discussion, then perhaps it could be moved to a more appropriate place such as the debian-user mailing-list? I probably will move it to debian-secur...@lists.debian.org. (Or it should be clarified how this relates to Tails development.) Well, Tails can choose between stable and unstable packages, therefore statistical security might be a factor in such decisions. My hypothesis is that generally (but not always) unstable is more secure regarding several security aspects (but not all). Cheers, Andreas ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Contribute section of the website: some ideas
We don't have anything to put under Designer for the moment but we might at some point. We do, see my previous email :) [...] Are you talking about the page Improve the Tails website that we could put under this role? Yes, that was what I meant (since you previously mentionned that we could group the web graphics into a single category, but you thought we had no content, while we have). But perhaps it doesn't fit well in there. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review'n'merge feature/linux-3.10.11
On Sun, Sep 15, 2013 at 07:07:06PM +0200, intrigeri wrote: Hi, = please review feature/linux-3.10.1, and merge it into devel. Reviewed, tested successfully, so merged into devel. Congrats! bert. ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Contribute section of the website: categories
Hi, sajol...@pimienta.org wrote (16 Sep 2013 11:33:42 GMT) : On 14/09/13 17:06, Alan wrote: I think we must find a way to group this, as a category with only one item is kindof useless. I think that a category should have 2 to 4/5 items. I disagree here. I don't see this work are try only trying to come up with categories to order a bunch of links. Now I am more trying to identifying roles or skills, that possible contributors can identify with, and point them to the relevant tasks. If a role only points to one task, then that's fine with me. A stronger, but somehow related, limitation for me would be to stick to a number of roles that good enough to structure and present our roles. I concur. - Server administrator - Setup a BitTorrent seed - Setup a HTTP mirror It have been suggested in a previous email to group these two. We might also want to group the two previous categories (developer and administrator) into one Have computer skills as you suggested before. I'm however unsure whether it would be less appealing to sysadmins. I'd don't really care about how well this section is classified. We don't have problems to get mirrors, and people are already pointed to that page before that and more systematically, from the download page. (OK, let's assume our mirror pool is sustainable if we remove this link from the How to contribute section -- we can always try it and see what happens.) I'm not quite comfortable with the idea of dropping some important and very real ways of contributing from this list, as is done in the `Without Server administrator' proposal. It feels a bit like negating the actual work people are doing. I'm unsure how important this really is, but I thought I would mention this uncomfortable feeling. Anyway, this may not matter much, as maybe a System administrator category will be needed anyway: there's been work done since the summit towards being able to have a contribute/sysadmin page, so at some point we surely want to add a link about this kind of work (I would say by the end of the year). I'm not sure how it integrates with the existing proposals, but perhaps we would be better off taking this into account right from the beginning. So I created two mockups which both our proposals on the blueprint. Thanks! It does help me think about the whole thing. I'm generally happy with the first proposal. One thing that bothers me slightly is where tasks like writing press releases would fit in. Right now, the place it fits best is probably the Spread the word page. However, it's listed in People person, and I doubt people skilled at writing PR things would necessarily identify as People persons, and then they could look at the Content writer category and get lost (because they don't feel like writing documentation). Perhaps we should have: * Writer - Improve documentation - Write press releases [points to Advocate Tails page] (could surely be phrased better) * Speaker - Talk at events [points to Advocate Tails too] ... then rename Spread the word to Advocate Tails (and possibly rename the page altogether from contribute/how/promote to contribute/how/advocate), and split this page into two big sections, one being for speakers, the other for writers of PR and alike? Thoughts? Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review doc update wrt. problematic USB sticks
sajol...@pimienta.org wrote (16 Sep 2013 12:03:37 GMT) : If we believe the same error message is printed out when the live-media=removable trick needs to be used then we can described them at the beginning of a step 5: « if the error message is xxx then, try to remove the live-media=removable option. » That might add a bit of structure. But otherwise the current flow is fine with me. Right, done (4d21697). Doc writers, please review and suggest improvements if needed :) Great. I did some minor rephrasing. Thanks! The caution warning is a very long sentence but I didn't find a good and quick solution to split it. Neither could I. Cheers -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
[Tails-dev] Reviewing doc/cold-boot-attack
I had a look at the work done on the doc/cold-boot-attack branch. I'm very happy to see new people taking initiatives regarding the documentation lately. I pushed it to the main repo. Regarding the structure, I felt that it was talking about two things that could be better separated or advertised: - memory wipe on shutdown - emergency shutdown I'd be tempted to move the emergency shutdown to the First steps section. And rename that page Memory wipe on shutdown and still have it in the Advanced topics section. What do you think? Regarding formatting: - The link to cold-boot attack on Wikipedia is broken. - I'd add a link to Wikipedia on the first occurrence of RAM. - I'd use a class=bug section when mentioning the emergency shutdown bug after using Tails USB Installer. Regarding terminology: - I'd say RAM instead of the RAM. - Don't use junk, random data might do the trick instead. - Please use a spell checker on your pages before pushing them! with Vim do `:set spell spelllang=en`. Does that make sense? signature.asc Description: OpenPGP digital signature ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Settings Configuration
Brilliant, i'll forward this on Apologies for the CC'ed email (tails-dev@boum.org), it was an extra address your colleague sent me earlier... Many thanks On 14/09/2013 at 1:01 PM, Alan wrote:Hi, 2 Questions please: You're currently asking on the public tails development mailing list. I'll answer here now, but please ask further public usage questions on the dedicated tails-supp...@boum.org mailing list. 1) I managed to convince a friend that Tails is the way forward in terms of Secure/Hack-proof internet browsing. However he has some IT background and would like to have some information about the Firewall in Tails? How secure is it or maybe a link to some material about it? Please read https://tails.boum.org/contribute/design/#index18h3 2) I was trying to install a linux package of Truecrypt (see attached file) on Tails, however I am new to Linux and a novice can you help?...please :-) Perhaps a step by step installation instruction as I have tried unpacking and simply double clicking the file (like in Windows) without success... Please read https://tails.boum.org/doc/encryption_and_privacy/truecrypt/ Cheers___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
