Re: [squid-users] New to Squid and Linux

2006-08-02 Thread Christoph Haas
On Wednesday 02 August 2006 21:04, [EMAIL PROTECTED] wrote:
> I'm running Fedora Core 5 with Squid 2.5. How do I configure Squid so
> that I can view both http and https sites?

Unless Fedora provides a completely broken squid.conf with the installation 
Squid will already be able to handle HTTP and HTTPS well. Just take a look 
at the http_access statements to grant proper access.

 Christoph


Re: [squid-users] New to Squid and Linux

2006-08-02 Thread mjmcgraw

This is what my squid.conf looks like. Does it look broke?

hierarchy_stoplist cgi-bin ?
acl QUERY urlpath_regex cgi-bin \?
no_cache deny QUERY
auth_param basic children 5
auth_param basic realm Squid proxy-caching web server
auth_param basic credentialsttl 2 hours
auth_param basic casesensitive off
refresh_pattern ^ftp:   144020% 10080
refresh_pattern ^gopher:14400%  1440
refresh_pattern .   0   20% 4320
acl all src 0.0.0.0/0.0.0.0
acl manager proto cache_object
acl localhost src 127.0.0.1/255.255.255.255
acl to_localhost dst 127.0.0.0/8
acl SSL_ports port 443 563
acl Safe_ports port 80  # http
acl Safe_ports port 21  # ftp
acl Safe_ports port 443 563 # https, snews
acl Safe_ports port 70  # gopher
acl Safe_ports port 210 # wais
acl Safe_ports port 1025-65535  # unregistered ports
acl Safe_ports port 280 # http-mgmt
acl Safe_ports port 488 # gss-http
acl Safe_ports port 591 # filemaker
acl Safe_ports port 777 # multiling http
acl CONNECT method CONNECT
http_access allow manager localhost
http_access deny manager
http_access deny !Safe_ports
http_access deny CONNECT !SSL_ports
http_access allow localhost
http_access deny all
http_reply_access allow all
icp_access allow all
visible_hostname venus
coredump_dir /var/spool/squid

Thanks, Michael


Quoting Christoph Haas <[EMAIL PROTECTED]>:


On Wednesday 02 August 2006 21:04, [EMAIL PROTECTED] wrote:

I'm running Fedora Core 5 with Squid 2.5. How do I configure Squid so
that I can view both http and https sites?


Unless Fedora provides a completely broken squid.conf with the installation
Squid will already be able to handle HTTP and HTTPS well. Just take a look
at the http_access statements to grant proper access.

 Christoph






Re: [squid-users] New to Squid and Linux

2006-08-02 Thread Christoph Haas
On Wednesday 02 August 2006 22:16, [EMAIL PROTECTED] wrote:
> This is what my squid.conf looks like. Does it look broke?

Not at all. Just read and understand the documentation on "http_access" 
and "acl". Everything else is fine.

 Christoph


Re: [squid-users] New to Squid and Linux

2006-08-03 Thread mjmcgraw
Now it works from the local machine that is actually running squid,  
but when I try to SSH using Putty into the squid host I get nothing. I  
am forwarding port 3128 with Putty and setting the brower to use  
localhost:3128 for proxy.


Maybe I'm understanding this wrong but I thought if I used SSH to  
connect to the squid host it would appear as a local connection and  
the acl for localhost for work.


Did I totally miss that?

Thanks, Michael

Quoting Christoph Haas <[EMAIL PROTECTED]>:


On Wednesday 02 August 2006 22:16, [EMAIL PROTECTED] wrote:

This is what my squid.conf looks like. Does it look broke?


Not at all. Just read and understand the documentation on "http_access"
and "acl". Everything else is fine.

 Christoph






Re: [squid-users] New to Squid and Linux

2006-08-03 Thread Christoph Haas
On Thursday 03 August 2006 16:46, [EMAIL PROTECTED] wrote:
> Now it works from the local machine that is actually running squid,
> but when I try to SSH using Putty into the squid host I get nothing. I
> am forwarding port 3128 with Putty and setting the brower to use
> localhost:3128 for proxy.

Just point your browser to the proxy server on port 3128. SSH is not 
needed.

> Maybe I'm understanding this wrong but I thought if I used SSH to
> connect to the squid host it would appear as a local connection and
> the acl for localhost for work.

SSH supports port forwarding. But that's surely not the normal mode of 
operation and proxy surfing.

I hope it's clear that Squid is a HTTP proxy which is not at all connected 
to SSH.

 Christoph


Re: [squid-users] New to Squid and Linux

2006-08-03 Thread mjmcgraw
I'm trying to use SSH to tunnel my traffic to the machine that is  
running squid. The machines are not on the same network.


Michael

Quoting Christoph Haas <[EMAIL PROTECTED]>:


On Thursday 03 August 2006 16:46, [EMAIL PROTECTED] wrote:

Now it works from the local machine that is actually running squid,
but when I try to SSH using Putty into the squid host I get nothing. I
am forwarding port 3128 with Putty and setting the brower to use
localhost:3128 for proxy.


Just point your browser to the proxy server on port 3128. SSH is not
needed.


Maybe I'm understanding this wrong but I thought if I used SSH to
connect to the squid host it would appear as a local connection and
the acl for localhost for work.


SSH supports port forwarding. But that's surely not the normal mode of
operation and proxy surfing.

I hope it's clear that Squid is a HTTP proxy which is not at all connected
to SSH.

 Christoph






Re: [squid-users] New to Squid and Linux

2006-08-03 Thread Tim Neto
I think you have the wrong acronym.  Do you really want a SSL connection 
as in a "https" connection?  In reading this thread you keep typing SSH, 
but do you really need to use is SSL.


Tim

---
Timothy E. Neto
Computer Systems Engineer Komatsu Canada Limited
Ph#: 905-625-6292 x2651725B Sismet Road
Fax: 905-625-6348 Mississauga, Canada
E-Mail: [EMAIL PROTECTED]  L4W 1P9
---



[EMAIL PROTECTED] wrote:
I'm trying to use SSH to tunnel my traffic to the machine that is 
running squid. The machines are not on the same network.


Michael

Quoting Christoph Haas <[EMAIL PROTECTED]>:


On Thursday 03 August 2006 16:46, [EMAIL PROTECTED] wrote:

Now it works from the local machine that is actually running squid,
but when I try to SSH using Putty into the squid host I get nothing. I
am forwarding port 3128 with Putty and setting the brower to use
localhost:3128 for proxy.


Just point your browser to the proxy server on port 3128. SSH is not
needed.


Maybe I'm understanding this wrong but I thought if I used SSH to
connect to the squid host it would appear as a local connection and
the acl for localhost for work.


SSH supports port forwarding. But that's surely not the normal mode of
operation and proxy surfing.

I hope it's clear that Squid is a HTTP proxy which is not at all 
connected

to SSH.

 Christoph








RE: [squid-users] New to Squid and Linux

2006-08-03 Thread Michael J McGraw
No, I really meant SSH. I'm using Putty from work to my home linux box.

Michael

-Original Message-
From: Tim Neto [mailto:[EMAIL PROTECTED] 
Sent: Thursday, August 03, 2006 1:57 PM
To: squid-users@squid-cache.org
Subject: Re: [squid-users] New to Squid and Linux

I think you have the wrong acronym.  Do you really want a SSL connection 
as in a "https" connection?  In reading this thread you keep typing SSH, 
but do you really need to use is SSL.

Tim

---
Timothy E. Neto
Computer Systems Engineer Komatsu Canada Limited
Ph#: 905-625-6292 x2651725B Sismet Road
Fax: 905-625-6348 Mississauga, Canada
E-Mail: [EMAIL PROTECTED]  L4W 1P9
---



[EMAIL PROTECTED] wrote:
> I'm trying to use SSH to tunnel my traffic to the machine that is 
> running squid. The machines are not on the same network.
>
> Michael
>
> Quoting Christoph Haas <[EMAIL PROTECTED]>:
>
>> On Thursday 03 August 2006 16:46, [EMAIL PROTECTED] wrote:
>>> Now it works from the local machine that is actually running squid,
>>> but when I try to SSH using Putty into the squid host I get nothing. I
>>> am forwarding port 3128 with Putty and setting the brower to use
>>> localhost:3128 for proxy.
>>
>> Just point your browser to the proxy server on port 3128. SSH is not
>> needed.
>>
>>> Maybe I'm understanding this wrong but I thought if I used SSH to
>>> connect to the squid host it would appear as a local connection and
>>> the acl for localhost for work.
>>
>> SSH supports port forwarding. But that's surely not the normal mode of
>> operation and proxy surfing.
>>
>> I hope it's clear that Squid is a HTTP proxy which is not at all 
>> connected
>> to SSH.
>>
>>  Christoph
>>
>
>
>
>



Re: [squid-users] New to Squid and Linux

2006-08-03 Thread Brian Gregory
- Original Message - 
From: "Michael J McGraw" <[EMAIL PROTECTED]>
To: 
Sent: Thursday, August 03, 2006 9:18 PM
Subject: RE: [squid-users] New to Squid and Linux


> No, I really meant SSH. I'm using Putty from work to my home linux box.
> 
> Michael

In what way do you believe that squid might be involved with this process.

--

Brian Gregory.
[EMAIL PROTECTED]

Computer Room Volunteer.
Therapy Centre.
Prospect Park Hospital.


Re: [squid-users] New to Squid and Linux

2006-08-03 Thread Henrik Nordstrom
tor 2006-08-03 klockan 10:46 -0400 skrev [EMAIL PROTECTED]:
> Now it works from the local machine that is actually running squid,  
> but when I try to SSH using Putty into the squid host I get nothing. I  
> am forwarding port 3128 with Putty and setting the brower to use  
> localhost:3128 for proxy.

Should work. Have done that many times.

Just make sure you use the correct forwarding method, local port to
remote host. Not the opposite..

local port 3128
local address 127.0.0.1 (if it can be specified)
remote host 127.0.0.1
remote port 3128

Regards
Henrik


signature.asc
Description: Detta är en digitalt signerad	meddelandedel


Re: [squid-users] New to Squid and Linux

2006-08-03 Thread Henrik Nordstrom
tor 2006-08-03 klockan 22:03 +0100 skrev Brian Gregory:

> > No, I really meant SSH. I'm using Putty from work to my home linux box.
> > 
> > Michael
> 
> In what way do you believe that squid might be involved with this process.

He is trying to set up a port forward of the Squid port via SSH,
allowing him to connect to the Squid proxy port over SSH as he can't (or
won't) connect to it directly from his station.

Nothing strange, just a bit odd, but perfectly normal use of SSH the
swiss army knife of networking.

Regards
Henrik


signature.asc
Description: Detta är en digitalt signerad	meddelandedel


Re: [squid-users] New to Squid and Linux

2006-08-03 Thread mjmcgraw
It works when I am sitting at the linux box but when I try to SSH into  
it and use the squid proxy through the tunnel I can get no where.


I have my Putty tunnel setup for local port 3128 forwarded to remote  
port 3128.


L3128  ip.address.to.linuxbox:3128
L is for local port.

Should ip.address.to.linuxbox be 127.0.0.1 also?

Michael

Quoting Henrik Nordstrom <[EMAIL PROTECTED]>:


tor 2006-08-03 klockan 10:46 -0400 skrev [EMAIL PROTECTED]:

Now it works from the local machine that is actually running squid,
but when I try to SSH using Putty into the squid host I get nothing. I
am forwarding port 3128 with Putty and setting the brower to use
localhost:3128 for proxy.


Should work. Have done that many times.

Just make sure you use the correct forwarding method, local port to
remote host. Not the opposite..

local port 3128
local address 127.0.0.1 (if it can be specified)
remote host 127.0.0.1
remote port 3128

Regards
Henrik






Re: [squid-users] New to Squid and Linux

2006-08-04 Thread Henrik Nordstrom
On Thu, 2006-08-03 at 19:24 -0400, [EMAIL PROTECTED] wrote:

> I have my Putty tunnel setup for local port 3128 forwarded to remote  
> port 3128.
> 
> L3128  ip.address.to.linuxbox:3128
> L is for local port.
> 
> Should ip.address.to.linuxbox be 127.0.0.1 also?

Yes, most likely. It's the same as your proxy settings when running on
the box.

Regards
Henrik