SEO

1.) I went to the OpenSSL ste, and tried to download opnSSL, but I only
saw Linux files. Is OpenSSL supported ni Windows?

2.) I am using the Npgsql.NET data provider to connect, but it doesn't
support SSL yet, when will it support SSL?



Thanks

> 1.) I went to the OpenSSL ste, and tried to download
> opnSSL, but I only saw Linux files. Is OpenSSL supported ni Windows?

Yes. They do a good job of hiding their binaries thouhg. You can get
them from http://www.openssl.org/related/binaries.html.


> 2.) I am using the Npgsql.NET data provider to connect,
> but it doesn't support SSL yet, when will it support SSL?

AFAIK, it does, an dhas for quite long. That's why you need a
Mono.Security DLL file, included in the binary package of npgsql.

//Magnus

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Greg Quinn wrote:
> 1.) I went to the OpenSSL ste, and tried to download opnSSL, but I
> only saw Linux files. Is OpenSSL supported ni Windows?

http://www.openssl.org/related/binaries.html

>
> 2.) I am using the Npgsql.NET data provider to connect, but it
> doesn’t support SSL yet, when will it support SSL?

You should ask this on the Npgsql.Net projects mailing list.

Joshua D. Drake


>
>
>
> Thanks
>
>
>


--

=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/



---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Greg Quinn wrote:
> 1.) I went to the OpenSSL ste, and tried to download opnSSL, but I
> only saw Linux files. Is OpenSSL supported ni Windows?
>
> 2.) I am using the Npgsql.NET data provider to connect, but it
> doesn’t support SSL yet, when will it support SSL?
>
>
>
> Thanks
>
>
>
Yes, it works on win32 and you can use the two dlls that are included
with any of the GUI clients out there or the ones that come with the
win32 build of Postgresql.

You will need to copy the two dlls (ssleay32.dll,libeay32.dll) to the
same directory where you have your npgsql.net assembly.
You could also put them in your system32 directory, but this will cause
all applications to use those copies which could cause problems.

MS changed the way the DLL search works in later SPs of windows 2000 and
XP. It always checks the system32 directory first, then the application
directory and this is opposite of how it used to work. Before it always
checked the app directory first, and this was nice because you could
always include your one copies of the DLLs to make sure your app always
had the correct version, but some stupid malware writer used this to
their advantage and MS had to make the change.

--
Tony Caduto
AM Software Design
Home of PG Lightning Admin for Postgresql
http://www.amsoftwaredesign.com

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

> -----Original Message-----
> From: pgsql-general-owner@postgresql.org
> [mailtogsql-general-owner@postgresql.org] On Behalf Of Tony Caduto
> Sent: 19 June 2006 03:51
> To: Greg Quinn; pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Question about openSSL
>
> Greg Quinn wrote:
> > 1.) I went to the OpenSSL ste, and tried to download
> opnSSL, but I
> > only saw Linux files. Is OpenSSL supported ni Windows?
> >
> > 2.) I am using the Npgsql.NET data provider to connect, but it
> > doesn't support SSL yet, when will it support SSL?
> >
> >
> >
> > Thanks
> >
> >
> >
> Yes, it works on win32 and you can use the two dlls that are included
> with any of the GUI clients out there or the ones that come with the
> win32 build of Postgresql.
>
> You will need to copy the two dlls (ssleay32.dll,libeay32.dll) to the
> same directory where you have your npgsql.net assembly.
> You could also put them in your system32 directory, but this
> will cause
> all applications to use those copies which could cause problems.
>
> MS changed the way the DLL search works in later SPs of
> windows 2000 and
> XP. It always checks the system32 directory first, then the
> application
> directory and this is opposite of how it used to work.
> Before it always
> checked the app directory first, and this was nice because you could
> always include your one copies of the DLLs to make sure your
> app always
> had the correct version, but some stupid malware writer used this to
> their advantage and MS had to make the change.

Err, not quite correct. The app directory is *always* the first choice
in either safe or unsafe mode, except if using LoadLibraryEx's alternate
search order. See
http://msdn.microsoft.com/library/de.../en-us/dllproc
/base/dynamic-link_library_search_order.asp.

We rely on that to allow side-by-side PostgreSQL 8.0 and 8.1
installations on Windows. The former installed libpq et al. in the
system32 directory, whilst 8.1+ have private copies.

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

> You will need to copy the two dlls
> (ssleay32.dll,libeay32.dll) to the same directory where you
> have your npgsql.net assembly.

If we're talking npgsql (http://pgfoundry.org/projects/npgsql), that
information is incorrect. Npgsql uses a managed implementation of SSL,
so it does *not* use the OpenSSL libraries.

If we're talking some other .net dataprovider (IIRC there is at least
one other out there somewhere, though I haven't used it and can't
remember exactly what it's called), then it may or may not be using
openssl.

//Magnus

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Dave Page wrote:
>
> Err, not quite correct. The app directory is *always* the first choice
> in either safe or unsafe mode, except if using LoadLibraryEx's alternate
> search order. See
> http://msdn.microsoft.com/library/de.../en-us/dllproc
> /base/dynamic-link_library_search_order.asp.
>
> We rely on that to allow side-by-side PostgreSQL 8.0 and 8.1
> installations on Windows. The former installed libpq et al. in the
> system32 directory, whilst 8.1+ have private copies.
>
> Regards, Dave.
>
>
Well, I guess you don't need openssl with npgsql. I stand corrected.

As far as the search order goes, the link you gave does not validate the
behavior I see on my fully patched version of XP and fully patch versions
of win2k in a corp environment.

The MSDN docs are not always correct or fully updated.

--
Tony Caduto
AM Software Design
http://www.amsoftwaredesign.com
Home of PG Lightning Admin for Postgresql
Your best bet for Postgresql Administration


---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

> -----Original Message-----
> From: Tony Caduto [mailto:tony_caduto@amsoftwaredesign.com]
> Sent: 19 June 2006 14:27
> To: Dave Page
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Question about openSSL
>
> Dave Page wrote:
> >
> > Err, not quite correct. The app directory is *always* the
> first choice
> > in either safe or unsafe mode, except if using
> LoadLibraryEx's alternate
> > search order. See
> >
> http://msdn.microsoft.com/library/de...l=/library/en-
> us/dllproc
> > /base/dynamic-link_library_search_order.asp.
> >
> > We rely on that to allow side-by-side PostgreSQL 8.0 and 8.1
> > installations on Windows. The former installed libpq et al. in the
> > system32 directory, whilst 8.1+ have private copies.
> >
> > Regards, Dave.
> >
> >
> Well, I guess you don't need openssl with npgsql. I stand corrected.

<shrug>I didn't mention npgsql.

> As far as the search order goes, the link you gave does not
> validate the
> behavior I see on my fully patched version of XP and fully
> patch versions
> of win2k in a corp environment.
>
> The MSDN docs are not always correct or fully updated.

Well, before we re-hashed pgInstaller to work the way it now does,
thorough testing was undertaken on 2K, XP and 2K3, with and without
various levels of service pack and in all cases we found that the DLL in
the app dir was used over a pre-existing shared one, exactly as
documented by Microsoft. We *had* to be sure that was working correctly,
otherwise 8.1 installs would be using 8.0 DLLs and chaos would have
reigned!

You might not see it on the lists because Magnus and I tend to work via
IM on pgInstaller, but we both do significant testing using VMs running
various builds of Windows. Both of us having MSDN subscriptions make
life so much easier!

Regards, Dave.


---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Hi,

I'm using PQexecParams so I can upload filenames including path that
have '\' characters. It works everywhere else I used it but not with
this query.

I get ERROR: there is no parameter $1.

INSERT INTO FileVersionHistory(applicationID, filename, createFile,
changeSetID, userName) VALUES (1,$1::text,FALSE,9,'postgres');

outTemp[0]=deletedFiles.fileList[fileListIndex].filename;
outLengths[0]=strlen(deletedFiles.fileList[fileListIndex].filename);
formats[0]=0;
result = PQexecParams(pgConn, query,1,0,outTemp,outLengths,formats,0);

There obviously is a $1 parameter.

Ideas?

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

Kevin Jenkins <gameprogrammer@rakkar.org> writes:
> I get ERROR: there is no parameter $1.

> INSERT INTO FileVersionHistory(applicationID, filename, createFile,
> changeSetID, userName) VALUES (1,$1::text,FALSE,9,'postgres');

> outTemp[0]=deletedFiles.fileList[fileListIndex].filename;
> outLengths[0]=strlen(deletedFiles.fileList[fileListIndex].filename);
> formats[0]=0;
> result = PQexecParams(pgConn, query,1,0,outTemp,outLengths,formats,0);

> There obviously is a $1 parameter.

Hm, nothing obviously wrong there. What PG version is this exactly?
Can you supply a self-contained test case?

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match