Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Log about:transparancy to console/file #71

Open
da2x opened this issue Jan 30, 2020 · 6 comments
Open

Log about:transparancy to console/file #71

da2x opened this issue Jan 30, 2020 · 6 comments

Comments

@da2x
Copy link

da2x commented Jan 30, 2020

Hi, can I somehow output a log of what goes on in about:transparency? There are delays before activity shows up, and things disappear before I get a chance to look at it.

@sammacbeth
Copy link
Collaborator

Hi,

The transparency page just shows a summary of outgoing requests from the browser. Depending on how much detail you want, you can also just monitor the HTTP traffic directly.

The easiest way to do this is via the extension debugger: visit about:devtools-toolbox?type=extension&id=cliqz%40cliqz.com to open a browser debugger for the browser-core extension, then go to the 'Network tab'. There you can analyse all outgoing requests from the extension, just as with a web page.

Screenshot 2020-01-30 at 09 50 27

From the dev tools you can export to HAR format for further analysis.

@da2x
Copy link
Author

da2x commented Jan 30, 2020

I did have a look there. However, all the data in the network debugger is encrypted. Not just HTTPS encapsulation — which the network debugger handles — but the payload is encrypted separately. This behavior matches what is described in Cliqz’s browser privacy policy.

screenshot

@sammacbeth
Copy link
Collaborator

Ah, true. For these messages, I think @philipp-classen may be able to advise on how to see the original content on these messages.

I'll also take this issue on-board as a feature request for an 'audit' mode for exporting all communicate with Cliqz' backend. The current dashboard is somewhat limited.

@da2x
Copy link
Author

da2x commented Jan 31, 2020

I'll also take this issue on-board as a feature request for an 'audit' mode for exporting all communicate with Cliqz' backend.

Logging to a file or stdout when an environmental variable is set would suffice. Or logging to the browser console while the about:transparancy is open.

The current dashboard is somewhat limited.

Displaying the last 10 minutes of data instead of the single last data point would be an enormous improvement. Maybe show the last by default but with an expander toggle to show last ten minutes? Instructions on how to log to a file would also suffice.

@philipp-classen
Copy link

@da2x You can make log outputs visible to print the unencrypted messages before they are sent. The steps are described in our blog post on Human Web (at the end):

https://0x65.dev/blog/2019-12-03/human-web-collecting-data-in-a-socially-responsible-manner.html#fn10

There is also a pref, which you can flip to turn off encryption at all. However, that means the proxy can also see (or could modify) your traffic, so reserve that option only for testing.

@Krahe65
Copy link

Krahe65 commented Feb 1, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants