Samun wata HTTP ko SOCKS proxy data kasance ta hanyar SSH
Samun wata nesa loopback HTTP ko SOCKS proxy ta hanyar SSH ba tare da fallasa mai sauraronta a fili ba.
Idan relay.example.net ya riga yana gudanar da SOCKS a kan 127.0.0.1:1080 nasa, tura damar shiga maimakon fallasa wannan mai saurare a fili:
ssh -N -L 127.0.0.1:1081:127.0.0.1:1080 [email protected]| Ƙarshen hanya | Matsayi |
|---|---|
Laptop 127.0.0.1:1081 | Adireshin SOCKS da za a saita a cikin manhajar laptop ɗin. |
Relay 127.0.0.1:1080 | Proxy ɗin da ke akwai wanda ake samu daga gefen uwar garken SSH. |
Rubutun tura gida yana ba da ƙayyadadden makoma ga gefen uwar garke. HTTP proxy a tashar loopback ta nesa 3128 ko ƙarshen cibiyar sadarwa kamar proxy.internal.example:8080 yana aiki bisa wannan ƙa'ida. Saita abokin ciniki don wancan HTTP protocol ɗin da ke akwai da asusu; ɗaukar sa ta SSH ba ya ƙirƙirar SOCKS ko mai sauraron HTTPS mai TLS.
Sabis ɗin da ke akwai har yanzu yana zaɓar nau'ikan protocol da ake tallafawa, tabbatarwa, wuraren zuwa da fitarwar ƙarshe. Idan wani tsari na SSH ya ƙirƙiri wancan proxy na nesa, dole ne duka tsarin biyu su kasance da rai. Hanyar laptop→relay→ƙofa tana barin gidan yanar gizon ya ga haɗin waje na ƙarshe, ba wani asali da tashar gida 1081 ta ware ba.
Riƙe ɗaurin laptop ɗin a fili a gida. Faɗaɗɗen fallasa yana canza wanda zai iya isa sabis ɗin, kuma shiga SSH ba ya ƙara kalmar sirri ta SOCKS ga mai sauraro. Don ƙi, duba mai sauraron laptop, jigilar SSH da proxy na nesa a matsayin matakai daban.