I was writing up the manpage update for exports to include info about
IPv6 addressing, and made a mistake on my first pass. I put the IPv6
address in brackets. It turned out that this worked because mountd
treats stuff in brackets as a character class wildcard match.
This behavior is undocumented in the manpage and it doesn't seem to
work correctly, but it's hard to be sure as I'm not sure what correct
behavior is for this.
For instance, I have a host with a valid hostname (tlielax) in DNS on
my subnet, and when I put this in /etc/exports:
/export [whiskeytangofoxtrot](rw)
...mountd allowed me to mount that. Normally a character class like
that should only match if you had a single-character hostname that
matches one of the characters in the brackets.
My question is -- do we want to continue to allow this sort of wildcard
match in mountd? Given that it's not documented, it's hard to imagine
anyone relying on it.
If we do want to keep it, what's the behavior we should be shooting for
here?
Thoughts?
--
Jeff Layton <jlayton@xxxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
