[Tails-dev] Please split tickets

[alan]

Hi,

If you are the main author of the following big tickets, please consider
splitting them into smaller tickets or state that you will not do it and
that somebody else should volonteer.

The goal is to be able to close the main ticket and to have a cleaner
view of the remaining tasks.

The tickets are:

https://tails.boum.org/todo/windows_theme/
https://tails.boum.org/todo/build_with_vagrant/

Thanks in advance,

Cheers,


-- 


pgp9AbplPJG1H.pgp
Description: PGP signature
___
tails-dev mailing list
tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev

Re: [Tails-dev] Please review bugfix/default_search_engines

[Ague Mill]

On Thu, Sep 27, 2012 at 10:27:34AM +0200, intrigeri wrote:
> Ague Mill wrote (26 Sep 2012 10:43:31 GMT) :
> > Do you have any idea of how to do it better?
> 
> > The only one that comes up to my mind is that we move all search
> > plugins somewhere else in the chroot tree and use a local hook to
> > add links in directories corresponding to given the installed
> > localization package set. It feels unnecessarily complicated.
> 
> I agree it is a bit complicated, but I disagree on the "unnecessarily"
> part: I think it's the only way to fix this bug in a robust way, that
> is, to avoid seeing this bug re-appear, without us noticing, as soon
> as the list of iceweasel localization packages changes (e.g. if fr_BE
> appears, or if es_MX disappears). We don't want to test every language
> setting at release time for such regressions.

Done. Have a look at commit d3ebdba5.
 
> >> >   f9d73a5 Be consistent when giving a locale to check.torproject.org
> >> 
> >> OK, great. (FTR, the previous setting made sense when our syslinux
> >> menu allowed to pick "Portuguese", and that's all -- considering there
> >> are many more Portuguese speakers in Brasil than in Portugal.)
> >> 
> >> I have a feeling that this commit is too much or too little, and
> >> causes a tiny regression for Brasilian users -- while we're at it, we
> >> should add support for pt-BR in our branding extension.
> 
> > Yes, that'd be the way to go.
> 
> Added to the branch, then (commit 5ba8642).

That did not work without another changes (commit 966f639).

-- 
Ague


pgpY9dkqtH4hM.pgp
Description: PGP signature
___
tails-dev mailing list
tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev

Re: [Tails-dev] Improvement of the shutdown sequence

[Ague Mill]

On Tue, Sep 25, 2012 at 11:04:58AM +0200, intrigeri wrote:
> Ague Mill wrote (24 Sep 2012 16:03:58 GMT) :
> > I'd be happy to get reviews of what is in feature/shutdown_cleanup.
> 
> Static review: fine with me, but now that we have merged
> feature/catch_errors_in_hooks, you want to add a "set -e" in
> config/chroot_local-hooks/52-update-rc.d. That's not much, but it
> still needs to be done and tested.

Merging devel back took care of it.

> Initial test works fine, but I skipped the emergency shutdown test.
> That one will be for the next (hopefully final) iteration :)

Emergency shutdown still works fine.

-- 
Ague


pgpggWXUgEPLw.pgp
Description: PGP signature
___
tails-dev mailing list
tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev

Re: [Tails-dev] Tails webbrowser homepage

[Ague Mill]

On Wed, Sep 26, 2012 at 07:44:48PM +0200, a...@boum.org wrote:
> So, we might want to use the Tails website as the iceweasel homepage,
> so that users know about it and find how to get in touch, report bugs,
> etc. (a bookmark to  has been added in
> the devel branch (commit 89d7561) to ease the transition).
> 
> Another reason to switch homepage to something else (a light
> check.torproject.org version, perhaps?) is that [[the current one is
> not discreet enough|bugs/Congratulations_notice.]]. The Tails website
> is not substantially more discreet.
> 
> > We started to discuss this, and the most up-to-date proposal would
> > be to point the homepage to our online website's "News" page, that
> > would e.g. announce new release candidates to test etc.
> 
> However, no decision have been reached now.
> 
> Thoughts?

I am still in favor of moveing to  or
another compound page which would highlight a few recent news item and
the documentation.

-- 
Ague


pgpA5CDTSGS2e.pgp
Description: PGP signature
___
tails-dev mailing list
tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev

Re: [Tails-dev] Download manager

[Ague Mill]

On Wed, Sep 26, 2012 at 07:44:20PM +0200, a...@boum.org wrote:
> https://tails.boum.org/todo/include_download_manager/
> -
> 
> As mentioned on the forum in
> [[/forum/using_DownThemAll___40__iceweasle_firefox_addon__41__]], it
> might be useful to include a download managar in Tails.
> 
> A usecase could be to try to download a big file across separate working
> sessions.
> 
> If so, [uget](http://urlget.sourceforge.net/) could be a good candidate.
> 
> [[!tag todo/discuss]]

uget is in Debian. I don't think such tool is needed in the default set
of software. People can always install it through APT. We could include
a default configuration that enables SOCKS proxying. I won't work on it
though.

-- 
Ague


pgpqWRhlLaCoX.pgp
Description: PGP signature
___
tails-dev mailing list
tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev

Re: [Tails-dev] Tails: pcmcia / firewire / etc.

[Ague Mill]

On Wed, Sep 26, 2012 at 07:44:34PM +0200, a...@boum.org wrote:
> Issue: 32bit PCMCIA gets DMA. It is thus usable by an adversary for
> external bus memory forensics on a running Tails.
> 
> Question: we now have to discuss what usability vs.
> security balance we want.
> 
> Ideas:
> 
> * If a firewire card was inserted into the slot and the bus is active,
>   pop up a dialog and ask "hey, you want to use firewire/etc.?"

I don't know how this would be possible without serious kernel hacking.

> * disable these buses by default, allow opt-in through tails-greeter
>   to enable
> * ask that users assert they want to use this or that bus, and make
>   the assertion bind to a single device, rather than all devices
>   blindly
> * de-activate PCMCIA and ExpressCard on systems that don't have any
>   PCMCIA or ExpressCard devices after running for 5 minutes. This is
>   going to byte some users, but probably only the first time.

I still prefer the later.

-- 
Ague


pgpi8mXnZmBpw.pgp
Description: PGP signature
___
tails-dev mailing list
tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev

Re: [Tails-dev] Shipping a 686-pae kernel

[Ague Mill]

On Thu, Sep 27, 2012 at 11:57:06AM +0200, intrigeri wrote:
> anonym wrote (27 Sep 2012 09:38:32 GMT) :
> > This was in Tails built from feature/multikernel.
> 
> Thank you. I updated the ticket accordingly. So, next step is: somehow
> fix our USB installer vs. the 686-pae kernel. I'm not committing to do
> it any time soon.

After some gdb lifting, I got a stack trace mentioning
`_dbus_watch_invalidate`. This lead me to find this pretty old blog post
 mentioning
that these stack traces were usually because of locking issues. It also
mentions that asking DBus to properly handle multiple threads is as
simple as running `dbus_thread_init_default()`


Unfortunately, while it looks fairly easy to do from Python when using
GLib, according to the answers on this page
,
I have not been able to find a way to easily do something similar for
the Python DBus Qt bindings.

So my hack have been to add a call to `dbus_thread_init_default()` in
the initialization of the Python `dbus` module. And it looks like it
solve the issue. I have not been able to get the installer to crash
after installing the modified `python-dbus` package. From what I can
read from the documentation, except a performance hit, there should be
no other downsides to it.

The binary `python-dbus` package is fairly small (226 kB) and at this
time, it's a patch I feel we can carry on.

It's far from ideal, but it looks like there is very few users of the
Python Qt DBus binding. And our installer is hackish already... which
unfortunately tend to lead to more hacks. :(

What's your opinion? Should I proceed in adding a custom `python-dbus`
to the multikernel branch?

-- 
Ague


pgpiUejoin6pE.pgp
Description: PGP signature
___
tails-dev mailing list
tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev