Opened 3 years ago

Last modified 4 months ago

#12456 assigned defect

Implement prop229 ("Further SOCKS5 extensions")

Reported by: nickm Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Keywords: tor-client, 027-triaged-1-out, term-project-ideas, tor-03-unspecified-201612
Cc: yawning, lists@… Actual Points:
Parent ID: Points: medium
Reviewer: Sponsor:

Description

In proposal 229, Yawning describes a few improvements to the SOCKS5 protocol for better use by Tor-aware tools.

We should implement that.

(I'm putting this ticket in 0.2.??? since I don't think I'll be able to do it on an 0.2.6 timeframe, but if somebody else does the coding, it might be able to get done sooner.)

Child Tickets

Change History (16)

comment:1 Changed 3 years ago by yawning

  • Cc yawning added

comment:2 Changed 3 years ago by naif

  • Cc lists@… added

comment:3 Changed 3 years ago by nickm

Noting here that there are trunnel implementations of the record formats in the examples directory of trunnel.

comment:4 follow-up: Changed 2 years ago by naif

Has this been implemented like per #6031 ticket or like https://lists.torproject.org/pipermail/tor-dev/2014-February/006340.html ?

As i expect we will need to update Tor2web code?

comment:5 in reply to: ↑ 4 Changed 2 years ago by yawning

Replying to naif:

Has this been implemented like per #6031 ticket or like https://lists.torproject.org/pipermail/tor-dev/2014-February/006340.html ?

No. The correct way to do it is to implement it along with the work for #11138, but that isn't happening yet.

As i expect we will need to update Tor2web code?

I assume if you want to take advantage of the new response codes, you would. I don't know how Tor2web works, or what all that entails.

comment:6 Changed 2 years ago by nickm

  • Milestone changed from Tor: 0.2.??? to Tor: 0.2.7.x-final

These may be worth looking at for 0.2.7.

comment:7 Changed 2 years ago by nickm

  • Status changed from new to assigned

comment:8 Changed 2 years ago by nickm

  • Keywords 027-triaged-1-out added

Marking triaged-out items from first round of 0.2.7 triage.

comment:9 Changed 2 years ago by nickm

  • Milestone changed from Tor: 0.2.7.x-final to Tor: 0.2.???

Make all non-needs_review, non-needs_revision, 027-triaged-1-out items belong to 0.2.???

comment:10 Changed 19 months ago by nickm

  • Milestone changed from Tor: 0.2.??? to Tor: 0.2.8.x-final

comment:11 Changed 19 months ago by nickm

  • Points set to medium

comment:12 Changed 15 months ago by nickm

  • Milestone changed from Tor: 0.2.8.x-final to Tor: 0.2.???

It is impossible that we will fix all 252 currently open 028 tickets before 028 releases. Time to move some out. This is my first pass through the "assigned" tickets with no owner, looking for things to move to ???.

If somebody thinks they can get these done before the 0.2.8 timeout, please assign it to yourself and move it back?

comment:13 Changed 15 months ago by nickm

  • Keywords 6s194 added

comment:14 Changed 15 months ago by nickm

  • Keywords term-project-ideas added; 6s194 removed

These tickets were tagged "6s194" as ideas for possible term projects for students in MIT subject 6.S194 spring 2016. I'm retagging with term-project-ideas, so that the students can use the 6s194 tag for tickets they're actually working on.

comment:15 Changed 5 months ago by teor

  • Milestone changed from Tor: 0.2.??? to Tor: 0.3.???

Milestone renamed

comment:16 Changed 4 months ago by nickm

  • Keywords tor-03-unspecified-201612 added
  • Milestone changed from Tor: 0.3.??? to Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

Note: See TracTickets for help on using tickets.