Hi,
It seems as if tbb-dev(a)lists.torproject.org is the list which
would be more appropriate.
If the 7 days without a reaction are simply due to the holidays in some countries,
it's my mistake. If you need internal discussion about this to respond
appropriately, let me know that you are reviewing this message at all.
I have no expectation for "neoliberal optimized" reply times.
Thanks.
ng0 transcribed 7.9K bytes:
> Hi folks,
>
> as your trademarks team / person suggested to me I get in touch with the
> dev team of torproject. While I'm more involved in GNUnet, I work at the
> intersection of projects. Currently this means I'm involved in system
> integration. At Guix we are interested in working closer with projects
> like tor, TAILS, Whonix and the like. Porting torbrowser is not only in
> the interest of the Guix community but also in the interest of Wonix who
> recently expressed interest in selectively using Guix for their work.
> For me as maintainer of the system (in development) pragmaOS it also
> means that we can decide between icecat OR torless torbrowser for
> proxied GNUnet connections.
>
> I'm interested in your response to the actions listed below and wether
> you think this will still qualify as torbrowser or what other option you
> propose for us at Guix to use. "Option" here means that I am not sure
> what other graphical theme you have for versions of the browser which do
> not use the trademark when they can (logically) also not use the firefox
> trademarks.
> I would reflect in the description of the package that it is not
> torbrowser but a reconstruction of the way torbrowser is build, tracking
> upstream as closely as possible while removing (list of features which
> were removed goes here).
> This can be compared to what the inoffical Gentoo maintainer does in the
> .ebuild file here:
> https://data.gpo.zugaina.org/torbrowser/www-client/torbrowser/
>
> My request here is just in the position as a contributor to Guix, not
> for pragmatique (the project which works on pragmaOS etc), Whonix,
> GNUnet or any other project I mentioned before.
>
> Thanks in advance. Now the content I've been talking about:
>
> It looks like the changes I need to make to torbrowser are not so
> grave at all. Someone pointed me to the gnu-linux-libre(a)nongnu.org list
> to reach out to other FSDG systems.
> The thread can be reviewed here:
> https://lists.nongnu.org/archive/html/gnu-linux-libre/2017-03/msg00002.html
>
> Basically:
>
> I will need to discourage Mozilla leftovers:
> - the mozilla addon service will be overwritten, in other words:
> Where you would find https://addons.mozilla.org/ at "Preferences > AddOns"
> it will be replaced by the thing Icecat points to. Longterm plan is
> to offer firefox extensions native through "guix package -i
> youraddonnamehere".
>
> Privacy / Tracking reasons:
> - Firefox "Sync" will be disabled.
> - Google will be removed from the search plugins if I understood the
> procedure correctly (at least it is not in Icecat)
>
> A question directly for torbrowser team:
> - about:license does not list licenses the torbrowser project uses, only
> firefox. Why?
>
> DRM
> - Luke from parabola mentioned that drm has been enabled in recent
> versions of torbrowser. This needs to be removed aswell.
> https://git.parabola.nu/abslibre.git/tree/libre/iceweasel/vendor.js#n23
> https://git.parabola.nu/abslibre.git/tree/libre/iceweasel/mozconfig#n39
> https://gitweb.torproject.org/tor-browser.git/tree/browser/app/profile/fire…
>
> ng0 transcribed 3.4K bytes:
> > bancfc(a)openmailbox.org transcribed 1.9K bytes:
> > > There is a serious Tor Browser packaging effort [3][4] being done by ng0
> > > (GNUnet dev) for the GNU Guix [0] package manager. GNU Guix supports
> >
> > Eh, now that the cat is out of the bag (cat's don't belong into bags
> > anyway), I think I have to do this now and not on my own conditions.
> >
> > Hi!
> >
> > As I told bancfc somewhere else, I've had a short contact with the
> > trademarks team of torproject. I will get back to you when someone was
> > able to identify issues in torbrowser which might lead to modifications
> > of torbrowser (for more details I just hope trademarks(a)tp.o can
> > communicate it to you) because all packaged software which is included
> > in upstream of Guix (master) must follow the GNU Free System
> > Distribution Guidelines.
> > I hope that I have to make as little modifications as possible as I
> > I am aware that the fingerprint of the browser could change depending on
> > the kind of changes.
> >
> > I hope to get back to this task in about 3 weeks, right now I'm busy
> > with getting more documentation done for another project.
> >
> > > transactional upgrades and roll-backs, unprivileged package management,
> > > per-user profiles and most importantly reproducible builds. I have checked
> > > with Guix's upstream and they are working on making a binary mirror
> > > available over a Tor Hidden Service. [2] Also planned is resilience [2] to
> > > the attack outlined in the TUF threat model. [1]
> > >
> > > Back to the topic of Tor Browser packaging. While there are good reasons for
> > > Debian's pakaging policies they make packaging of fast evolving software
> > > (and especially with TBB's reliance on a opaque binary VM for builds)
> > > impractial. Both we and Micah have been doing a good effort to automate
> > > downloading and validating TBB but I still believe its a maintenance burden
> > > and Guix may be a way out of that for Linux distros in general.
> > >
> > > What are your thoughts on this?
> > >
> > >
> > >
> > >
> > >
> > > ***
> > >
> > > [0] https://www.gnu.org/software/guix/
> > > [1] https://github.com/theupdateframework/tuf/blob/develop/SECURITY.md
> > > [2] https://lists.gnu.org/archive/html/guix-devel/2017-03/msg00192.html
> > > [3] https://lists.gnu.org/archive/html/guix-devel/2017-03/msg00189.html
> > > [4] https://lists.gnu.org/archive/html/guix-devel/2017-03/msg00149.html
> > > _______________________________________________
> > > tor-dev mailing list
> > > tor-dev(a)lists.torproject.org
> > > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
> > _______________________________________________
> > tor-dev mailing list
> > tor-dev(a)lists.torproject.org
> > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
>
> --
> PGP and more: https://people.pragmatique.xyz/ng0/
> _______________________________________________
> tor-dev mailing list
> tor-dev(a)lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev
--
PGP and more: https://people.pragmatique.xyz/ng0/
Hello TB team!
I created a pad for us to create agenda and share information folks
should review before Rome:
https://storm.torproject.org/shared/2RXUuAa_G4_GNy5yHFt8gjFqOv2wAJeq8-_0mQm…
This pad ^^ is for all the meetings on March 11th.
I merged UX sync with Roadmap because:
1. I think most of the conversation is coordination of work (when
Antonela needs to be done, when dev starts etc)
2. This gives 2 hrs of hanging out and talking roadmap; so there is no
rush and if it ends earlier - the better :)
Mobile! I added a big chunk of the language used in the proposal to
describe the activities to help guide you on the discussion related to
what is the final product for this project.
The timeline is just a guide for you, if you want to change it, you can
do it. Is better to change and have things reflect reality. Also, use
the time you think you need to get the work done. We will ask for an
extension to sponsor8 contract, so this will help me know how long do
you need it to be.
Desktop! :) I think coordination with Antonela and Mobile is good for
all the UI changes coming up (work Antonela is doing under OTF grant).
We sent a SOI to DRL asking money for TB team, there is a link in the
pad to it. But is nothing crazy, just keeping up with Mozilla releases
and implement Anto's work.
I left agenda for meetings with Mozilla open - we should share with
folks so it can be populated before Rome.
I also left the questions to answer when doing the retrospective, you
can reflect on it ;) I leave it up to the team if folks want to fill it
up before Rome or after Rome.
One less thing, Antonela will be with yall during the roadmap meeting. I
will have to split and be with network team roadmap meeting hehe :)
Let me know if you have any questions!
isabela