Editing XEP-0065: SOCKS5 Bytestreams
From JaWiki (Jabber/XMPP wiki)
Warning: The database has been locked for maintenance, so you will not be able to save your edits right now. You may wish to copy and paste your text into a text file and save it for later.
The administrator who locked it offered this explanation: MediaWiki upgrading
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 382: | Line 382: | ||
Здесь Инициатор узнаёт, какой ВедущийУзел использует Цель. | Здесь Инициатор узнаёт, какой ВедущийУзел использует Цель. | ||
− | === | + | === Initiator Establishes SOCKS5 Connection with StreamHost === |
− | + | If the StreamHost used is a Proxy, the Initiator MUST authenticate and establish a connection with the StreamHost before requesting that the StreamHost activate bytestream. The Initiator will establish a connection to the SOCKS5 proxy in the same way the Target did (passing the same value for the CONNECT request), as shown in the following examples. | |
+ | Example 17. Initiator Connects to StreamHost | ||
+ | CMD = X'01' | ||
+ | ATYP = X'03' | ||
+ | DST.ADDR = SHA1 Hash of: (SID + Initiator JID + Target JID) | ||
+ | DST.PORT = 0 | ||
+ | |||
− | + | Example 18. StreamHost Acknowledges Connection to Initiator | |
− | + | STATUS = X'00' | |
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
=== Activation of Bytestream === | === Activation of Bytestream === | ||