Re: [Tails-dev] Fwd: live-config_3.0.4-1_i386.changes ACCEPTED into unstable
On Fri, Aug 24, 2012 at 05:03:50PM +0200, intrigeri wrote: Hi, live-config (3.0.4-1) unstable; urgency=low . * Using /etc/live/config/* instead of /etc/live/config.d/*.conf and /live/image/live/config/* instead of /live/image/live/config.d/*.conf for consistency reasons. * Removing leftover from live-debconfig in postrm. * Recreating /etc/live/config in postinst. * Removing /etc/live/config if empty on purge in postrm. Given we install live-config from sid, I think next builds (including 0.13~rc2) will get that one, and then we're affected by the config directory name change. Do we want to keep the current version tested in rc1 (live-config 3.0.3-1) or get the new one and adapt? I'm strongly tempted by the former. Given the current state of our work for the 0.13 release, I'm also tempted to say we should delay this for the next point release too. We're supposed to have freezed after all. bert, slowly getting into wearing its neatpicker hat :) ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please review feature/assymetric_gpgApplet [sic!]
On Fri, Aug 24, 2012 at 09:21:22AM +0200, intrigeri wrote: anonym wrote (22 Aug 2012 08:53:02 GMT) : All is merged into experimental. Thanks. Unfortunately, I forgot to merge it at pre-freeze time, and unfortunately nobody noticed it in time since the todo/qa tag was not set after the last development round, so that will be stuff for the 0.14 merge window. I updated the ticket to reflect the current state of things. Sorry about that :( (To clarify: when, after I've reviewed a branch, I'm asking for more development to be done before merging, then I'm setting the ticket back to todo/code state, and I consider it's the responsibility of the branch/ticket holder to change it back to todo/qa once they consider the issues raised by the reviewer were fixed. If we agree on that, perhaps it's material for our upcoming how changes go into Tails improved process doc.) Sounds like a good process, agree to add this in the documentation. bert. ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
[Tails-dev] Upcoming release schedule plan
Hi, Following our discussions on the timeline for the next release, here is the plan we ended up with and I committed to send on this list : - Theoritically: ESR (August 28th) + 1 week = September 4th - August 23: release 0.13~rc1, do the test suite together - Week 35 - Mon 27th: ESR is out update of the GnuPG docs - Week 36 - Tue 4th: release 0.13~rc2, testing phase - Thu 6th: monthly meeting - Week 37 - Tue 11th: release 0.13 (final) Hope I didn't forget anything. If anyone on this list is willing to participate to the release tests, help on this is more than appreciated. :) bert. ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Please test 0.13-rc1
Hi, I could not upload the rc1 at the planned time, sorry. I will do it on Monday. Cheers! ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Tails: pcmcia / firewire / etc.
Hi, I'd still go for [...] A possible middle-ground could be to [...] FWIW, I've created a parent ticket for these issues, and pasted the various implementation ideas in there: todo/protect_against_external_bus_memory_forensics 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] Tails: pcmcia / firewire / etc.
Hi, Jacob Appelbaum wrote (22 Aug 2012 21:01:22 GMT) : Pop up a dialog and ask hey, you want to use firewire? - at least if they had enabled a password, they will have to bypass a screen lock or authenticate to enable full memory forensics. I'm not sure I understand clearly what you are suggesting. When do you think such a dialog should appear? Cheers! ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] PGP Smart Cards
On Fri, Aug 24, 2012 at 12:34 PM, intrigeri intrig...@boum.org wrote: Are you interested in trying to backport these two packages for Squeeze, or testing backports we would prepare, and see if that's enough to get things working? I can't say i'd be the best person to make the back ports as I have no experience with that, but I'd be more then happy to help test them. Let me how I can help and I will get back pretty fast about things. Abel, a developer for the guardian project is working on a fork of Tails called 'Clean Room'. Basically, it would just be a Tails distribution that includes this drivers, removes all networking, and adds script that facilitates creating and managing an offline master key. I think it'd still be very useful to have the drivers in Tails and other support that doesn't conflict with the more general computing environment that is Tails. He plans to release an early version this week I believe. I'll make its gets mentioned on the list if anyone is interested. Regards, patch ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] PGP Smart Cards
On Sat, Aug 25, 2012 at 10:35 PM, Patrick Bx patric...@gmail.com wrote: I can't say i'd be the best person to make the back ports as I have no experience with that, but I'd be more then happy to help test them. Let me how I can help and I will get back pretty fast about things. Hi, what's the big deal about having support for PGP SmartCards? Liberté had ccid + pcsc-lite and some other packages (engine_pkcs11) since forever, and the latest snapshot has gnupg-pkcs11-scd. Maybe you can test this support [1] and tell what's missing? I don't have the hardware, unfortunately (although I think that at one point I considered asking some guy who would send evaluation USB tokens for a free one, but it turned out as too much trouble). [1] https://forum.dee.su/topic/a-new-snapshot-has-been-released-20120825 -- Maxim Kammerer Liberté Linux: http://dee.su/liberte ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Tails: pcmcia / firewire / etc.
intrigeri: Hi, Jacob Appelbaum wrote (22 Aug 2012 21:01:22 GMT) : Pop up a dialog and ask hey, you want to use firewire? - at least if they had enabled a password, they will have to bypass a screen lock or authenticate to enable full memory forensics. I'm not sure I understand clearly what you are suggesting. When do you think such a dialog should appear? If a firewire card was inserted into the pcmcia slot and pcmcia/cardbus is active, I suggest it. If such things were entirely disabled, I'd have a setup wizard that stores preferences in the persistent storage area. All the best, Jacob ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
