On Tue, May 31, 2011 at 12:44, Asia wrote:
>
>
> W dniu 2011-05-31 11:09:10 użytkownik Magnus Hagander
> napisał:
>> On Tue, May 31, 2011 at 10:06, Craig Ringer
>> wrote:
>> > On 31/05/11 15:40, Asia wrote:
>> >
>> >> Would you please advise what I am doing wrong? Or maybe there is other
>> >
On Tue, May 31, 2011 at 10:06, Craig Ringer wrote:
> On 31/05/11 15:40, Asia wrote:
>
>> Would you please advise what I am doing wrong? Or maybe there is other way
>> to generate wildcard certificate ? Or maybe this is a possible bug?
>
> I wouldn't be surprised if libpq didn't support wildcard c
On 31/05/11 15:40, Asia wrote:
> Would you please advise what I am doing wrong? Or maybe there is other way to
> generate wildcard certificate ? Or maybe this is a possible bug?
I wouldn't be surprised if libpq didn't support wildcard certificates at
all. I doubt there's ever been any demand for
Hi,
I am trying to generate self-signed certificate for full ssl authentication. I
need to have universal version of this certificate for development purposes (so
any client can connect with any postgresql server with ssl on and verify-full
flag).
I am using IP while connecting, I mean host=.
On 05/30/2011 03:58 PM, Asia wrote:
Would you please advise what I am doing wrong? Or maybe there is other way to
generate wildcard certificate ?
I wouldn't be surprised if libpq didn't support wildcard certificates at
all. I doubt there's ever been any demand for them.
Have you checked in
Hi,
I am trying to generate self-signed certificate for full ssl authentication. I
need to have universal version of this certificate for development purposes (so
any client can connect with any postgresql server with ssl on).
I am using IP while connecting, I mean host=.
However verify-full co
