Squid Top-Site Report Generator 1.2.0 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Squid Top-Site Report Generator 1.2.0 (Default branch)
# 1  
Old 05-14-2008
Squid Top-Site Report Generator 1.2.0 (Default branch)

STSRG (Squid Top-Site Report Generator) is ascript to analyze the previous day's squidaccess.log log file and produce a report of themost frequently visited URLs. It's reasonablyquick, processing about 100,000 lines of log filein 12 seconds.License: GNU General Public License (GPL)Changes:
The ability to sort by size, rather thanfrequency, was added.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

squid: Allow access to only one site and only via 80 or 443

Can someone please give me the conf file line to allow access to myexample.com and only that site, and only through http and https? So far I have only that site accessible via http, but all https sites are opened. Squid 3.1 on Cent 6 ---------- Post updated at 12:06 PM ---------- Previous... (0 Replies)
Discussion started by: glev2005
0 Replies
Login or Register to Ask a Question
digest_file_auth(8)					      System Manager's Manual					       digest_file_auth(8)

NAME
digest_file_auth - File based digest authentication helper for Squid. Version 1.0 SYNOPSIS
digest_file_auth [-c] file DESCRIPTION
digest_file_auth is an installed binary authentication program for Squid. It handles digest authentication protocol and authenticates against a text file backend. OPTIONS
-c Accept digest hashed passwords rather than plaintext in the password file CONFIGURATION
Username database file format: - comment lines are possible and should start with a '#'; - empty or blank lines are possible; - plaintext entry format is username:password - HA1 entry format is username:realm:HA1 To build a directory integrated backend, you need to be able to calculate the HA1 returned to squid. To avoid storing a plaintext password you can calculate MD5(username:realm:password) when the user changes their password, and store the tuple username:realm:HA1. then find the matching username:realm when squid asks for the HA1. This implementation could be improved by using such a triple for the file format. However storing such a triple does little to improve security: If compromised the username:realm:HA1 combination is "plaintext equivalent" - for the purposes of digest authentication they allow the user access. Password syncronisation is not tackled by digest - just preventing on the wire compromise. AUTHOR
This program was written by Robert Collins <robertc@squid-cache.org> Based on prior work by Arjan de Vet <Arjan.deVet@adv.iae.nl> This manual was written by Robert Collins <robertc@squid-cache.org> Amos Jeffries <amosjeffries@squid-cache.org> COPYRIGHT
This program and documentation is copyright to the authors named above. Distributed under the GNU General Public License (GNU GPL) version 2 or later (GPLv2+). QUESTIONS
Questions on the usage of this program can be sent to the Squid Users mailing list <squid-users@squid-cache.org> REPORTING BUGS
Bug reports need to be made in English. See http://wiki.squid-cache.org/SquidFaq/BugReporting for details of what you need to include with your bug report. Report bugs or bug fixes using http://bugs.squid-cache.org/ Report serious security bugs to Squid Bugs <squid-bugs@squid-cache.org> Report ideas for new improvements to the Squid Developers mailing list <squid-dev@squid-cache.org> SEE ALSO
squid(8), GPL(7), The Squid FAQ wiki http://wiki.squid-cache.org/SquidFaq The Squid Configuration Manual http://www.squid-cache.org/Doc/config/ digest_file_auth(8)