SOCKS5 wani tsarin wakilci ne wanda ke watsawa TCP da UDP traffic tsakanin abokin ciniki da uwar garke ba tare da karanta bayanan aikace-aikace ba, don haka yana aiki tare da kowanne aikace-aikace da ke goyon bayan SOCKS, ba kawai masu bincike na yanar gizo ba. An bayyana shi a cikin RFC 1928, yana goyon bayan tantance sunan mai amfani/kalmar wucewa, kuma ba ya encrypt traffic a kansa.

Saboda SOCKS5 yana aiki tsakanin matakan aikace-aikace da sufuri maimakon fassara HTTP, ba ya takaita ga traffic na yanar gizo. Idan bukatunku suna bukatar SOCKS5, yana da kyau a tabbatar da cewa mai bayarwa yana goyon bayan shi kafin ku yarda.

Yadda SOCKS5 Connection ke Aiki

  1. Abokin ciniki yana haɗawa da wakilin, a al'ada akan TCP port 1080, kuma yana lissafa hanyoyin tantancewa da ya goyi bayan.
  2. Wakilin yana zaɓar ɗaya, kamar babu tantancewa ko sunan mai amfani/kalmar wucewa, kuma abokin ciniki yana tantancewa.
  3. Abokin ciniki yana aika wurin da zai tafi a matsayin adireshin IPv4, adireshin IPv6 ko suna na yankin. Yana amfani da CONNECT don TCP ko UDP ASSOCIATE don UDP.
  4. Wakilin yana buɗe haɗin kuma yana watsawa bayanai a dukkan hanyoyi.

Don UDP, wakilin yana amsa tare da adireshin wani UDP relay. Abokin ciniki yana aika datagrams dinsa a can, kuma haɗin yana ɗaukar lokaci ne kawai har tsawon haɗin TCP da ya kafa shi.

SOCKS5 vs. SOCKS4

SOCKS5 yana faɗaɗa tsohon tsarin SOCKS4:

  • Tantancewa: SOCKS4 yana da fili na ID na mai amfani kawai. SOCKS5 yana ƙara hanyoyi kamar sunan mai amfani/kalmar wucewa da GSSAPI.
  • UDP: SOCKS4 yana sarrafa TCP kawai. SOCKS5 kuma na iya watsawa UDP.
  • IPv6: SOCKS4 yana karɓar wurare na IPv4 kawai. SOCKS5 yana ƙara IPv6.
  • Sunan masarrafar: SOCKS5 yana ba wa abokin ciniki damar aika suna na yankin don wakilin ya warware. SOCKS4 yana buƙatar fa'idar SOCKS4a don yin wannan.

SOCKS5 vs. HTTP Proxy

Wakilin HTTP yana karanta kowanne buƙatar HTTP kuma yana iya ƙara headers kamar Via. Wakilin SOCKS5 yana watsawa bytes ba tare da karantawa ba, don haka yana iya ɗaukar traffic mara yanar gizo ma. Shafin shigar da HTTP yana da tebur mai gefe-zuwa-gefe.

Tantancewa da Encrypting

  • Hanyoyin da ake buƙata: RFC 1928 yana cewa aiwatar da daidaito dole ne su goyi bayan GSSAPI kuma ya kamata su goyi bayan sunan mai amfani/kalmar wucewa.
  • Kalmar wucewa a cikin rubutun bayyananne: hanyar sunan mai amfani/kalmar wucewa, wanda aka bayyana a cikin RFC 1929, yana aika kalmar wucewa ba tare da encrypting ba. RFC ba ya ba da shawarar yin hakan inda za a iya kamawa traffic.
  • Babu encrypting na kansa: SOCKS5 ba ya encrypt bayanan da yake watsawa. Traffic na HTTPS yana kasancewa a cikin encrypting saboda TLS yana gudana tsakanin aikace-aikacenku da shafin yanar gizo.

Inda DNS Lookups ke Faruwa

  • curl: wani socks5:// wakilin URL yana warware sunayen masarrafar a kan na'urarka. socks5h:// yana sa wakilin ya warware su.
  • Chrome: sunayen masarrafar SOCKS5 koyaushe ana warware su a wakilin. Don SOCKS4, Chrome yana warware su a kan abokin ciniki.

Binciken da aka yi a kan na'urarka na iya bayyana shafukan da kake ziyarta ga mai warware DNS na gida, wanda shine DNS leak.

Menene Wannan ke Nufi ga Web Scraping

  • Chrome ba zai iya shiga SOCKS5 ba: takardun shaida na Chrome suna cewa ba su goyi bayan kowanne hanyoyin tantance SOCKS5 kuma suna amfani da SOCKS5 kawai don buƙatun TCP. Don Chrome mai kai tsaye, yi amfani da tantancewa bisa IP ko wakilin HTTP tare da takardun shaida.
  • Ci gaba da bincike a kan wakilin: yi amfani da socks5h:// a cikin curl don haka binciken DNS suna wucewa ta wakilin maimakon hanyar sadarwarka.
  • Gwada tare da SSH: ssh -D <port> yana sa OpenSSH ya zama wakilin SOCKS4 da SOCKS5 na gida, wanda shine hanya mai sauri don gwada saitin SOCKS.

Sharuɗɗan da suka shafi