I don't know which Mono.security.dll to use.

In the past we had trouble with this library.

There was this problem:
http://pgfoundry.org/tracker/index.php?func=detail&aid=1000674&group_id=
1000140&atid=590
which caused the client to hang (endless loop or similar).

The solution was to use a different Mono.secutity.dll
(http://npgsql.projects.postgresql.org/Mono.Security.dll.zip)

We are in the process of distributing PostgreSQL 8.2.4 in our
company and use the MSI binary package from postgresql.org.

Now I notice that the Mono.security.dll distributed with the
MSI has the same version (1.0.5000.0) as the one from the link
above, but the file sizes and checksums are different.

The one from the MSI package has a link timestamp of
April 15, 2005, while the above one is from July 14, 2006.
The age (2005!) makes me fear that the bug is not fixed in this DLL.

I checked with the versions available for download from
mono-project.org and found that they all have the SAME version,
but DIFFERENT link dates and sizes.

- How can anybody keep track of the different Mono.security.dlls
  when they all have the same version?

- Which Mono.security.dll should I use to avoid the bug above?

- Is there any version of Mono.security.dll that does not suffer from
  http://bugzilla.ximian.com/show_bug.cgi?id=78597

- If this is the wrong place to ask all this, where should I go?

Just for the record, here's a list of all Mono.security.dlls I
have found:

origin                   | DLL version | link timestamp | size (bytes)
-------------------------+-------------+----------------+--------------
PostgreSQL 8.2.4 MSI     | 1.0.5000.0  |   2005-04-15   | 255488
above link               | 1.0.5000.0  |   2006-07-14   | 278528
Mono 1.1.13.8.2 download | 1.0.5000.0  |   2006-12-07   | 273920
Mono 1.2.4 download      | 1.0.5000.0  |   2007-05-14   | 281088

Yours,
Laurenz Albe
_______________________________________________
Npgsql-general mailing list
Npgsql-general@gborg.postgresql.org
http://gborg.postgresql.org/mailman/listinfo/npgsql-general

Reply via email to