From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Dave Page <dpage(at)pgadmin(dot)org> |
Cc: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: Support for sslverify |
Date: | 2009-03-16 18:31:11 |
Message-ID: | 49BE9AEF.6000503@hagander.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Dave Page wrote:
> On Mon, Mar 16, 2009 at 2:35 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> Dave Page wrote:
>>> On Mon, Mar 16, 2009 at 1:57 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>>> - There doesn't seem to be any way to push the verify mode down to the
>>> backup/backupall/backupglobals/restore dialogues, or to the debugger
>>> (which, annoyingly, still has it's own connection class). Do we want
>>> to re-verify in those places, or just set verify=none, as we've
>>> already verified at initial connection? I guess in theory a mitm
>>> attack could start after we initially connect.
>> Ick. I'll need to look into that. We must absolutely verify every
>> connection, anything else is very stupid.
This look better?
(I haven't actually tested the backup stuff :-P But it builds..)
I also noticed we have windows linebreaks in at least one file in the
debugger directory...
//Magnus
Attachment | Content-Type | Size |
---|---|---|
pgadmin_sslverify2.patch | text/x-diff | 30.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | svn | 2009-03-16 19:46:55 | SVN Commit by dpage: r7711 - trunk/pgadmin3/pgadmin |
Previous Message | Guillaume Lelarge | 2009-03-16 18:08:44 | Re: pgAdminIII 1.10 Visual Tour |