Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #19229

Closed (moved)
Open
Opened Jun 02, 2016 by cypherpunks@cypherpunks

Canary monitoring

Some websites put canaries into their Privacy Policy as a legal way to inform the users about gag orders. It is fine to have a browser extension checking for canaries and warn users if canary disappear.

If an extension discovers a valid canary, it caches the site as canaried. If a canary changes or disappears it informs the user. A DB of known canaries can be available as a subscription (like adblock one).

First it tries to discover a canary in the page. If it doesn't, it looks for meta or a element referring to ToS and privacy policy and looks for canaries there.

To discover a canary an extension searches in meta tags for it. If it finds a meta element with content having a canary it means it has a canary. This canary has the following format . The implementation must check the signature and pin public key.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#19229