[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
SOCKS4/5 support for OR and direcotry connections
- To: or-talk@xxxxxxxxxxxxx
- Subject: SOCKS4/5 support for OR and direcotry connections
- From: Christopher Davis <loafier@xxxxxxxxx>
- Date: Tue, 13 Jan 2009 12:26:15 -0800
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-talk-outgoing@xxxxxxxx
- Delivered-to: or-talk@xxxxxxxx
- Delivery-date: Tue, 13 Jan 2009 15:26:58 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject :message-id:mime-version:content-type:content-disposition:user-agent; bh=/5s79OEGtHWKMys6u888n+zJRyirxwaQS9K0VMs7cxs=; b=rlu1VZmgbJtDQfjuM1TfULbpSZO8EWIwifZSq0xDcHDnaQXKs1XJnGcmGmIFaSnh6j tQr7PnJBbWAEzUNJJaXwaLyD1z+y517bl1LD/s3+gN9RQUjl/9Kbc53aGE2Fk68p9zMZ aQ0liVUr+cr2cNDV07CEuF1BrxS01+Op4uRCo=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:mime-version:content-type :content-disposition:user-agent; b=vvjjp4WPrKXwG+SCvr3xRgF1OTJJ4OYZQfo6qQhIkA1tBMzve+q1DxlBLHu+3q2u5s 4/rShE2NgxMYs2zLH1dEBa9TPuJIKNhMLopqiYbzmDX+rb5B3LRXPXLDHgaChj2Lsuvf rM8pRHeOFNXILsQLHx/kJ03NRC2nTYYTepvhA=
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-talk@xxxxxxxxxxxxx
- User-agent: Mutt/1.4.2.3i
Hello,
I'm working on a patch to enable SOCKS 4 and 5 support for
Tor's OR and directory connections. I got SOCKS working for OR
connections already, but the directory behavior is a bit more
challenging to SOCKSify, because it queues the request immediately
on the connection's outbuf with the directory_send_command() call
right after connecting in directory_initiate_command_rend(). To
get SOCKS to work, the parameters (resource, payload, etc) would
need to be saved to the connection structure so
directory_send_command() can be called after the proxy handshake
finishes. Would that be acceptable?
--
Christopher Davis