| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Alexey Klyukin <alexk(at)hintbits(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Wildcard usage enhancements in .pgpass |
| Date: | 2013-12-06 21:56:44 |
| Message-ID: | 52A2481C.1030905@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/17/13, 1:56 PM, Martijn van Oosterhout wrote:
> Looks interesting, though I wonder if you could use fnmatch(3) here. Or
> woud that match more than you expect? For example, it would allow
> 'foo*bar' to match 'foo.bar' which your code doesn't.
The question is whether you'd want that.
We had previously considered using fnmatch() for wildcard matching of
host names in certificates and ended up deciding against that. It would
be worth checking that old thread. It would also be good if the pgpass
wildcard matching were somehow consistent with certificates, since they
are both somewhat related security features.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2013-12-06 21:58:05 | Re: WITHIN GROUP patch |
| Previous Message | Andrew Gierth | 2013-12-06 21:51:25 | Re: WITHIN GROUP patch |