Re: [Tails-dev] [Whonix-devel] Persistent Tor start in Tails vs location aware Tor entry guards (LATEG)
On 2016-02-06 23:14, intrigeri wrote:
Hi,
[can you please decide what mailing-list this discussion should happen
on, and then we can stop cross-posting over 4 mailing-list?]
[snip]
I'm not sure I understand the problem you mean to raise, though.
Can you please elaborate what problem you see if users do exactly this
("click through whatever hoops required to make the WiFi connect
again", which I agree is very likely)?
Thanks!
Cheers,
The problems in LATEG/AdvGoalTracking go deep enough that TPO is
investigating how to solve them in Tor's codebase:
https://lists.torproject.org/pipermail/tor-dev/2016-February/010364.html
A wider effort to think about usability of the user facing part of this
(is any at all) is good too.
___
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
Great Miguel! I'll work on getting it merged once I'm back and I finish my developer onboarding. On Feb 7, 2016 3:30 PM, "Miguel Angel Marco Buzunariz" wrote: > > Good news! > > Poncho merged my pull requests in his torbrowser overlay. He also improved my ebuild a bit. That means that option 2) of what I mentioned in my previous email should "just work". > > So now, a gentoo user that wants to get tails-installer just needs to do the following: > > first, install the layman tool to manage overlays (if it is not already installed): > > $ emerge layman > > then pull the torbrowser overlay (if it is not installed already): > > $ layman -a torbrowser > > finally, just the usual installation: > > $ emerge tails-installer > > Deppending on the user configuration, the system might complain about the package not being marked as stable. In that case, add a line like > > =app-misc/tails-installer-4.4.7 > > to the file /etc/portage/packages.keywords > (again, deppending on the user configuration, the emerge command itself could offer the option of doing this automatically). > > If you want to include this information in the web page, and need some further explanations, please contact me. > > However, I think roght now it would be better to wait and see if Austin English can manage to include the ebuild in the main portage tree, which would make the process even simpler. > > Best, > > Miguel Marco > > > > 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 > > ___ > 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 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] intrigeri vs. Tails Redmine
intrigeri: > anonym wrote (05 Feb 2016 13:02:57 GMT) : >> Could you please clarify what you mean here? Obviously it's not >> sustainable to rely on a single person (you) following all of Redmine, >> but in order to not have tickets be forgotten or go unnoticed, we need >> some processes and tools to deal with it instead. I assume this is what >> you are getting at, and that you already has some ideas for it. Please >> share! > > It's indeed a class of problems we'll need to solve. But no, I wasn't > getting at this. And I don't want to be the one who leads the effort > on this front. Understood. I'm personally in favor of testing having no complete tracking of Redmine for some time and advertising it. I think this will bring in a more healthy culture for regular contributors. Then if we realize this is really problematic (for example towards new tickets, new contributors mishandling metadata, etc.) then we can consider having a collective effort for tracking everything again. But I feel this would be better discussed at a summit maybe. > My point was rather about solving problems like "I would like to track > all changes made to tickets that are in the 'Test suite' category", > without anyone having to manually add me to the list of watchers. +1 ___ 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
Good news! Poncho merged my pull requests in his torbrowser overlay. He also improved my ebuild a bit. That means that option 2) of what I mentioned in my previous email should "just work". So now, a gentoo user that wants to get tails-installer just needs to do the following: first, install the layman tool to manage overlays (if it is not already installed): $ emerge layman then pull the torbrowser overlay (if it is not installed already): $ layman -a torbrowser finally, just the usual installation: $ emerge tails-installer Deppending on the user configuration, the system might complain about the package not being marked as stable. In that case, add a line like =app-misc/tails-installer-4.4.7 to the file /etc/portage/packages.keywords (again, deppending on the user configuration, the emerge command itself could offer the option of doing this automatically). If you want to include this information in the web page, and need some further explanations, please contact me. However, I think roght now it would be better to wait and see if Austin English can manage to include the ebuild in the main portage tree, which would make the process even simpler. Best, Miguel Marco > 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 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] Limiting the Amount of Software in Tails
Hi, Michael English wrote (06 Feb 2016 22:43:22 GMT) : > There are a few software packages installed in Tails from contrib and > non-free that concern me. > [...] > Could someone explain the reasoning for including these > software packages? See "3.9 Hardware support" in our design doc: https://tails.boum.org/contribute/design/ 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.
