[Tails-dev] [patch, please review] generate Iceweasel profile at build time

2012-09-22 Thread Alessandro Grassi
Hi,
attached patch should generate Iceweasel profile on build time, rather than
run time. It is required for a "bookmarks" persistence preset (which I want
to implement soon), as explained in the todo ticket:

https://tails.boum.org/todo/persistence_preset_-_bookmarks/

First time I send a patch, I hope it's ok :-)

Alessandro


static-iceweasel-profile
Description: Binary data
___
tails-dev mailing list
tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev


Re: [Tails-dev] Using the http.debian.net redirector?

2012-09-22 Thread Ague Mill
On Fri, Sep 21, 2012 at 09:59:15PM +0200, intrigeri wrote:
> it looks like the http.debian.net redirector looks mature enough to be
> worth considering using it as the default APT repository in Tails
> images. It supports the main archive, as well as backports.
> 
> Rationale:
> 
>  * constantly use an APT mirror that's close from the exit node being
>used

I did some tests, with the same pros in my mind. But it seemed to me
that it was plagued by similar problems than 'cdn.debian.net':
sometimes, one circuit is created and goes to one mirror, and the one
just after goes to a different mirror. And one of those mirrors is more
up-to-date than the other, resulting in APT complaining about missing
files or mismatching checksums.

But that was just over an afternoon before switching back to
ftp.us.debian.org. I'll be happy to hear other experiences.

-- 
Ague


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


[Tails-dev] Using the http.debian.net redirector?

2012-09-22 Thread intrigeri
Hi,

it looks like the http.debian.net redirector looks mature enough to be
worth considering using it as the default APT repository in Tails
images. It supports the main archive, as well as backports.

Rationale:

 * constantly use an APT mirror that's close from the exit node being
   used
 * use the same mirror at build- and run- time
 * use a close mirror at build time
 * that's now the default in live-build 3.x

Description:

   The redirector uses the geo and network location of the user and
   the mirrors, the architecture of the requested files, IP address
   family, the availability and freshness of the mirrors, and a few
   other things. It is constantly improved.

Details: http://http.debian.net/

I'm starting to use it as a backend for my own apt-cacher-ng:
# cat http://http.debian.net/debian/ > /etc/apt-cacher-ng/backends_debian

I encourage you to do the same, and report back any issues.

Security/anonymity -wise, we should check how the mirror selection and
redirection works, and verify if it can be used to track a given Tails
user across circuit changes (in a worse way than the current setup,
I mean) or other such issues. Perhaps we'll just quickly realize it's
not worth the effort. We'll see.

(Meta: I intend to handle this as a funny, low-priority project,
no deadline involved, but feel free create a ticket if you see it
important enough to be tracked as part of our agenda, and want to
bring it to a quick resolution / is not forgotten / whatever.)

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