Squid...Autenticação

ti@cmrh.com.br
(usa CentOS)

Enviado em 21/09/2012 - 10:52h

ti@cmrh.com.br
(usa CentOS)

BOm dia a todos, e muito obrigado pela a atenção dispensada...

Seguinte as estações de trabalho estão visualizando e solicitando logon, porém o usuario e senha que criei não está logando, creio eu que algo sobre autenticação esteja errado ou quando crio o usuario, o comando que utilizo para criar e o seguite abaixo :
#####################################################################
htdigest /etc/squid/digpass "Squid proxy-caching server" frederico
#####################################################################

Segue abaixo o meu arquivo squid.conf


######################################################################
visible_hostname pdc3


auth_param digest program /usr/lib/squid/digest_pw_auth /etc/squid/digpass
auth_param digest children 5
auth_param digest realm Squid proxy-caching web server
auth_param digest nonce_garbage_interval 5 minutes
auth_param digest nonce_max_duration 30 minutes
auth_param digest nonce_max_count 50



# Recommended minimum configuration:

acl manager proto cache_object
acl localhost src 127.0.0.1/32 ::1
acl to_localhost dst 127.0.0.0/8 0.0.0.0/32 ::1

# Example rule allowing access from your local networks.
# Adapt to list your (internal) IP networks from where browsing
# should be allowed
acl localnet src 10.0.0.0/8 # RFC1918 possible internal network
acl localnet src 172.16.0.0/12 # RFC1918 possible internal network
acl localnet src 192.168.0.0/16 # RFC1918 possible internal network
acl localnet src fc00::/7 # RFC 4193 local private network range
acl localnet src fe80::/10 # RFC 4291 link-local (directly plugged) machines

acl SSL_ports port 443
acl Safe_ports port 80 # http
acl Safe_ports port 21 # ftp
acl Safe_ports port 443 # https
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

#Minhas Acl's


acl our_networks src 10.1.1.0/24
acl grupo_same proxy_auth "/etc/squid/acl/grupo_same.acl"
acl sites_same dstdomain "/etc/squid/acl/sites_same.acl"


acl autenticado proxy_auth REQUIRED

# Recommended minimum Access Permission configuration:
#
# Only allow cachemgr access from localhost
http_access allow manager localhost
http_access deny manager

# Deny requests to certain unsafe ports
http_access deny !Safe_ports

# Deny CONNECT to other than secure SSL ports
http_access deny CONNECT !SSL_ports

# We strongly recommend the following be uncommented to protect innocent
# web applications running on the proxy server who think the only
# one who can access services on "localhost" is a local user
#http_access deny to_localhost

#
# INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS

http_access allow autenticado our_networks
http_access allow grupo_same sites_same

# Example rule allowing access from your local networks.
# Adapt localnet in the ACL section to list your (internal) IP networks
# from where browsing should be allowed
http_access allow localnet
http_access allow localhost

# And finally deny all other access to this proxy
http_access deny all

# Squid normally listens to port 3128
http_port 3128

# We recommend you to use at least the following line.
hierarchy_stoplist cgi-bin ?

# Uncomment and adjust the following to add a disk cache directory.
#cache_dir ufs /var/spool/squid 100 16 256

# Leave coredumps in the first cache dir
coredump_dir /var/spool/squid

# Add any of your own refresh_pattern entries above these.
refresh_pattern ^ftp: 1440 20% 10080
refresh_pattern ^gopher: 1440 0% 1440
refresh_pattern -i (/cgi-bin/|\?) 0 0% 0
refresh_pattern . 0 20% 4320

#####################################################################

Obrigado

saitam
(usa Slackware)

Enviado em 21/09/2012 - 10:57h

segue how-to de proxy autenticado no squid e sarg

squid: http://mundodacomputacaointegral.blogspot.com.br/2011/12/configurando-servidor-proxy-autenticado.htm...

sarg:http://mundodacomputacaointegral.blogspot.com.br/2012/01/usando-sarg-para-monitorar-acessos-do.html

Espero que ajude!

Adonist
(usa Debian)

Enviado em 21/09/2012 - 12:25h

cara não sei ao certo
mas seu .conf do squid está desestruturado
o squid lê o arquivo de baixo para cima
e da esquerda para direita
isso pode ser um dos motivos
quanto a autenticação, existem vários métodos
como pelo AD, PAM, NCSA etc
pelo AD você precisa de um servidor Windows Server para autenticar
com o PAM você precisa criar o usuário no próprio linux
e via NCSA você cria um arquivo com os usuários

vê ao certo qual melhor se encaixa pra vc

abraços