Bypass Proxy - Revision history

PhilippeTeuwen: /* SOCKS5 */

2015-05-01T16:50:21Z

SOCKS5

← Older revision		Revision as of 16:50, 1 May 2015
Line 499:		Line 499:
	[ProxyList]		[ProxyList]
	socks5 127.0.0.1 12345		socks5 127.0.0.1 12345
			It's also possible to redirect DNS through proxy ("proxy_dns") but if you don't need it, it will work smoother without.

	Use it, e.g.:		Use it, e.g.:
	proxychains youtube-dl "Some geo-locked video web page"		proxychains youtube-dl "Some geo-locked video web page"

2015-05-01T16:48:54Z

Next step: Through real SSL Proxies

← Older revision		Revision as of 16:48, 1 May 2015
Line 479:		Line 479:
	What socat cannot do, our script can!		What socat cannot do, our script can!
	ProxyCommand /usr/local/bin/ssh-tunnel.pl - 0 %h %p -e -R my.server:443 -U <user> -P <password> --noproxy		ProxyCommand /usr/local/bin/ssh-tunnel.pl - 0 %h %p -e -R my.server:443 -U <user> -P <password> --noproxy
			==Make your own SOCKS5==
			Example: download geo-locked content.
			===youtube-dl===
			apt-get install youtube-dl
			or
			wget https://yt-dl.org/latest/youtube-dl
			chmod +x youtube-dl

			===SOCKS5===
			Just ssh to a box in the right area and enable SOCKS5 proxy:
			ssh -D 12345 remote_host
			Get proxychains
			apt-get install proxychains
			Edit /etc/proxychains.conf
			dynamic_chain
			quiet_mode
			tcp_read_time_out 15000
			tcp_connect_time_out 8000
			[ProxyList]
			socks5 127.0.0.1 12345
			Use it, e.g.:
			proxychains youtube-dl "Some geo-locked video web page"

2013-02-20T11:55:55Z

Reverted edits by JanWilkinson1952 (talk) to last revision by PhilippeTeuwen

Can't load revision 7874

2013-02-19T09:42:20Z

Background

Can't load revision 7873

2010-11-24T20:36:15Z

Reverted edits by Etegohy (Talk) to last revision by PhilippeTeuwen

Can't load revision 6866

2010-11-24T00:32:11Z

Can't load revision 6708

2009-02-04T14:58:27Z

Utilisation de SSH à travers un proxy

← Older revision		Revision as of 14:58, 4 February 2009
Line 51:		Line 51:

	==Utilisation de SSH à travers un proxy==		==Utilisation de SSH à travers un proxy==
	~~Installez~~ [http://git.yobi.be/?p=ssh-tunnel.git;a=~~summary~~ ce ~~script~~ ~~(!git)]~~ ~~dans~~ ~~par exemple /usr/local/bin/ssh-tunnel.pl~~		Récupérez [http://git.yobi.be/?p=ssh-tunnel.git;a=snapshot;h=HEAD;sf=tgz la dernière version du script]
			<br>Installez le script dans par exemple /usr/local/bin/ssh-tunnel.pl

2009-02-04T14:56:26Z

Utilisation de SSH à travers un proxy

2008-11-25T20:38:56Z

Having fun with socat, bash & file descriptors...

← Older revision		Revision as of 20:38, 25 November 2008
Line 1,263:		Line 1,263:
	exec multitee 0:3 3:1'		exec multitee 0:3 3:1'

	Multitee (source [http://cr.yp.to/software/multitee-3.0.shar.gz here], also packaged in Debian) can do exactly what socat was doing: "socat - FD:3" == "multitee 0:3 3:1"		Multitee (source [http://cr.yp.to/software/multitee-3.0.shar.gz here], also packaged in Debian) can do exactly what socat was doing: "socat - FD:3" == "multitee 0:3 3:1".
			<br>To compile multitee on Cygwin, see [[Cygwin-multitee\|here]]

	==Using SSH as a proxy==		==Using SSH as a proxy==

2008-11-22T16:45:16Z

Having fun with socat, bash & file descriptors...

← Older revision		Revision as of 16:45, 22 November 2008
Line 1,254:		Line 1,254:

	Back with socat, here used just to maintain the forwarding between stdin/stdout and file descriptor 3.		Back with socat, here used just to maintain the forwarding between stdin/stdout and file descriptor 3.
	* If you compare it with the two cat solution, ~~not~~ that forwarding from server to client was done before as the client will send its banner only once it gets something from the server. To achieve the same we introduced the "head -c 50" to forward part of the server-to-client communication before eating the client banner.		* If you compare it with the two cat solution, note that forwarding from server to client was done before as the client will send its banner only once it gets something from the server. To achieve the same we introduced the "head -c 50" to forward part of the server-to-client communication before eating the client banner.
	* "head -c 50": the number 50 is not that important, it has to be bigger than the server banner (usually between 20 and 35 chars) and smaller than the first server packet (about 800 chars)		* "head -c 50": the number 50 is not that important, it has to be bigger than the server banner (usually between 20 and 35 chars) and smaller than the first server packet (about 800 chars)