linux-traipu team mailing list archive

[Henrik Ingo <henrik.ingo@xxxxxxxxxxxxx>]

Is there a commit missing? Everything looks fine but I don't see that
t/basic.policy would have changed as you claim.

A few comments on the docs:

Important: These docs are published on docs.drizzle.org and the same
manual should cover all versions of Drizzle. So you must write something
like:

In Drizzle 7 and Drizzle 7.1 the action words ACCEPT and DENY were used.
Beginning with Drizzle 7.2.0 [yeah, I'm assuming this is the version
where this code is published, but you would of course update it if it is
not merged as expected] you should use ALLOW and DENY, but also ACCEPT
and REJECT are supported for backward compatibility.

[Then continue with examples using ALLOW/DENY as you now do.]

You could remove the Examples section completely. Since the "Regex
Policy File Format" does contain an example, there is no need to
apologize.

-- 
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