From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Alexey Klyukin <alexk(at)hintbits(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: implement subject alternative names support for SSL connections |
Date: | 2014-07-25 17:20:32 |
Message-ID: | CABUevEyCK=-S0p4+G6UFZ3AB6iyfn1BmF_sgoMfO5TtNrpsDGw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Jul 25, 2014 at 7:15 PM, Alexey Klyukin <alexk(at)hintbits(dot)com> wrote:
> On Fri, Jul 25, 2014 at 6:34 PM, Magnus Hagander <magnus(at)hagander(dot)net>
> wrote:
>>
>>
>> I just took a very quick look at the code, and just noticed one thing:
>>
>> Why keep looping once you've found a match? When you set result=true
>> you should break; from the loop I think. Not necessarily for
>> performance, but there might be something about a different extension
>> we can't parse for example, no need to fail in that case.
>
>
>
> The for loop header is for (i = 0; i < alt_names_total && !result; i++), so
> the loop
> should terminate right when the result becomes true, which happens if the
> pg_strcasecmp
> finds a match between the given dNSName and the name supplied by the client.
oh, ha. So yeah, that was too quick to count as a review - clearly :)
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2014-07-25 18:11:32 | pg_background (and more parallelism infrastructure patches) |
Previous Message | Alexey Klyukin | 2014-07-25 17:15:27 | Re: implement subject alternative names support for SSL connections |