From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1JENrp-00065U-Ja for garchives@archives.gentoo.org; Mon, 14 Jan 2008 11:52:37 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 2693AE0A94; Mon, 14 Jan 2008 11:52:10 +0000 (UTC) Received: from wa-out-1112.google.com (wa-out-1112.google.com [209.85.146.177]) by pigeon.gentoo.org (Postfix) with ESMTP id 59A77E0A87 for ; Mon, 14 Jan 2008 11:52:09 +0000 (UTC) Received: by wa-out-1112.google.com with SMTP id k34so3670931wah.10 for ; Mon, 14 Jan 2008 03:52:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=JC0U0jR/S2d5x0a1N5/wDT20D5nWYCBCEe7S2EjlHtw=; b=lB4X1IBWW1FKJeFZxwQfIebiFp0KCrklasZWqz99A8fhy6Ndz2A5QDnrk48fGbDdaaWxEEs72krUE197l6fHGKWhTVMfjvQpT8Z56+OoKkLTunA4qDoHKIPswnqBuFRA3BnSYWdQCLG7siqX7iKBcZ4AyLr6TFs5qsuDAylcm9E= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=g06xht+EJ43S+Ysr55pHBhfy5pqRgHn5RCWoaRcXF3B8nj4K9niTp+yFj6EcD4tigfFWeYyJEWUtjOHN8dMOdTiRAfZtZIhBx5wMIzi1A7YrAQsyPQhnI3qzFMXXAQJaqGuJmIYmEAVH1CbI4fy6uWQyhC6SM6HAcb+Ue0H9X8c= Received: by 10.114.88.1 with SMTP id l1mr1149548wab.79.1200311528878; Mon, 14 Jan 2008 03:52:08 -0800 (PST) Received: by 10.115.76.8 with HTTP; Mon, 14 Jan 2008 03:52:08 -0800 (PST) Message-ID: Date: Mon, 14 Jan 2008 13:52:08 +0200 From: "Elyahou ITTAH" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] SSH tunnel With Portage In-Reply-To: <200801141251.52371.shrdlu@unlimitedmail.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_11080_16466813.1200311528866" References: <200801141214.27087.shrdlu@unlimitedmail.org> <200801141251.52371.shrdlu@unlimitedmail.org> X-Archives-Salt: c089f1d0-72a6-4445-baff-584a3a367d25 X-Archives-Hash: f685c1ecdc2bb8b1c26171960a7dfb7c ------=_Part_11080_16466813.1200311528866 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline 2008/1/14, Etaoin Shrdlu : > > On Monday 14 January 2008, Elyahou ITTAH wrote: > > > Ok, ;) > > > > My Network have a Squid Proxy who allow only some ports like 80 443... > > Ok, so you should be able to use > > # export http_proxy="proxyname or address" > # emerge-webrsync > > To use the already existing proxy in your network. If you insist on using > your tunnel, read on. > > > Putty is configurated to connect to a box i have in an other place, it > > allow to make a SSH Tunnel who create a socks proxy at localhost:8080. > > So you're forwarding port 8080 on the putty (windows) box to port 1080 on > the remote box, where a SOCKS server is listening on that port, correct? > > I'm not sure whether putty allows non-local connections to forwarded > ports by default, if this is not the case you'll need to enable that > option. > > > Putty listen to this port and send all the frames passing the 443 of > > the SQUID proxy to my exterior box. > > How do you do that? > > > I wan't to configure Portage to > > use this SOCK proxy at localhost:8080 > > "localhost", IIUC, is a windows box, and portage is running on another > (linux, on the same network) box. So, at a minimum, you'll need to > use "a.b.c.d:8080" as a SOCKS server, where a.b.c.s is the IP address of > the windows putty box. > > Assuming you have a SOCKS server at "a.b.c.d:8080" (albeit through a > tunnel, but the apps don't know that), then you need to use some > socksifying utility for emerge, since (AFAIK) it does not support SOCKS > out of the box. So, something like > > # socksify emerge --sync > > should work (though I have not tested it). socksify is part of > net-proxy/dante. Of course, you need to specify the SOCKS proxy at > a.b.c.d port 8080 in the /etc/socks/socks.conf configuration file (I > don't remember the exact syntax to do that right now, but it should be > quite intuitive). > -- > gentoo-user@lists.gentoo.org mailing list I am a little confused... Putty listen to my 127.0.0.1:8080 and forward to my extern box:443 passing the squid proxy:3128 (in SSH of course) I tried configure the http proxy by export... but the web rsync still don't run... ------=_Part_11080_16466813.1200311528866 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline

2008/1/14, Etaoin Shrdlu <shrdlu@unlimitedmail.org>:
On Monday 14 January 2008, Elyahou ITTAH wrote:

> Ok, ;)
>
> My Network have a Squid Proxy who allow only some ports like 80 443...

Ok, so you should be able to use

# export http_proxy="proxyname or address"
# emerge-webrsync

To use the already existing proxy in your network. If you insist on using
your tunnel, read on.

> Putty is configurated to connect to a box i have in an other place, it
> allow to make a SSH Tunnel who create a socks proxy at localhost:8080.

So you're forwarding port 8080 on the putty (windows) box to port 1080 on
the remote box, where a SOCKS server is listening on that port, correct?

I'm not sure whether putty allows non-local connections to forwarded
ports by default, if this is not the case you'll need to enable that
option.

> Putty listen to this port and send all the frames passing the 443 of
> the SQUID proxy to my exterior box.

How do you do that?

> I wan't to configure Portage to
> use this SOCK proxy at localhost:8080

"localhost", IIUC, is a windows box, and portage is running on another
(linux, on the same network) box. So, at a minimum, you'll need to
use "a.b.c.d:8080" as a SOCKS server, where a.b.c.s is the IP address of
the windows putty box.

Assuming you have a SOCKS server at "a.b.c.d:8080" (albeit through a
tunnel, but the apps don't know that), then you need to use some
socksifying utility for emerge, since (AFAIK) it does not support SOCKS
out of the box. So, something like

# socksify emerge --sync

should work (though I have not tested it). socksify is part of
net-proxy/dante. Of course, you need to specify the SOCKS proxy at
a.b.c.d port 8080 in the /etc/socks/socks.conf configuration file (I
don't remember the exact syntax to do that right now, but it should be
quite intuitive).
--
gentoo-user@lists.gentoo.org mailing list


I am a little confused...

Putty listen to my 127.0.0.1:8080 and forward to my extern box:443 passing the squid proxy:3128 (in SSH of course)

I tried configure the http proxy by export... but the web rsync still don't run...






------=_Part_11080_16466813.1200311528866-- -- gentoo-user@lists.gentoo.org mailing list