On Fri, Jul 11, 2014 at 8:27 AM, Sandeep Thakkar < sandeep.thak...@enterprisedb.com> wrote:
> There is no change in the build script. I opened the pgAdmin.sln and see > that the PG_SSL is not defined in the Preprocessor Definitions for x64 > platform. So, the change should be made in the source code. > Oh, how'd that happen I wonder? Ashesh, can you commit a fix for that please? Thanks. > > > On Thu, Jul 10, 2014 at 4:34 PM, Sandeep Thakkar < > sandeep.thak...@enterprisedb.com> wrote: > >> Sure. Looking into it. >> >> On Wed, Jul 9, 2014 at 3:30 PM, Dave Page <dp...@pgadmin.org> wrote: >> >>> Hi >>> >>> >>> On Tue, Jul 8, 2014 at 5:23 PM, Colin Wright < >>> colin.wri...@thinkwhere.com> wrote: >>> >>>> Hi Dave, >>>> >>>> >>>> >>>> It is always either the version bundled with PG 9.3.x downloaded from >>>> http://www.enterprisedb.com/products-services-training/pgdownload#windows >>>> , or the stand-alone version from >>>> http://www.postgresql.org/ftp/pgadmin3/release/v1.18.1/win32/ >>>> >>>> >>>> >>>> When I do set up PGAdmin with a copy of the server certificate it does >>>> connect to the database OK, so at least some of the SSL functionality must >>>> be there. >>>> >>>> >>>> >>> >>> OK, I checked the MSI package and the 32 and 64 bit PG installers from >>> EDB. I see this issue on the 64bit EDB installer only - the others are all >>> OK. >>> >>> Sandeep, can you look into this ASAP please - it's behaving as if PG_SSL >>> isn't defined. >>> >>> >>> >>>> *From:* Dave Page [mailto:dp...@pgadmin.org] >>>> *Sent:* 08 July 2014 16:52 >>>> *To:* Colin Wright >>>> *Cc:* pgadmin-support@postgresql.org >>>> *Subject:* Re: [pgadmin-support] SSL Mode in PGAdmin 1.18.1 >>>> >>>> >>>> >>>> >>>> >>>> >>>> >>>> On Tue, Jul 8, 2014 at 4:42 PM, Colin Wright < >>>> colin.wri...@thinkwhere.com> wrote: >>>> >>>> Hi, >>>> >>>> I’ve been trying to set up SSL connections to our postgres databases >>>> but I’m coming across some difficulties with the way the settings are >>>> working with the latest version of PGAdmin. Can someone tell me if these >>>> are known bugs with the use of SSL in PGAdmin 1.18.1 (windows 7), and if >>>> there are any work-arounds? >>>> >>>> >>>> >>>> The SSL drop-down is empty which I assume is a bug? It had a list of >>>> options in previous versions. >>>> >>>> >>>> >>>> When I try to connect to a database that forces SSL (using a >>>> self-signed certificate) it is failing to connect because of being unable >>>> to validate the certificate. Does this mean that PGAdmin is defaulting >>>> to either “verify-ca” or “verify-all” SSL option? Is there any way of >>>> changing this to “require” instead so that I don’t need to set up the >>>> server certificate on every PC running PGAdmin (given that the drop-down >>>> doesn’t have any options)? >>>> >>>> >>>> >>>> In PGAdmin 1.18.0 and earlier there was a list of SSL settings on the >>>> properties tab of the details pane for the connection, including whether or >>>> not you were using an encrypted connection. Is this information still >>>> available somehow as it can be useful confirmation that you are using an >>>> encrypted connection? >>>> >>>> >>>> >>>> Thanks in advance for any tips and advice you can provide >>>> >>>> >>>> >>>> >>>> >>>> It sounds like your build has SSL disabled. Where did it come from? >>>> >>>> >>>> >>>> >>>> -- >>>> Dave Page >>>> Blog: http://pgsnake.blogspot.com >>>> Twitter: @pgsnake >>>> >>>> EnterpriseDB UK: http://www.enterprisedb.com >>>> The Enterprise PostgreSQL Company >>>> >>>> Colin Wright >>>> Principal Developer >>>> >>>> <http://www.thinkwhere.com> >>>> >>>> t: 01786 476060 (Office) >>>> t: 01786 476083 (Direct Dial) >>>> w:www.thinkwhere.com >>>> >>>> Glendevon House >>>> Castle Business Park >>>> Stirling FK9 4TZ >>>> <https://twitter.com/thinkWhere1> >>>> <http://www.linkedin.com/company/1509510?trk=companies_home_ycp_logo_forth-valley-gis> >>>> >>>> This email and its attachments are private and confidential. If you >>>> believe you have received this email in error, please contact the sender >>>> immediately on 01786 476060. If you are not the intended recipient, you may >>>> not rely on, use or disclose this email or any attachments in any way. >>>> >>>> thinkWhere Limited does not accept any liability for any damage that >>>> may be caused to the recipient's system or data by this email or any >>>> attachments. Please note that our email system may be subject to random >>>> monitoring by us. This Company accepts no liability for personal emails. >>>> >>>> thinkWhere is a limited company registered in Scotland with Registered >>>> Number SC315349 and having its Registered Office at Glendevon House, Castle >>>> Business Park, Stirling, FK9 4TZ. >>>> >>>> >>> >>> >>> -- >>> Dave Page >>> Blog: http://pgsnake.blogspot.com >>> Twitter: @pgsnake >>> >>> EnterpriseDB UK: http://www.enterprisedb.com >>> The Enterprise PostgreSQL Company >>> >> >> >> >> -- >> Sandeep Thakkar >> Senior Software Engineer >> >> >> Phone: +91.20.30589505 >> >> Website: www.enterprisedb.com >> EnterpriseDB Blog: http://blogs.enterprisedb.com/ >> Follow us on Twitter: http://www.twitter.com/enterprisedb >> >> This e-mail message (and any attachment) is intended for the use of the >> individual or entity to whom it is addressed. This message contains >> information from EnterpriseDB Corporation that may be privileged, >> confidential, or exempt from disclosure under applicable law. If you are >> not the intended recipient or authorized to receive this for the intended >> recipient, any use, dissemination, distribution, retention, archiving, or >> copying of this communication is strictly prohibited. If you have received >> this e-mail in error, please notify the sender immediately by reply e-mail >> and delete this message. >> > > > > -- > Sandeep Thakkar > Senior Software Engineer > > > Phone: +91.20.30589505 > > Website: www.enterprisedb.com > EnterpriseDB Blog: http://blogs.enterprisedb.com/ > Follow us on Twitter: http://www.twitter.com/enterprisedb > > This e-mail message (and any attachment) is intended for the use of the > individual or entity to whom it is addressed. This message contains > information from EnterpriseDB Corporation that may be privileged, > confidential, or exempt from disclosure under applicable law. If you are > not the intended recipient or authorized to receive this for the intended > recipient, any use, dissemination, distribution, retention, archiving, or > copying of this communication is strictly prohibited. If you have received > this e-mail in error, please notify the sender immediately by reply e-mail > and delete this message. > -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
