[Tails-dev] Please review&merge feature/obfs3
Hi, the feature/obfs3 branch adapts the ClientTransportPlugin line added to torrc when needed to support the obfs3 bridges, that the new obfsproxy 0.2.x (automatically picked up by the latest Tails ISO image builds) supports. Please review&merge. ticket: todo/obfs3 branch: feature/obfs3 candidate for Tails 0.18 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] Please review & merge feature/set-wireless-devices-state
Hi, about the feature/set-wireless-devices-state branch, please: 1. review the end-user doc 2. test on whatever hardware you have access to 3. merge into devel ticket: todo/set_wireless_devices_state Candidate for 0.18. 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 and merge feature/about_tails
On 08/04/13 15:30, Alan wrote:
> Hi,
>
> On Fri, 15 Mar 2013 20:02:06 +0100 intrigeri wrote:
> -Categories=GNOME;GTK;Core;Utility;
> +Categories=GNOME;GTK;Utility;
>>> According to th Desktop Menu Specification[1], the "Core" category
>>> means "Important application, core to the desktop such as a file
>>> manager or a help browser". That is unclear to me if when replacing
>>> a GNOME application by a custom one we should preserve tghis
>>> category. "GNOME" which means "Application based on GNOME
>>> libraries" should perhaps be removed too. Thought? The current
>>> version perserves all the categories of the original version.
>>
>> If there's no *visible* effect of removing Core, then I don't want to
>> maintain a bigger delta, nor discuss it any further. I've got other
>> bikesheds to pick a color for :)
>>
> Done. I thus ask for review and merge again.
I tested it as merged in experimental today and choosing "About Tails"
in the System menu causes a "Starting About Tails" to appears for some 5
seconds in the bottom panel, and then it disappears, and nothing else.
Trying to run tails-about from the command line returns the following trace:
amnesia@amnesia:~$ tails-about
Traceback (most recent call last):
File "/usr/local/bin/tails-about", line 8, in
gettext.install("tails-about")
File "/usr/lib/python2.6/gettext.py", line 493, in install
t = translation(domain, localedir, fallback=True, codeset=codeset)
File "/usr/lib/python2.6/gettext.py", line 478, in translation
t = _translations.setdefault(key, class_(open(mofile, 'rb')))
File "/usr/lib/python2.6/gettext.py", line 180, in __init__
self._parse(fp)
File "/usr/lib/python2.6/gettext.py", line 337, in _parse
tmsg = unicode(tmsg, self._charset)
LookupError: unknown encoding: CHARSET
signature.asc
Description: OpenPGP digital signature
___
tails-dev mailing list
tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] April's low-hanging fruits week
Hi, Today: * feature/debian_live_log_in_bugreports and our updated custom programs ([[todo/newer_live-boot]]) were reviewed, tested and merged. * feature/obfs3 ([[todo/obfs3]]) was pushed. Review & merge request sent to tails-dev. * feature/set-wireless-devices-state was reviewed and tested. Its end-user documentation was drafted. Review & merge request sent to tails-dev. How about we schedule a 3-4 hours public low-hanging fruits meeting every month with the same relaxed push/review/merge process? It could also be used to tackle the pending review&merge requests, if people feel like it. 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] [tor-talk] secure and simple network time (hack)
On Fri, Jul 20, 2012 at 3:07 AM, Jacob Appelbaum wrote: > Allow me to be very explicit: it is harder to parse an HTTP Date header > than properly than casting a 32bit integer and flipping their order. The > attack surface is very small and easy to audit. Just discovered that tlsdated in tlsdate-0.0.6 is dying with a segmentation fault after a while. Not surprised after seeing the code — my experimentation with this gimmick is finally over. Turns out that “throw something together and wait for patches” is not a sound development approach. -- 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] manual usb installation for mac
On 11/04/13 10:39, intrigeri wrote:
> Hi,
>
> kolohe wrote (10 Apr 2013 17:51:41 GMT) :
>> Everything removed in this reply was changed.
>
> :)
>
>>> - The Markdown of the bullet list in step 4 is still buggy. I'm sorry
>>> I should have made it clear that the single quotes I wrote against
>>> every bullet point was here only to delimit what I was suggesting,
>>> but should not have been pasted as is.
>
>> I removed the single quotes. Is it working properly now?
>
> Yes.
>
>>> - step 6 ("Reboot your Mac") seems awkward to me, as we just
>>> redirected the user to the "start Tails" section on the download
>>> page, so they're facing contradictory information at this point.
>>> Perhaps the Mac-specific bits of step 6 should be integrated into
>>> the download page's step 6 somehow?
>>>
>
>> I combined the Reboot your Mac and "start Tails" into the div
>> class="next". Is that good?
>
> Looks good to me.
>
> Congrats!
>
> I've merged your branch into the `doc/manual_usb_installation/mac' one
> in our main Git repository, and pushed a few minor fixes on top of it.
>
> sajolida, may you please have a look and merge if you're happy
> with it?
>
> (ticket: todo/document_USB_boot_for_Intel_Mac)
I had a look at the new doc. I'm glad we found a solution for that!
I did many little changes that ended up being a mess to commit nicely.
So that's commit a6a9ae3..c49fcc1. Sorry for the blob.
While I was at it I also improved a bit the style of the Linux
documentation.
If you're fine with that I'll merge it into master, unfuzz what I can in
the translations, and notify the translators.
signature.asc
Description: OpenPGP digital signature
___
tails-dev mailing list
tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] [tor-talk] secure and simple network time (hack)
On Fri, Apr 12, 2013 at 02:43:13PM +0300, Maxim Kammerer wrote: > On Fri, Jul 20, 2012 at 3:07 AM, Jacob Appelbaum wrote: > > Allow me to be very explicit: it is harder to parse an HTTP Date header > > than properly than casting a 32bit integer and flipping their order. The > > attack surface is very small and easy to audit. > > Just discovered that tlsdated in tlsdate-0.0.6 is dying with a > segmentation fault after a while. Not surprised after seeing the code > — my experimentation with this gimmick is finally over. Turns out that > “throw something together and wait for patches” is not a sound > development approach. Did you get a stack trace? Also, yes, tlsdated is not very well-written. I wrote it in a great hurry and now don't really have time to undo the worst of the hacks :(. Patches gratefully accepted. -- elly ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] manual usb installation for mac
sajol...@pimienta.org wrote (12 Apr 2013 13:28:36 GMT) : > If you're fine with that I'll merge it into master, unfuzz what I can in > the translations, and notify the translators. Please go ahead :) 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] [tor-talk] secure and simple network time (hack)
On Fri, Apr 12, 2013 at 02:43:13PM +0300, Maxim Kammerer wrote: > On Fri, Jul 20, 2012 at 3:07 AM, Jacob Appelbaum wrote: > > Allow me to be very explicit: it is harder to parse an HTTP Date header > > than properly than casting a 32bit integer and flipping their order. The > > attack surface is very small and easy to audit. > > Just discovered that tlsdated in tlsdate-0.0.6 is dying with a > segmentation fault after a while. Not surprised after seeing the code > ? my experimentation with this gimmick is finally over. Turns out that > ?throw something together and wait for patches? is not a sound > development approach. Did you get a stack trace? Also, yes, tlsdated is not very well-written. I wrote it in a great hurry and now don't really have time to undo the worst of the hacks :(. Patches gratefully accepted. -- elly signature.asc Description: Digital signature ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Discussion on minitube
I will try to install it in Tails and see how it works. Thanks for the info! Alessandro 2013/4/9, intrigeri : > Hi, > > intrigeri wrote (06 Mar 2013 09:45:35 GMT) : >> Alessandro Grassi wrote (01 Mar 2013 21:38:03 GMT) : >>> 2013/3/1, intrigeri : BTW, smtube (http://smplayer.sourceforge.net/smtube.php) was uploaded to Debian (waiting in the NEW queue) two weeks ago, no idea if that might be a better candidate. > >>> I can't find any .deb packages yet. > >> This is expected: Debian does not publicly distributes software before >> the ftp-master team has checked [...]. > > smtube is now available from Debian experimental, and installs nicely > on a Debian Wheezy desktop system. I've set it up to use Totem, and > indeed it runs "/usr/bin/totem http://xyz";. > > Who knows, its authors might be a bit more reactive, when submitted > patches, than the Minitube's one? > > 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 mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
[Tails-dev] Tails Jenkins setup: present and future
Hi, bertagaz and I have just spent quite some time together working on our Jenkins setup. Tails core developers can now push stable, testing, devel and experimental branches to `gitol...@git.puppet.tails.boum.org:tails'. Whenever they do this, an ISO image is built on builder.lizard. The product of this build is kept there for a while. Along the way, we have patched vagrant/provision/assets/build-tails to make it support our Jenkins build setup too. The changes (feature/jenkins-compatible-build-script) were merged into stable, testing, devel and experimental. Vagrant users, please verify that the script still works for you. Next steps in terms of what's visible externally: * publish build products on http://nightly.tails.boum.org/ * automate mirroring process from our master Git repository to the clone on lizard, so that we don't have to push to a special remote * automatically build Debian packages for our custom programs See the roadmap for details: https://tails.boum.org/todo/automated_builds_and_tests/#index3h1 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 Jenkins setup: present and future
Amazing! As someone whose grappling with Jenkins and Android emulators, the idea of getting it working with a complicated vagrant setup is scary. Props all around! ~abel intrigeri: > Hi, > > bertagaz and I have just spent quite some time together working on our > Jenkins setup. > > Tails core developers can now push stable, testing, devel and > experimental branches to `gitol...@git.puppet.tails.boum.org:tails'. > Whenever they do this, an ISO image is built on builder.lizard. > The product of this build is kept there for a while. > > Along the way, we have patched vagrant/provision/assets/build-tails to > make it support our Jenkins build setup too. The changes > (feature/jenkins-compatible-build-script) were merged into stable, > testing, devel and experimental. Vagrant users, please verify that the > script still works for you. > > Next steps in terms of what's visible externally: > > * publish build products on http://nightly.tails.boum.org/ > > * automate mirroring process from our master Git repository to the > clone on lizard, so that we don't have to push to a special remote > > * automatically build Debian packages for our custom programs > > See the roadmap for details: > https://tails.boum.org/todo/automated_builds_and_tests/#index3h1 > > Cheers, > ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] [tor-talk] secure and simple network time (hack)
I don't really understand your reservation about this project. It's reasonable to want authenticated time to a non-webserver of ones choice. Depending on your environment, tlsdate is complementary to the various other programs. You can (and will) use whatever you decide fits your needs, but please don't disparage a valid project because it segfaults "after a while". It's a work-in-progress, better to contribute useful information than complain. On Fri, Apr 12, 2013 at 02:43:13PM +0300, Maxim Kammerer wrote: > On Fri, Jul 20, 2012 at 3:07 AM, Jacob Appelbaum wrote: > > Allow me to be very explicit: it is harder to parse an HTTP Date header > > than properly than casting a 32bit integer and flipping their order. The > > attack surface is very small and easy to audit. > > Just discovered that tlsdated in tlsdate-0.0.6 is dying with a > segmentation fault after a while. Not surprised after seeing the code > — my experimentation with this gimmick is finally over. Turns out that > “throw something together and wait for patches” is not a sound > development approach. > > -- > Maxim Kammerer > Liberté Linux: http://dee.su/liberte > ___ > tor-talk mailing list > tor-t...@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Tails Jenkins setup: present and future
On Fri, Apr 12, 2013 at 04:10:08PM +, Abel Luck wrote: > Amazing! > > As someone whose grappling with Jenkins and Android emulators, the idea > of getting it working with a complicated vagrant setup is scary. We don't really use vagrant for the jenkins build. We do explain to people who wants to build Tails to use our vagrant scripts though, as in https://tails.boum.org/contribute/build/ In jenkins, we use a kvm guest as build slave. As a lot of bricks can change the build result, it's better to use the same tools as much as possible everywhere. So we just adapted the script we provide for our vagrant build so that it also works for our jenkins builds. > Props all around! Thanks! bert. ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] manual usb installation for mac
On 12/04/13 16:12, intrigeri wrote: > sajol...@pimienta.org wrote (12 Apr 2013 13:28:36 GMT) : >> If you're fine with that I'll merge it into master, unfuzz what I can in >> the translations, and notify the translators. > > Please go ahead :) Done. See the result on: https://tails.boum.org/doc/first_steps/manual_usb_installation/mac/ But we receive a few more comments. We were told that the copy (cat [tails.iso] > [device] && sync) only works while being root. Could that make sense on some version of Mac OS X? How shall we correct the instruction to be root? signature.asc Description: OpenPGP digital signature ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
[Tails-dev] new instructions for manual USB installation for Mac, and Linux updated
Hi translators, The instructions for manual USB installation for Mac are back! See https://tails.boum.org/doc/first_steps/manual_usb_installation/mac/ Feel free to translate them. While we were at it we also did some changes to the instructions for Linux so you could have a look at the fuzzy string in there as well, and review my commit 3f537b9. signature.asc Description: OpenPGP digital signature ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
Re: [Tails-dev] Tails Jenkins setup: present and future
Sounds great. intrigeri: > Tails core developers can now push stable, testing, devel and > experimental branches to `gitol...@git.puppet.tails.boum.org:tails'. > Whenever they do this, an ISO image is built on builder.lizard. > The product of this build is kept there for a while. While I am not a core developer but I could imagine to contribute some patches. Building requires setting a build environment, takes a lot space and a long time. Could I push my branch somewhere and you initiate the build? ___ tails-dev mailing list tails-dev@boum.org https://mailman.boum.org/listinfo/tails-dev
