Gadar socat SOCKS: kiyaye sunan masaukin TLS na shafin

Yi amfani da mai sauraron TCP na loopback don manufar SOCKS ɗaya yayin kiyaye asalin HTTP da TLS a cikin aikace-aikacen.

Aikace-aikacen ba shi da zaɓin SOCKS, amma yana iya haɗawa da adireshin TCP da aka zaɓa. Mai daidaitawa mai tsayayyen manufa na iya ba da tattaunawar SOCKS don manufa ɗaya. Ba lallai ba ne ya zama wani babban wakili na gaba.

Ga gine-ginen socat da ke ba da SOCKS4A, misalin tsari shi ne:

socat TCP4-LISTEN:9443,bind=127.0.0.1,reuseaddr,fork \
  SOCKS4A:127.0.0.1:service.example.net:443,socksport=1080

Ƙarshen SOCKS shine tashar gida 1080. Mai daidaitawa yana saurare a tashar gida 9443 kuma yana neman wannan ƙarshen service.example.net:443. Waɗannan ƙimar misali ne, ba cikakken tura sabis ba.

Mai daidaitawa yana da tsayayyen manufa ɗaya

Kowace haɗin TCP da aka karɓa tana neman sabis ɗaya. Aikace-aikacen da ke haɗawa da 9443 yana ba da bayanan ka'idarsa na yau da kullum; socat yana ba da tattaunawar SOCKS4A. Aika sabuwar buƙatar HTTP CONNECT zuwa 9443 ba zai zaɓi wata manufa ba—zai aika waɗannan bayanan zuwa tsayayyen sabis ɗin.

SOCKS4A yana ba da sunan masauki ga ƙarshen SOCKS don warwarewar nesa. Wannan ya bambanta da sigar SOCKS4 da ke amfani da adireshin da abokin ciniki ya zaɓa. Tushen da aka zaɓa—ciki har da ɗan takara na jama'a daga jerin wakilan SOCKS4—dole ne ya goyi bayan sarrafa sunan masaukin SOCKS4A da tabbacin da ake buƙata; wannan misalin ba girke-girken shiga da kalmar sirri ta SOCKS5 ba ne.

Haɗa a gida, gane ainihin sabis ɗin

Canza URL na HTTPS zuwa https://127.0.0.1:9443/ yana canza sunan masaukin da abokin ciniki zai iya amfani da shi don TLS da HTTP. Takardar shaidar service.example.net ba za ta zama ingantacciyar takardar shaidar loopback ba.

Inda abokin ciniki ke goyan bayan hanyar haɗi daban, kiyaye asalin URL na asali. Curl na iya nuna wannan bambancin:

curl --noproxy '*' \
  --connect-to service.example.net:443:127.0.0.1:9443 \
  https://service.example.net/

Socket ɗin yana zuwa ga mai daidaitawa na gida yayin da tabbacin TLS da makomar HTTP sun kasance service.example.net. Sauran aikace-aikace suna buƙatar nasu daidaitaccen kulawa mai goyan baya; ba kowane abokin ciniki ne ke bayar da shi ba.

Haɗin loopback yana iyakance fallasa cibiyar sadarwa, amma wasu hanyoyin gida da suka cancanta na iya isa gare shi. Ka riƙe tsawon rayuwar sabis ɗin da masu amfani da su dace. Ka riƙe tabbacin TLS maimakon murkushe kuskuren asali da URL na loopback ya haifar.

Labarai masu alaƙa