comparison ChangeLog @ 30065:fc4bacb35cbc

nss: NSS should work after reiniting libpurple. Closes #11524.
author Paul Aurich <paul@darkrain42.org>
date Thu, 01 Apr 2010 06:51:04 +0000
parents df9de37e0274
children f93f0ff8811d
comparison
equal deleted inserted replaced
30064:df9de37e0274 30065:fc4bacb35cbc
7 * Using the --disable-nls argument to configre now works properly. You 7 * Using the --disable-nls argument to configre now works properly. You
8 will no longer be forced to have intltool to configure and build. 8 will no longer be forced to have intltool to configure and build.
9 * Fix two related crashes in the GnuTLS and NSS plugins when they 9 * Fix two related crashes in the GnuTLS and NSS plugins when they
10 suffer internal errors immediately upon attempting to establish 10 suffer internal errors immediately upon attempting to establish
11 an SSL connection. 11 an SSL connection.
12 * Fix NSS to work when reinitialized after being used. (Thanks to
13 Ludovico Cavedon for the testcase)
12 * Added support for PURPLE_GNUTLS_PRIORITIES environment variable. 14 * Added support for PURPLE_GNUTLS_PRIORITIES environment variable.
13 This can be used to specify GnuTLS priorities on a per-host basis. 15 This can be used to specify GnuTLS priorities on a per-host basis.
14 The format is "host=priority;host2=priority;...". The default 16 The format is "host=priority;host2=priority;...". The default
15 priority can be overridden by using "*" as the host. See the 17 priority can be overridden by using "*" as the host. See the
16 GnuTLS manual for documentation on the format of the priority 18 GnuTLS manual for documentation on the format of the priority