Skip to content
This repository has been archived by the owner. It is now read-only.
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also .

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also .
base repository: Yawning/goptlib
base: master
head repository: Yawning/goptlib
compare: bug12535_v2
Checking mergeability… Don’t worry, you can still create the pull request.
  • 1 commit
  • 3 files changed
  • 0 comments
  • 1 contributor
Commits on Apr 03, 2015
@Yawning
Replace the SOCKS4a listener with a SOCKS5 listener.
93bcaf4 
The change is designed to be transparent to calling code and implements
enough of RFC1928/RFC1929 such that pluggable transports can be written.

Notable incompatibilities/limitations:
 * GSSAPI authentication is not supported.
 * BND.ADDR/BND.PORT in responses is always "0.0.0.0:0" instead of the
   bound address/port of the outgoing socket.
 * RFC1929 Username/Password authentication is setup exclusively for
   pluggable transport arguments.
 * The BIND and UDP ASSOCIATE commands are not supported.
Showing with 685 additions and 216 deletions.
  1. +3 −2 pt.go
  2. +324 −62 socks.go
  3. +358 −152 socks_test.go
5 pt.go
View file
@@ -119,10 +119,11 @@
// Extended ORPort Authentication:
// https://gitweb.torproject.org/torspec.git/tree/proposals/217-ext-orport-auth.txt.
//
// The package implements a SOCKS4a server sufficient for a Tor client transport
// The package implements a SOCKS5 server sufficient for a Tor client transport
// plugin.
//
// http://ftp.icm.edu.pl/packages/socks/socks4/SOCKS4.protocol
// https://www.ietf.org/rfc/rfc1928.txt
// https://www.ietf.org/rfc/rfc1929.txt
package pt

import (

No commit comments for this range