Re: [Tails-dev] stats on upgrade time

2016-02-01 Thread intrigeri
Spencer wrote (01 Feb 2016 18:02:18 GMT) :
> I must know what is being requested, sent, how, and why. Is there 
> documentation on
> this [I couldn't quickly find any] or should I capture a VM session?

In general, our design doc is the best entry point to understand how
Tails works behind the hood:

https://tails.boum.org/contribute/design/incremental_upgrades/
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.


[Tails-dev] stats on upgrade time

2016-02-01 Thread Spencer

Hi,



intrigeri:
our design doc



Thanks (:

Wordlife,
Spencer



___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.


Re: [Tails-dev] Cannot install Tor Browser in Tails 2.0 build

2016-02-01 Thread ceyx

intrigeri:


ceyx wrote (01 Feb 2016 16:48:27 GMT) :
Git branch is stable. The build is performed on Wheezy running within 
VirtualBox,

meeting the dependencies as described here:
https://tails.boum.org/contribute/build/#index3h1


Are you using Vagrant?

If not, did you configure the build system to use a HTTP proxy? How 
exactly?


No, it's the manual build and I did not configure a proxy.
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.


Re: [Tails-dev] Cannot install Tor Browser in Tails 2.0 build

2016-02-01 Thread intrigeri
ceyx wrote (01 Feb 2016 16:48:27 GMT) :
> Git branch is stable. The build is performed on Wheezy running within 
> VirtualBox,
> meeting the dependencies as described here:
> https://tails.boum.org/contribute/build/#index3h1

Are you using Vagrant?

If not, did you configure the build system to use a HTTP proxy? How exactly?

Cheers,
-- 
intrigeri
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.


Re: [Tails-dev] Cannot install Tor Browser in Tails 2.0 build

2016-02-01 Thread ceyx

Spencer:


ceyx:
some minor customizations (i.e.,
some files in /etc/skel/).



Will you share some details about your use case as it pertains to
these customizations?

This will help with usability (:


The customer needs some of his preferred IM settings in $HOME/.purple/ . 
That's about it.

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.


[Tails-dev] Cannot install Tor Browser in Tails 2.0 build

2016-02-01 Thread ceyx

Hello,

First, thank you all for bringing the world Tails.

My question concerns the manual build of Tails 2.0. My builds were 
successful up to 1.8.2 and now they break, as the Tor Browser cannot be 
fetched due to a DNS error in the chrooted environment.


Install the Tor Browser
Fetching 
http://torbrowser-archive.tails.boum.org/5.5//tor-browser-linux32-5.5_ar.tar.xz 
...
  % Total% Received % Xferd  Average Speed   TimeTime Time  
Current
 Dload  Upload   Total   SpentLeft  
Speed
  0 00 00 0  0  0 --:--:-- --:--:-- --:--:-- 
0curl: (6) Could not resolve host: torbrowser-archive.tails.boum.org
E: config/chroot_local-hooks/10-tbb failed (exit non-zero). You should 
check for errors.

P: Begin unmounting filesystems...

real9m1.158s
user3m37.662s
sys 1m35.506s
+ RET=1
+ '[' -e binary.iso ']'
+ fatal 'lb build failed (1).'
+ echo 'lb build failed (1).'
lb build failed (1).
+ exit 1
+ kill -9 12774

The http_proxy variable turns out to be empty at this point. The URL is 
perfectly accessible from the build machine. When I replace it with an 
IP address (198.252.153.59) the build breaks on a SHA256 error.


Git branch is stable. The build is performed on Wheezy running within 
VirtualBox, meeting the dependencies as described here: 
https://tails.boum.org/contribute/build/#index3h1


What is going wrong here? I'm probably overlooking something obvious. 
Any hint that points me in the right direction is appreciated.


Best regards,

Ceyx

PS The rationale behind our build are some minor customizations (i.e., 
some files in /etc/skel/).

___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.


[Tails-dev] Migrate Tail's browser AdBlock Plus to uBlock Origin

2016-02-01 Thread Spencer

Hi,



random_u...@airpost.net:
the arguments against including an ad-blocker



Are not thought out or are intentional for reasons not relevant to 
security/anonymity.




best interests



Would lead us to a blocker at the exits, as all of the data still gets 
sent by the destination and increases latency.




indistinguishable fingerprints



Seems limited and fights against the real traffic patterns of the 
internet.


Wordlife,
Spencer



___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.


Re: [Tails-dev] ebuild for tails-installer

2016-02-01 Thread sajolida
Miguel Angel Marco Buzunariz:
> I have uploaded the ebuild to 
> https://github.com/miguelmarco/tails-installer-ebuild
> 
> If someone has access to a gentoo box, please test it.
> 
> If furthermore someone maintains a gentoo overlay, or any other place were it 
> makes sense to offer an ebuild, please feel free to include it.

Hi Miguel,

I never used Gentoo myself so I won't be able to test this.

But I wrote the new set of installation instructions [1] and I wonder
when and how we should document tails-installer for Gentoo in there.

So, what would be the process for the official inclusion of
tails-installer in Gentoo? What needs to happen before a regular Gentoo
user can use your work?

Once this happen, I'd like to get some basic instructions so I can maybe
test this in a Gentoo live CD and then I'll propose something to
document this in [1].

[1]: https://tails.boum.org/install/
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.


[Tails-dev] Cannot install Tor Browser in Tails 2.0 build

2016-02-01 Thread Spencer

Hi,



ceyx:
some minor customizations (i.e.,
some files in /etc/skel/).



Will you share some details about your use case as it pertains to these 
customizations?


This will help with usability (:

Wordlife,
Spencer



___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.


[Tails-dev] ebuild for tails-installer

2016-02-01 Thread mmarco
In gentoo, there are essentially three ways to install a package through the 
package manager:

1) Packages that are included in the main portage tree (that would be the 
official packages of the distro)
2) Packages included in one of the layman overlays (would be like thirthd 
party repos, but can be easily managed with a tool provided by the distro).
3) Packages in the local overlay of the user (would be the equivalent of 
downloading a .deb package and install it manually).

I have no contact with the official gentoo team, so can't do much about option 
1). However, Austin English, who also showed interest in this, might help with 
that. AFAIK, he is on hollyday now. Maybe when he comes back he could help 
with that. If this get fixed, gentoo users that want to install tails-installer 
should just use the standard way:

$ emerge tails-installer

and that would be it (well, maybe some work should be done to allow the 
installation of a package that is not marked as fully stable, but that is the 
kind of things that a typical gentoo user is used to deal with)

About option 2), I also don't maintain any of those semioficial overlays. 
However, one of those overlays is focused preciselly on torbrowser and related 
packages. I have already sent a pull request to include my ebuild in it. If it 
is merged, the installation would be almost as easy. Just install the layman 
tool in the usual way and then:

$ layman -a torbrowser
$ emerge tails-installer

Finally, until 1) and/or 2) become possible, a regular user can use a local 
overlay. In order to do so, (s)he should follow the following steps:

a) enable the local overlay by adding a line like 

PORTDIR_OVERLAY = "/usr/local/portage/"

to the file /etc/portage/make.conf

b) copy the directory tails-installer and its content inside of the directory 
/usr/local/portage/app-misc

c) run the usual "emerge tails-installer" command.

I hope this helps to clarify the general picture. If you need more details, I 
would be happy to provide them.


P.S. During the writing of the ebuild I noticed that there are several 
dependencies that are not listed in the README file. They are the following:

configobj
urlgrabber
python-distutils-extra
pygobject
pyparted
cdrtools
gptfdisk


best,

Miguel Marco






> Miguel Angel Marco Buzunariz:
> > I have uploaded the ebuild to
> > https://github.com/miguelmarco/tails-installer-ebuild
> > 
> > If someone has access to a gentoo box, please test it.
> > 
> > If furthermore someone maintains a gentoo overlay, or any other place were
> > it
> > makes sense to offer an ebuild, please feel free to include it.
> 
> Hi Miguel,
> 
> I never used Gentoo myself so I won't be able to test this.
> 
> But I wrote the new set of installation instructions [1] and I wonder
> when and how we should document tails-installer for Gentoo in there.
> 
> So, what would be the process for the official inclusion of
> tails-installer in Gentoo? What needs to happen before a regular Gentoo
> user can use your work?
> 
> Once this happen, I'd like to get some basic instructions so I can maybe
> test this in a Gentoo live CD and then I'll propose something to
> document this in [1].
> 
> [1]: https://tails.boum.org/install/

signature.asc
Description: This is a digitally signed message part.
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.

Re: [Tails-dev] Where are the developers? I thought this was supposed to be a support list

2016-02-01 Thread u
Hi,

vcc...@sigaint.org:
> Do the developers even give one shit about its users? [etc. etc.]

As a Free Software project based on a lot of volunteer work, we very
much welcome constructive criticism. However, this kind of email might
not get any answer. [If you want to understand why, I kindly refer you
to reading our Code of Conduct:
https://tails.boum.org/contribute/working_together/code_of_conduct/]

Our support channels are documented here:
https://tails.boum.org/support/index.en.html Subreddit is not one of
them. If you'd like to get help, please report bugs as described.
Sometimes answers take some time. I think that's because there are
humans behind machines, not robots.

Cheers!
u.
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.


[Tails-dev] stats on upgrade time

2016-02-01 Thread Spencer

Hi,



sajolida:
You cannot disable the security check for open security
issues or upgrades.



Not from within Tails?

Should I roll my own and adjust the relevant package content beforehand?



it's worth spending time on



I agree d: Knowledge provides value.

I must know what is being requested, sent, how, and why. Is there 
documentation on this [I couldn't quickly find any] or should I capture 
a VM session?




create a ticket.



Maybe.

Wordlife,
Spencer



___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to 
tails-dev-unsubscr...@boum.org.