pg.ddx.io  pgadmin-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Guillaume Lelarge <guillaume@lelarge.info>
To: Magnus Hagander <magnus@hagander.net>
Cc: pgadmin-hackers@postgresql.org
Subject: Re: Patch to support SSL certificate connections
Date: Thu, 27 Jan 2011 22:56:05 +0100
Message-ID: <4D41E9F5.6000808@lelarge.info> (raw)
In-Reply-To: <4D3A2609.2040406@lelarge.info>
References: <4D3623DB.20105@lelarge.info>
	<4D38B269.6000509@lelarge.info>
	<AANLkTikQAQPo9acQt39x4WGbmyPO7M-Cs9FF6AxRTMOC@mail.gmail.com>
	<4D3A2609.2040406@lelarge.info>

Le 22/01/2011 01:34, Guillaume Lelarge a écrit :
> Le 21/01/2011 10:17, Magnus Hagander a écrit :
>> On Thu, Jan 20, 2011 at 23:08, Guillaume Lelarge <guillaume@lelarge.info> wrote:
>>> Le 19/01/2011 00:35, Guillaume Lelarge a écrit :
>>>> Hi,
>>>>
>>>> This patch adds support to specify SSL certificate files and to connect
>>>> according to those.
>>>>
>>>> It's pretty straightforward: four file pickers to handle on dlgServer,
>>>> and changes in the connection code to add those parameters in the
>>>> connection string.
>>>>
>>>
>>> A screenshot attached so that you can see the UI without building pgAdmin :)
>>>
>>> Comments?
>>
>> I would move root cert up before the others. Also CRL.
>>
>> Root cert and CRL are about validating the *server* certificate. Key
>> and cert file are about SSL authentication of the *client* (thus
>> *client* certificates). They should definitely be in that order -
>> perhaps even grouped with a headline?
>>
> 
> Done for moving widgets. Not sure grouped widgets could make sense here.
> 

Here is what I finally managed to do. Comments?


-- 
Guillaume
 http://www.postgresql.fr
 http://dalibo.com

Attachments:

sslserver.png (image/png, 37.1K) download view image

view thread (20+ messages)  latest in thread

Message-ID: <4D41E9F5.6000808@lelarge.info>
Permalink:  ../4D41E9F5.6000808@lelarge.info/
Also on:    postgresql.org/message-id/4D41E9F5.6000808@lelarge.info

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgadmin-hackers@postgresql.org
  Cc: guillaume@lelarge.info, magnus@hagander.net
  Subject: Re: Patch to support SSL certificate connections
  In-Reply-To: <4D41E9F5.6000808@lelarge.info>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox