From: "Garcia Ruiz" <gar_ruiz@teleline.es>
To: Ramin Dousti <ramin@cannon.eng.us.uu.net>
Cc: jen@saturn5.com, netfilter@lists.netfilter.org
Subject: Re: ssl forward / proxy question
Date: Sat, 26 Jul 2003 00:03:27 +0200 [thread overview]
Message-ID: <001601c352f8$94146f00$05001aac@breton1> (raw)
In-Reply-To: 20030725193303.GB30070@cannon.eng.us.uu.net
I can tell you that squid 2.5 supports reverse proxying and it works this
way: Client -> SSL -> Squid (with certificates) -> No SSL -> Internal
Server. I think that HTTP proxying supports reverse proxying for more than 1
server but I don't know if it's the same for SSL. In this case your only
problem is that the internal network donn't have encryption (Is it fine for
you¿?). If reverse proxy works for you, you can get an extra: The load of
you web servers will be much lower (you won't probably get cached SSL pages
but as you know, when requesting a page there are a lot of requests -images
among other- and these kind of requests can be cached and also are very
heavy. The load of your servers would be also lower due to the lack of
encryption-decryption inside them).
Squid 3.0 supports Client -> SSL -> Squid (with certificates) -> SSL ->
Internal Server but it is in developement state (I wouldn't use in
production mode).
Here you have some interesting links:
http://squid.bilkent.edu.tr/mail-archive/squid-users/200102/0714.html
http://www.squid-cache.org/mail-archive/squid-users/200303/1040.html
http://squid.visolve.com/white_papers/reverseproxy.htm
Regards,
JBGR
----- Original Message -----
From: "Ramin Dousti" <ramin@cannon.eng.us.uu.net>
To: "Garcia Ruiz" <gar_ruiz@teleline.es>
Cc: <jen@saturn5.com>; <netfilter@lists.netfilter.org>
Sent: Friday, July 25, 2003 9:33 PM
Subject: Re: ssl forward / proxy question
> You mean squid is going to handle the "get" requests for https??????
> Meaning it's terminating SSL, sending the right cert, negotiating a
> session key with the client, getting the request and fetching the
> contents based on the "get" request from the right web server on the
> LAN????
>
> Can you confirm all the above? If so, squid is a big security hole,
> but I'm sure it's not:
>
> http://www.squid-cache.org/Doc/FAQ/FAQ-1.html#ss1.12
>
> Ramin
>
> On Fri, Jul 25, 2003 at 08:38:14PM +0200, Garcia Ruiz wrote:
>
> > Have a look at Squid proxy. The last releases admit SSL reverse
proxying. If
> > it would be capable of handling different servers your problem would be
> > solved. You could have it inside of the firewall (but be careful with
> > security issues).
> >
> > Regards.
> >
> > BGR
>
next prev parent reply other threads:[~2003-07-25 22:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 0:12 ssl forward / proxy question jen
2003-07-25 18:38 ` Garcia Ruiz
2003-07-25 19:33 ` Ramin Dousti
2003-07-25 22:03 ` Garcia Ruiz [this message]
2003-07-26 2:46 ` Ramin Dousti
2003-07-29 18:51 ` jen
-- strict thread matches above, loose matches on Subject: below --
2003-07-25 0:44 George Vieira
2003-07-28 15:05 Hulsman, MJ (Mike)
2003-07-28 15:45 ` Ramin Dousti
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='001601c352f8$94146f00$05001aac@breton1' \
--to=gar_ruiz@teleline.es \
--cc=jen@saturn5.com \
--cc=netfilter@lists.netfilter.org \
--cc=ramin@cannon.eng.us.uu.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox