Hi, anonym wrote (28 Dec 2013 17:25:37 GMT) : > 27/12/13 18:05, intrigeri wrote: >> I've pushed a few minor improvements on top (oh crap, I realize I've >> done this in feature/spoof-mac, which is the right place IMO, but not >> the way you've been doing it — I'm sorry).
> The reason I wanted to have the design in our master branch and not the > feature branch was to make it available on our website so it can be > linked to in the call for testing. Like in your CFT for incremental > updates I want to urge people with "security auditing skills" to have a > look at the design, and I think they'd be encouraged better like this > compared to linking to the raw markdown in git. I see, and I think you're totally right. If you want, I'll cherry-pick the relevant commits into master later today or tomorrow. Shall I? >> (I would personally have done this in two steps, first issuing a clear >> call for testing on tails-dev, and second a broader public call for >> testing, but well, I guess it's too late now, so go, go, go! :) > Ok. Why? To catch show stoppers before the public call? Yes. AFAICT, only you and me have tested this code so far, on a pretty limited range of hardware. Anyway, here we go, fingers crossed :) 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
