linux-traipu team mailing list archive

[Clint Byrum <clint@xxxxxxxxxx>]

Excerpts from Stewart Smith's message of Tue Feb 14 23:36:37 UTC 2012:
> On Tue, 14 Feb 2012 08:20:51 -0000, Henrik Ingo <henrik.ingo@xxxxxxxxxxxxx> wrote:
> > In auth_regex the pair of commands ACCEPT/DENY is confusing. It should
> > have been either ACCEPT/REJECT  (see iptables) or ALLOW/DENY (see apache
> > httpd). My proposal is to make it ALLOW/DENY.
> 
> Maybe allow all 4, with ACCEPT/REJECT being synonyms for ALLOW/DENY and
> then it should all "just work"? :)
> 

+1 from me.

Note that this plugin *really* needs to have my other branch merged which
helps to reduce its memory impact on the system. It caches every lookup
right now. This branch fixes that by limiting the cache size:

https://code.launchpad.net/~clint-fewbar/drizzle/regex-policy-cache-
limiter/+merge/53536

I wouldn't recommend using the plugin without that branch merged (failed
on some boost bug in SuSE)

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Drizzle.
https://bugs.launchpad.net/bugs/931917

Title:
  regex_policy should use apache like ALLOW/DENY

Status in A Lightweight SQL Database for Cloud Infrastructure and Web Applications:
  New

Bug description:
  In auth_regex the pair of commands ACCEPT/DENY is confusing. It should
  have been either ACCEPT/REJECT  (see iptables) or ALLOW/DENY (see
  apache httpd). My proposal is to make it ALLOW/DENY.

  The fix should of course be backward compatible and still also support
  ACCEPT/DENY, but documentation should mark this usage as deprecated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/drizzle/+bug/931917/+subscriptions