[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-dev] Proposal xxx: Further SOCKS5 extensions (Was Pluggable transport SOCKS5 extensions)

To: tor-dev@xxxxxxxxxxxxxxxxxxxx
Subject: Re: [tor-dev] Proposal xxx: Further SOCKS5 extensions (Was Pluggable transport SOCKS5 extensions)
From: "Sebastian G. <bastik.tor>" <bastik.tor@xxxxxxxxxxxxxx>
Date: Sat, 01 Mar 2014 13:57:34 +0100
Delivered-to: archiver@xxxxxxxx
Delivery-date: Sat, 01 Mar 2014 07:57:48 -0500
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=dYC11JJlwELah/8TLSHuv6QOEkLcZgpqLn4h9hPZDVI=; b=LVMOBBRCwCu0TCXtNwYnMDQc/HOxdiRn2BbQy8BHDVNf9dWmcNw5RtTwQ1Vichc5mJ ncNMhAYv8K9tqjFxK3XKVGgZKI2zPcrW6seKpt8fr1IQXbdS05z47Bt39BBMB5S+ui5U xMyvvz0pPNkJrN768FTVq5ezy923N81nDlHUWkQLAHFeRbRddT5+VU2onACz76YKnJb/ rxyheyzokk7xHK5UyR1upUC/YHwpNoz6IFZz7fjAyNRPgiRmeiI0x9wheUs23nfuBmJA Eu00PHKVmRrD3RNU+CeE1wTlA3braomygGycPUfufMAr+EtitM7D1Oe/6M6Z6c9Kq+jl avqg==
In-reply-to: <20140228085316.5210f36a@xxxxxxxxxxxxxxx>
List-archive: <http://lists.torproject.org/pipermail/tor-dev/>
List-help: <mailto:tor-dev-request@lists.torproject.org?subject=help>
List-id: discussion regarding Tor development <tor-dev.lists.torproject.org>
List-post: <mailto:tor-dev@lists.torproject.org>
List-subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev>, <mailto:tor-dev-request@lists.torproject.org?subject=subscribe>
List-unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-dev>, <mailto:tor-dev-request@lists.torproject.org?subject=unsubscribe>
References: <20140225101511.04998166@xxxxxxxxxxxxxxx> <20140228085316.5210f36a@xxxxxxxxxxxxxxx>
Reply-to: tor-dev@xxxxxxxxxxxxxxxxxxxx
Sender: "tor-dev" <tor-dev-bounces@xxxxxxxxxxxxxxxxxxxx>
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0

28.02.2014 09:53, Yawning Angel:
> 2.2. Tor Extended SOCKS5 Reply Codes
> 
> We introduce the following additional SOCKS5 reply codes to be sent
> in the REP field of a SOCKS5 message.  Implementations MUST NOT
> send any of the extended codes unless the initiator has indicated
> that it understands the "Tor Extended SOCKS5 Authentication" as
> part of the version identifier/method selection SOCKS5 message.
> 
> Where:
> 
> * X'E0' Hidden Service Not Found
> 
> The requested Tor Hidden Service was not reachable.
> 
> * X'E1' Hidden Service Not Reachable
> 
> The requested Tor Hidden Service was not found.

To me it is clear that the two are messed up, but I'm not sure what's
the correct order.

X'E0' means either it couldn't be found or it is not reachable, but is
the description wrong or the error message?

Regards,
Sebastian (bastik)
_______________________________________________
tor-dev mailing list
tor-dev@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev

Follow-Ups:
- Re: [tor-dev] Proposal xxx: Further SOCKS5 extensions (Was Pluggable transport SOCKS5 extensions)
  - From: Yawning Angel

Prev by Author: Re: [tor-dev] Fwd: About using source code
Next by Author: Re: [tor-dev] Proposal 228: Cross-certifying identity keys with onion keys
Previous by thread: Re: [tor-dev] [weather-rewrite] Update on hourly-script
Next by thread: Re: [tor-dev] Proposal xxx: Further SOCKS5 extensions (Was Pluggable transport SOCKS5 extensions)
Index(es):
- Author
- Thread