Arch Linux

gcarq

Member

From: Austria

Registered: 2013-10-07

Posts: 40

Re: Inox Browser - yet another Chromium Privacy Spin-off

Hi,

I've updated the packages to 45.0.2454.93.
I also changed two and added two new patches. You can see the full changes on github.
Now I'm happy to say after a 24h traffic sniffing with mitmproxy there is no more data leakage compared to Chromium.

Last edited by gcarq (2015-09-21 18:41:25)

Perfect Gentleman

Member

Registered: 2012-10-25

Posts: 222

Re: Inox Browser - yet another Chromium Privacy Spin-off

applied new patches to 45.0.2454.99.
@gcarq, why don't you use chromium-lite packages in your pgkbuilds?

gcarq

Member

From: Austria

Registered: 2013-10-07

Posts: 40

Re: Inox Browser - yet another Chromium Privacy Spin-off

@Perfect Gentleman never heard of this package before, do you have a link? I can just find a suse package from 2011.

Perfect Gentleman

Member

Registered: 2012-10-25

Posts: 222

Re: Inox Browser - yet another Chromium Privacy Spin-off

@gcarq, just add "-lite" to the end of packahe name, it'll be like "chromium-45.0.2454.99-lite.tar.xz".
also, could you, please, move hide-"Sing-In-Chromium"-patch to separate file?

Last edited by Perfect Gentleman (2015-09-25 04:28:01)

gcarq

Member

From: Austria

Registered: 2013-10-07

Posts: 40

Re: Inox Browser - yet another Chromium Privacy Spin-off

@Perfect Gentleman, I don't think it is a good idea to name it a -lite package, because that could imply that some Google features are available which is not the case.
Sure I will add this to a sperate file asap.

cheers

Perfect Gentleman

Member

Registered: 2012-10-25

Posts: 222

Re: Inox Browser - yet another Chromium Privacy Spin-off

@gcarq,  i don't mean that you rename your packages, I'm about using chromium-xx.x.x.xx-lite.tar.xz as sources, they're just lighter than chromium-xx.x.xxxx.xx.tar.xz for about 30%.

gcarq

Member

From: Austria

Registered: 2013-10-07

Posts: 40

Re: Inox Browser - yet another Chromium Privacy Spin-off

@Perfect Gentleman, just checked your overlay, now I know what you mean :-)
Thanks I will use this on the next update.

PS: I'm looking for a second package maintainer if anyone has to much spare time.

Last edited by gcarq (2015-10-02 09:24:08)

Perfect Gentleman

Member

Registered: 2012-10-25

Posts: 222

Re: Inox Browser - yet another Chromium Privacy Spin-off

@gcarq, I won't be a maintainer as I use Gentoo, but I can help you with testing.

Shadowdodger

Member

Registered: 2015-10-16

Posts: 1

Re: Inox Browser - yet another Chromium Privacy Spin-off

Hello! I'm really impressed with this browser, but certain extensions won't work. Ublock Origin crashes every time and I just couldn't get it to work. How can I fix this?

gcarq

Member

From: Austria

Registered: 2013-10-07

Posts: 40

Re: Inox Browser - yet another Chromium Privacy Spin-off

Hi @Shadowdoger! I'm glad you like it. There exists a github issue for this bug and hopefully there wil land a fix soon.
AFAIK Chromium exposes the WebRTC API altough its disabled via the build flags. Until Google provides a proper fix you can manually remove the WebRTC check in uBlock.

All you have to do is  go to the extension directory (usually something like: ~/.config/inox/Default/Extensions/cjpalhdlnbpafiamejdnhcphjbkeiagm/) and find vapi-background.js.
In this file remove the following lines (starting at line 105 or something):

            case 'webrtcIPAddress':
                if ( typeof chrome.privacy.network.webRTCMultipleRoutesEnabled === 'object' ) {
                    try {
                        chrome.privacy.network.webRTCMultipleRoutesEnabled.set({
                            value: !!details[setting],
                            scope: 'regular'
                        });
                    } catch(ex) {
                        console.error(ex);
                    }
                }
                break;

If you reload the extension it should work as expected.

gcarq

Member

From: Austria

Registered: 2013-10-07

Posts: 40

Re: Inox Browser - yet another Chromium Privacy Spin-off

Hi @Shadowdodger! I'm glad you like it. There exists a github issue for this bug and hopefully there wil land a fix soon.
AFAIK Chromium exposes the WebRTC API altough its disabled via the build flags. Until Google provides a proper fix you can manually remove the WebRTC check in uBlock.

All you have to do is  go to the extension directory (usually something like: ~/.config/inox/Default/Extensions/cjpalhdlnbpafiamejdnhcphjbkeiagm/) and find vapi-background.js.
In this file remove the following lines (starting at line 105 or something):

            case 'webrtcIPAddress':
                if ( typeof chrome.privacy.network.webRTCMultipleRoutesEnabled === 'object' ) {
                    try {
                        chrome.privacy.network.webRTCMultipleRoutesEnabled.set({
                            value: !!details[setting],
                            scope: 'regular'
                        });
                    } catch(ex) {
                        console.error(ex);
                    }
                }
                break;

If you reload the extension it should work as expected.

Perfect Gentleman

Member

Registered: 2012-10-25

Posts: 222

Re: Inox Browser - yet another Chromium Privacy Spin-off

applied patches to Version 46.0.2490.80 (64-bit)

Last edited by Perfect Gentleman (2015-10-23 10:28:46)

Wilco

Member

Registered: 2008-11-09

Posts: 440

Re: Inox Browser - yet another Chromium Privacy Spin-off

Excellent work, much appreciated

Shadowdodger2

Member

Registered: 2015-11-05

Posts: 9

Re: Inox Browser - yet another Chromium Privacy Spin-off

Hey there! Your browser was working wonderfully, just until a few days ago. It just wouldn't start for whatever reason. This is the version that always worked for me: https://aur.archlinux.org/inox.git. It apparently got removed from the AUR, so I tried compiling this one from source (https://aur.archlinux.org/packages/inox/), but it didn't work. It also didn't work when I've tried to install it from the AUR. I successfully compiled it from source, but it doesn't start. What should I do? It's my favourite browser and I want to use it again.

Last edited by Shadowdodger2 (2015-11-05 11:07:28)

gcarq

Member

From: Austria

Registered: 2013-10-07

Posts: 40

Re: Inox Browser - yet another Chromium Privacy Spin-off

Hi,

I updated the packages to 46.0.2490.80.

@Perfect Gentleman, thanks for helping me out with testing. BTW I tried to use the chromium-lite package but it won't compile:

sed: can't read ./third_party/chromite/scripts/lddtree.py: No such file or directory
==> ERROR: A failure occurred in prepare().
    Aborting...

Do I need a additional build flag for this?

@Shadowdodger2, the frist link you provided is from the old AUR and is no longer maintained, the  2nd one should build fine now.

Last edited by gcarq (2015-11-06 15:07:45)

Shadowdodger2

Member

Registered: 2015-11-05

Posts: 9

Re: Inox Browser - yet another Chromium Privacy Spin-off

Unfortunately, I'm always getting the same error when installing it. It's this one:
IOError: [Errno 28] No space left on device
ERROR: A failrue occured in prepare ()
Aborting...
ERROR: Makepkg was unable to build inox.

null

Member

Registered: 2009-05-06

Posts: 398

Re: Inox Browser - yet another Chromium Privacy Spin-off

Where are you building your package? Is there still enough space for the build process? Do you have enough ram?

Shadowdodger2

Member

Registered: 2015-11-05

Posts: 9

Re: Inox Browser - yet another Chromium Privacy Spin-off

Uhh, I'm trying to install it from the AUR. I have 6 gigs of RAM, so I don't think that's the issue, though I'm not quite about the space for the build process. Where is it exactly and how can I check if I have enough space? As I've noticed, the only time I get the error is when trying to install Inox. It didn't happen with any other software as far as I remember.

respiranto

Member

Registered: 2015-05-15

Posts: 479

Website

Re: Inox Browser - yet another Chromium Privacy Spin-off

Uhh, I'm trying to install it from the AUR. I have 6 gigs of RAM, so I don't think that's the issue, though I'm not quite about the space for the build process. Where is it exactly and how can I check if I have enough space? As I've noticed, the only time I get the error is when trying to install Inox. It didn't happen with any other software as far as I remember.

If you don't know, where your package is built, you are most probably using an AUR helper.
Check it's documentation to see where it builds the packages by default.

Wilco

Member

Registered: 2008-11-09

Posts: 440

Re: Inox Browser - yet another Chromium Privacy Spin-off

You need a couple of free GB on your harddisk to compile chromium.

As for the Inox patchset, it greatly reduces Google calls, but not entirely. With Wireshark I still see lots of calls to:
tools.google.com
apis.google.com
fonts.googleapis.com
fonts.gstatic.com
and plenty other, especially on first or second run.

This is not a complaint btw, just something I've noticed

Perfect Gentleman

Member

Registered: 2012-10-25

Posts: 222

Re: Inox Browser - yet another Chromium Privacy Spin-off

@gcarq,
because ./third_party/chromite/scripts/lddtree.py is a link to non-exist file.
imo,

  find . -name '*.py' -exec sed -i -r 's|/usr/bin/python$|&2|g' {} +

is not needed

Last edited by Perfect Gentleman (2015-11-07 14:49:31)

Perfect Gentleman

Member

Registered: 2012-10-25

Posts: 222

Re: Inox Browser - yet another Chromium Privacy Spin-off

applied patches to Version 46.0.2490.86 (64-bit)

Perfect Gentleman

Member

Registered: 2012-10-25

Posts: 222

Re: Inox Browser - yet another Chromium Privacy Spin-off

@gcarq, Chromium 47 is out.

gcarq

Member

From: Austria

Registered: 2013-10-07

Posts: 40

Re: Inox Browser - yet another Chromium Privacy Spin-off

Updated to version 47.0.2526.73.
I also added three new patches:

• disable-first-run-behaviour.patch prevent calls mentioned by @Wilco.

• disable-new-avatar-menu.patch this is now a seperate patch because --disable-new-avatar-menu is gone.

• chromium-sandbox-pie.patch compiles sandbox with -fPIE.

Perfect Gentleman

Member

Registered: 2012-10-25

Posts: 222

Re: Inox Browser - yet another Chromium Privacy Spin-off

thanx, gcarq