Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
arti
arti
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 19
    • Issues 19
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Package Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • 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.

  • The Tor Project
  • Core
  • artiarti
  • Issues
  • #28

Closed
Open
Opened Oct 27, 2020 by Nick Mathewson@nickm🐙Owner4 of 5 tasks completed4/5 tasks

Basic path-generation logic

I should extend tor-netdir (or some related crate) to build plausible paths through the Tor network.

At the very least for this milestone I want

  • Distinct relays
  • Making sure we know enough relays
  • Avoiding relays in the same family
  • Choosing exits that do what we want
  • Weighting more or less correctly
Edited Dec 02, 2020 by Nick Mathewson
Assignee
Assign to
A1: minimal socksport
Milestone
A1: minimal socksport (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/core/arti#28