Re: SigningTable (was: SigingTable)

From: SM <sm_at_resistor.net>
Date: Sun, 21 Feb 2010 23:35:29 -0800

Hi Murray,
At 22:53 21-02-10, Murray S. Kucherawy wrote:
>Depends on what format you're using. For flat files, it's spaces, like so:
>
> foo bar
>
>"foo" would be the key, "bar" would be the value. The separation is
>pretty obvious for DB, LDAP and SQL types. For regex files, the format is:
>
> pattern:value
>
>I suppose we can expect not to have spaces in patterns, so we could
>change the colon as separator to a space if people think that makes more sense.
>
>The specifics are spelled out in the opendkim(8) man page where it
>talks about "DATA SETS".

Both "file:" and "refile:" refer to file-based storage. It is not
intuitive to have two different separators (between KEY and
VALUE. "file:" uses whitespace-separated values. "refile:" uses
everything after the colon as the value to be used. We have
separators between KEY and VALUE and separators between the different values.

The question is whether we want the separator between KEY and VALUE
to be different from a VALUE that has multiple values. As DB uses
colons to separate the multiple values, we might want to keep
that. There is an assumption that we will never have a colon in a
value, e.g. host:port.

We could have whitespaces (and TAB) as a separator between KEY and
VALUE. In your regex file example, I consider "pattern" as a KEY even
though it is a regex.

Regards,
-sm
Received on Mon Feb 22 2010 - 07:35:56 PST