Re: [Tails-dev] Release schedule for Tails 2.6 [*urgent*]
anonym: > > Testers, please let me know: > > * if you are available on 2016-09-02, late CEST > > * if you are available on 2016-09-03, morning to afternoon, CEST. > > * if you are available on 2016-09-12, late CEST > > * if you are available on 2016-09-13, morning to afternoon, CEST. > Yes signature.asc Description: OpenPGP digital signature ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] Release schedule for Tails 2.6 [*urgent*]
I'll be available the 12-13 of September. On 01/09/2016 19:35, anonym wrote: > Hi, > > I'll be the release manager for Tails 2.6, which is a major release > scheduled on 2016-09-13. The list of tickets targeting Tails 2.6 can be > found here: > > https://labs.riseup.net/code/projects/tails/issues?query_id=215 > > So, yeah, this is a very late date to send the schedule given that the > freeze will be tomorrow. I blame the distractions of summer and other > things. > > Here's the preliminary release schedule for Tails 2.6: > > * 2016-09-02: >- Feature Freeze: All feature branches targeting Tails 2.6 should > be merged into the `devel` branch by noon, CEST. I'm open to make > exceptions if you can be online and responsive during that > afternoon, but ask me first! >- Build and upload Tails 2.6~rc1. >- Start testing Tails 2.6~rc1 during late CEST if building the image > went smoothly. > > * 2016-09-03: >- Finish testing Tails 2.6~rc1 by the afternoon, CET. >- Release Tails 2.6~rc1. > > * 2016-09-12: > - All branches targeting Tails 2.6 *must* be merged into the `testing` > branch by noon, CEST. > - The upcoming Tor Browser is hopefully out so we can import it. > - Build and upload Tails 2.6 ISO image and IUKs. > - Hopefully start testing Tails 2.6. > > * 2016-09-13: > - Finish testing Tails 2.6 by the afternoon, CEST. > - Release Tails 2.6 during late CEST. > > Testers, please let me know: > > * if you are available on 2016-09-02, late CEST > > * if you are available on 2016-09-03, morning to afternoon, CEST. > > * if you are available on 2016-09-12, late CEST > > * if you are available on 2016-09-13, morning to afternoon, CEST. > > Cheers! > > ___ > Tails-dev mailing list > Tails-dev@boum.org > https://mailman.boum.org/listinfo/tails-dev > To unsubscribe from this list, send an empty email to > tails-dev-unsubscr...@boum.org. > ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Release schedule for Tails 2.6 [*urgent*]
Hi, I'll be the release manager for Tails 2.6, which is a major release scheduled on 2016-09-13. The list of tickets targeting Tails 2.6 can be found here: https://labs.riseup.net/code/projects/tails/issues?query_id=215 So, yeah, this is a very late date to send the schedule given that the freeze will be tomorrow. I blame the distractions of summer and other things. Here's the preliminary release schedule for Tails 2.6: * 2016-09-02: - Feature Freeze: All feature branches targeting Tails 2.6 should be merged into the `devel` branch by noon, CEST. I'm open to make exceptions if you can be online and responsive during that afternoon, but ask me first! - Build and upload Tails 2.6~rc1. - Start testing Tails 2.6~rc1 during late CEST if building the image went smoothly. * 2016-09-03: - Finish testing Tails 2.6~rc1 by the afternoon, CET. - Release Tails 2.6~rc1. * 2016-09-12: - All branches targeting Tails 2.6 *must* be merged into the `testing` branch by noon, CEST. - The upcoming Tor Browser is hopefully out so we can import it. - Build and upload Tails 2.6 ISO image and IUKs. - Hopefully start testing Tails 2.6. * 2016-09-13: - Finish testing Tails 2.6 by the afternoon, CEST. - Release Tails 2.6 during late CEST. Testers, please let me know: * if you are available on 2016-09-02, late CEST * if you are available on 2016-09-03, morning to afternoon, CEST. * if you are available on 2016-09-12, late CEST * if you are available on 2016-09-13, morning to afternoon, CEST. Cheers! ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
Re: [Tails-dev] [Secure Desktops] Tails' MAC 'leak prevention' question
On Fri 2016-08-26 14:50:12 -0400, intrigeri wrote: > Since then, NetworkManager gained the ability to randomize MAC > addresses [1]. If we delegate the bulk of the work to it, then this > becomes: > > a) We remove the modules blacklist logic. > b) We set up a boot-time firewall that blocks all outgoing connections >to non-loopback interfaces. > c) Once the user has made their decision wrt. MAC spoofing (that is, >in tails-unblock-network, run by PostLogin, just as it is now): > >1. We record that decision in some place where all legitimate > interested parties can check it out. >2. We configure NM accordingly. >3. We replace the boot-time firewall with the production one. >4. We start NetworkManager. > > Here again, hotplugged interfaces are not as well protected against > permanent MAC address leaks as the coldplugged ones. But this is > a compromise we are already doing in our current design. fwiw, i prefer mac address spoofing at the udev layer since it means the first userspace tool to see the device gets a chance to set the mac address immediately. It's easy enough to do by dropping a file in /etc/systemd/network/99-default.link with the contents: [Link] MACAddressPolicy=random Note that we will also need to tell network-manager to not automatically reset the MAC address to a its permanent one though, since the defaults for that setting are wrong: https://bugzilla.gnome.org/show_bug.cgi?id=770611 for the versions of nm with that crappy default setting, you'll also want to include a file /etc/NetworkManager/conf.d/20-mac-addr-preserve.conf with the contents: [device-mac-addr-preserve] ethernet.cloned-mac-address=preserve wifi.cloned-mac-address=preserve Regards, --dkg ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
[Tails-dev] Working on Persistence Seed PRNG
Hi, This is to announce a meeting for those interested on Friday, September 2th where we'll be working on: " Investigate whether we should resume shipping a static random seed"[1]. In addition to our blueprint[2] Please study some of this before we'll have the meeting! * September 2rd 2016, 12:00 - 14:00 (Paris/Amsterdam/Berlin time) The goal of this meeting is to have a clear understanding on where we stand and to divide tasks in addition to scheduling a follow-up meeting. Best, dr [1] https://labs.riseup.net/code/issues/7642 [2] https://tails.boum.org/blueprint/randomness_seeding/ ___ Tails-dev mailing list Tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to tails-dev-unsubscr...@boum.org.
