On Wed, 1 Aug 2001, Joe Cooper wrote:
> I'm not itching for more auth options at the moment, personally. From
> my perspective, Oops needs work in some other areas...
alright, I know, but igor is so-out-of-order, thus we cannot discuss about
your (and others') wishes.
> Performance--a well tuned Squid is considerably faster on big hardware,
> contrary to popular opinion. On small hardware Oops wins, IMHO, but
> because it's more memory efficient not because it runs faster and memory
> usage is usually more important on smaller hardware (like a small
> gateway/router/firewall type box with multiple services running in the
> small business environment). So a faster Oops that can really take
> advantage of multiple disks and lots of RAM would be good.
yep, not a trivial question. afaik the performance increasing on the most
system is about the hardest work, because we need to know which progress
takes the most time, how could we fasten it. But if you have exact ideas,
where we can optimize the code, please share it!
> Database-backed redirector (ala SquidGuard)--Maybe I'm just not familiar
> enough with the existing redirection options in Oops, but it seems like
> creating a content filtering system with Oops is not currently possible.
> One of my pet projects right now is to create a free porn blocking
> system for Squid+SquidGuard, and I'd like to support more proxy
> platforms if possible. But a list of 500,000 domains (a guess, we
> haven't actually compiled the lists and edited them yet) is not going to
> work very well in a flat file list.
so.. oops redirector is very good in that stage, especially if you compile
it with pcre (perl compatible regular expression), just watch the oops
debian package (/usr/share/doc/oops/examples/adfilter) or watch the
author's HP: http://nrg.martos.bme.hu/release/adfilter [thanks Raszi for
your work]
and, I mentioned abrand-new feature to Igor, but seems, he doesn't have
time, plus he's away (maybe vacation?). this ability called by me as
content-filter/acl. I started to plan (really it is an idea yet) a method
to filter/modify/block the web pages byt its CONTECNT. for example, you'd
like to eliminate the ALL scripts, or images, or anything from the
incoming web pages, this way, you can. simply it should be good, if you
can do that by an ACL or a simple sed-like regexp command. that is
supported by the pcre, see the adfilter's end eg.:
http://.*\.g\.akamai\.net/([^/]+/){4}(.*) http://$2
keep in mind, it is brainstorming yet, so drop me, and us with your ideas,
comments. :)
> Well, you /did/ ask. ;-)
right, seems, pam, sql, file auth is enough for the common users. :) i
delay this. :)
--
VWOL
Tamas SZERB <[EMAIL PROTECTED]>
GPG public key: http://alabama.rulez.org/~toma/gpgkey-toma.asc
=====================================================================
If you would like to unsubscribe from this list send message to
[EMAIL PROTECTED] with "unsubscribe oops-eng" in message body.
Archive is accessible on http://www.paco.net/oops/
