Re: [Tails-dev] MAC spoofing: current status? [Was [RFC] Design (and prototype) for MAC spoofing in Tails]
anonym wrote (22 Dec 2013 15:08:56 GMT) : Could any one with the know-how set up a nightly build of feature/spoof-mac? I don't have time to look at the rest right now, but I didn't want to be blocking on the Jenkins front, so: this is done! I've just pushed the current feature/spoof-mac to the lizard remote, which triggered a build. The results should land there in 20-30 minutes: http://nightly.tails.boum.org/build_Tails_ISO_feature-spoof-mac/ Note that *you* have to push the stuff you want to see built to this remote, in addition to our regular repository: gitol...@git.puppet.tails.boum.org:tails Builds are triggered by Git push, and another daily build is run anyway. You'll want to monitor Jenkins from time to time to ensure it still builds fine: https://jenkins.tails.boum.org/ 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] MAC spoofing: current status? [Was [RFC] Design (and prototype) for MAC spoofing in Tails]
Hi, anonym wrote (03 Dec 2013 00:33:43 GMT) : Definitely. I'll return to this post in a few days (when I have more time on my hands) with more affirmative answers + proper bugs/tasks. See this post more as a heads up. Ping? 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] MAC spoofing: current status? [Was [RFC] Design (and prototype) for MAC spoofing in Tails]
Hi, (I'm acting with my RM hat for the next two Tails releases on.) It's now clear feature/spoof-mac won't make it into 0.22. No big deal, as long as it's merged soon enough and we can publish some beta version of it by the end of the year. I'd like to have some visibility on what's left to do for this to happen. I've updated the existing tickets to match the current state. anonym, I think now would be a great time to sum up what the current state is: * remaining coding blockers * remaining design documentation blockers (the blueprint didn't make it into a design doc yet, right?) * remaining user documentation blockers (are there placeholders doc pages with indications for doc writers already?) * once all coding blockers are solved, I think a bolder call for testing (pointing to a nightly built ISO from experimental) would be good: some of us told that they are lost in this huge thread, and it's unclear to them how close we are to the please widely test this code state (I know, one call for testing was sent as part of this thread, but I wouldn't expect everyone to have read the whole thread and seen it, so a dedicated email in a new thread could be worth it) I'd love to see tickets created for all the blockers, so that one can easily track the progress of this feature. 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
