Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • P purr-data
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 363
    • Issues 363
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 54
    • Merge requests 54
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Jonathan Wilkes
  • purr-data
  • Issues
  • #133

Closed
Open
Created Oct 11, 2016 by Jonathan Wilkes@jwilkesOwner

chromium phones home to google about stuff

nw.js binary occasionally shoots messages back to google servers for various purposes-- safe browsing blacklists, google apis, ipv6 pings, etc.

These need to be turned off at compile time. In the meantime, add the following to the manifest to keep these requests from leaving the local machine: "chromium-args": "--proxy-server=http://127.0.0.1"

For testing purposes, change it to --proxy-server=http://127.0.0.1:4321 and set a listener with netcat or something to log the outgoing requests for a Purr Data session.

Assignee
Assign to
Time tracking