Opened 4 years ago

Closed 2 years ago

#17262 closed defect (fixed)

Experimental simulation prototype for guard selection algorithm

Reported by: nickm Owned by: nickm
Priority: High Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: prop259, tor-guard, tor-guards-revamp
Cc: isis, brade, mcs, asn Actual Points:
Parent ID: Points: 3
Reviewer: Sponsor:

Description

This is an end-of-october deliverable. Let's take the results of #17261 and make them into a python prototype that we can run experiments on. Forcing us to be concrete in this way will help us get a better plan.

Child Tickets

Change History (32)

comment:1 Changed 4 years ago by nickm

Keywords: TorCoreTeam201510 added

comment:2 Changed 4 years ago by isis

Cc: isis added
Severity: Normal

comment:3 Changed 4 years ago by nickm

Dropped the start of some simulation code at https://github.com/nmathewson/guardsim . It is neither quite accurate nor quite enough, and I suspect it's not quite right either. Still it is a start.

comment:4 Changed 4 years ago by mcs

Cc: brade mcs added

comment:5 Changed 3 years ago by nickm

Priority: MediumHigh

comment:6 Changed 3 years ago by isis

Owner: set to isis
Status: newassigned

comment:7 Changed 3 years ago by isis

Status: assignedneeds_review

The latest code is in my develop branch. I think this is mostly done, as in "we could start writing the C implementation now".

comment:8 Changed 3 years ago by nickm

I've merged it to my master branch. As many folks as possible should start looking it over soon IMNSHO

comment:9 Changed 3 years ago by asn

Milestone: Tor: 0.2.8.x-finalTor: 0.2.???

Removing this from the 0.2.8.x milestone.

This is not a 0.2.8.x deliverable and it's not even a little-t-tor ticket. We are still not sure which guard algorithm to implement in Tor, and guardsim should help us with this.

comment:10 Changed 3 years ago by isabela

Sponsor: SponsorUSponsorU-must

comment:11 Changed 3 years ago by nickm

Keywords: TorCoreTeam201604 added; TorCoreTeam201510 removed
Milestone: Tor: 0.2.???Tor: 0.2.9.x-final
Status: needs_reviewneeds_revision

We need this prototype done in order to be able to build the algorithm in Tor.

comment:12 Changed 3 years ago by nickm

Keywords: prop259 added

These are all prop259-related.

comment:13 Changed 3 years ago by mikeperry

Keywords: tor-guard added

comment:14 Changed 3 years ago by nickm

Keywords: tor-guards-revamp added

comment:15 Changed 3 years ago by asn

Owner: changed from isis to asn
Status: needs_revisionassigned

Changing to May tag, and assigning myself as the owner because that's probably closer to the truth than isis.

comment:16 Changed 3 years ago by asn

Keywords: TorCoreTeam201605 added; TorCoreTeam201604 removed
Status: assignedneeds_revision

comment:17 in reply to:  15 Changed 3 years ago by isis

Replying to asn:

Changing to May tag, and assigning myself as the owner because that's probably closer to the truth than isis.


Thanks! I still have it on my list of things to do to review the implementation the ThoughtWorks team was working on, if you still want help with that.

comment:18 Changed 3 years ago by isabela

Points: medium3

comment:19 Changed 3 years ago by asn

Keywords: TorCoreTeam201606 added; TorCoreTeam201605 removed

comment:20 Changed 3 years ago by asn

FWIW, this is the simulation prototype of prop259 in python by the thoughtworks team:
https://github.com/twstrike/tor_guardsim

comment:21 Changed 3 years ago by asn

Summary: Experimental prototype for guard selection algorithmExperimental simulation prototype for guard selection algorithm

comment:22 Changed 3 years ago by asn

Cc: asn added

comment:23 Changed 3 years ago by nickm

Keywords: nickm-deferred-20161005 added
Milestone: Tor: 0.2.9.x-finalTor: 0.3.0.x-final

Deferring big/risky-feature things (even the ones I really love!) to 0.3.0. Please argue if I'm wrong.

comment:24 Changed 3 years ago by asn

Owner: asn deleted
Status: needs_revisionassigned

Removed myself from owner as it's no longer clear whether we will simulate prop271, and in any case I doubt I'm going to do the simulation here. Feel free to assign it someone else.

Last edited 3 years ago by asn (previous) (diff)

comment:25 Changed 3 years ago by dgoulet

Keywords: triage-out-030-201612 added
Milestone: Tor: 0.3.0.x-finalTor: 0.3.1.x-final

Triaged out on December 2016 from 030 to 031.

comment:26 Changed 2 years ago by nickm

Sponsor: SponsorU-must

Clear sponsorS and sponsorU from open tickets in 0.3.1

comment:27 Changed 2 years ago by nickm

Milestone: Tor: 0.3.1.x-finalTor: unspecified
Owner: set to nickm

Move "assigned" items with no owner from 031 to unspecified

comment:28 Changed 2 years ago by nickm

Keywords: nickm-deferred-20161005 removed

comment:29 Changed 2 years ago by nickm

Keywords: triage-out-030-201612 removed

comment:30 Changed 2 years ago by nickm

Keywords: TorCoreTeam201606 removed

comment:31 Changed 2 years ago by nickm

Keywords: 028-triage removed

comment:32 Changed 2 years ago by nickm

Resolution: fixed
Status: assignedclosed

We did this as part of the prop271 work. We can and should update it, but that's a separte issue.

Note: See TracTickets for help on using tickets.