unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <contact.ng0@cryptolab.net>
To: dian_cecht@zoho.com
Cc: guix-devel@gnu.org
Subject: Re: torbrowser
Date: Mon, 6 Mar 2017 17:38:58 +0000	[thread overview]
Message-ID: <20170306173858.5k7xydt7eduqyc2q@abyayala> (raw)
In-Reply-To: <20170306080652.796452a2@khaalida>

On 17-03-06 08:06:52, dian_cecht@zoho.com wrote:
> On Mon, 6 Mar 2017 15:14:59 +0000
> ng0 <contact.ng0@cryptolab.net> wrote:
> > My idea is now to just reconstruct what torproject does, from the git
> > checkout of torbrowser and eventually later fix Guix specific
> > issues and fine tuning (freedom issues etc etc).
> 
> Would it be possible to grab the patches Torbrowser uses against
> Firefox and simply try to apply them to IceCat? I don't know exactly
> what version of FF Icecat and Torbrowser build off of, but if that
> could work it might make life a bit easier.
> 
> Alternativly, maybe applying the icecat patches to Torbrowser might
> work, too.
> 
> 

Not really. Icecat is just too old, and the firefox version torbrowser
is based on is not compatible with the one icecat uses. I would not want
the extra work to backport patches.

So far, I haven't investigated all possible ways, it seems too much work
to cherry-pick what torbrowser does to firefox. as they seem to maintain
all in the repository it could work out to just build from there. Their
release workflow (not automated but well documented) includes pulling in
from firefox, so there has to be firefox code in the repository.
The time and effort to base this on icecat is not worth it... unless
someone wants to start an icecat-torbrowser which *closely* tracks
torbrowser and does not become so unresponsive to bugs/issues like
icecat currently is.
And in both cases, the browser I assemble, and in the not-existing case
of a blend of torbrowser,I want to compare against upstream releases to
see how much we would differ and how much it'll affect fingerprinting
etc.
This difference will go into the description, as it can't be described
as a 1:1 port of torbrowser.

  reply	other threads:[~2017-03-06 16:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06 15:14 torbrowser ng0
2017-03-06 15:47 ` torbrowser Ludovic Courtès
2017-03-06 17:26   ` torbrowser ng0
2017-03-06 16:06 ` torbrowser dian_cecht
2017-03-06 17:38   ` ng0 [this message]
2018-03-07 12:46     ` torbrowser ng0
2018-03-07 15:32       ` torbrowser Christopher Lemmer Webber
2018-03-08  7:24         ` torbrowser Catonano
2018-03-08 12:11           ` torbrowser ng0

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170306173858.5k7xydt7eduqyc2q@abyayala \
    --to=contact.ng0@cryptolab.net \
    --cc=dian_cecht@zoho.com \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).