[jadmin] Help needed with certificate problem / Pidgin

[Christoph Willing]

On 05/05/2008, at 11:21 PM, Matthias Wimmer wrote:

> Hi Christoph!
>
>
> The patch I used should work against the vanilla 1.6.1.1 code as well.
> (http://permalink.gmane.org/gmane.network.jabber.xmppd.devel/151)
>
> If you take the repository code, please make sure, that you use the
> 1.6.1 branch (http://svn.jabberd.org/branches/RELEASE-1_6_1/) and  
> not trunk.
>
> The changes in the 1.6.1 branch are moderate, just some added
> functionality for a customer of mine to be able to dynamically and and
> remove domains from the session manager. - While in trunk there are
> really heavy changes that also break the programming API transforming
> jabberd to a more OOP design.


Thanks Matthias,

I initially used the trunk code which, as you say, is very heavily  
modified. I'll just apply the minimal patch to vanilla 1.6.1.1 code  
for now.


chris



> Christoph Willing schrieb:
>> On 05/05/2008, at 8:50 PM, Matthias Wimmer wrote:
>>
>>> Hi Christoph!
>>>
>>> Christoph Willing schrieb:
>>>> I'm not sure if this is related to your problem with Pidgin's TLS
>>>> error, but maybe.
>>>>
>>>> For sometime, I've been building/using jabberd14-1.6.1.1 without
>>>> problems. Recently, the distribution I use has had a new release in
>>>> which the gnutls version jumped from 1.6.2 to 2.2.2; since then I
>>>> can't compile jabberd14 any more. The reason is that the signature
>>>> for the gnutls_certificate_set_openpgp_key_file() function has
>>>> changed and so compilation fails during mio_tls.cc (line 634).
>>>>
>>>> Could you consider providing a new jabberd14 release which uses the
>>>> new function definition for gnutls_certificate_set_openpgp_key_file
>>>> ()? I imagine most Linux distributions will be using the newer  
>>>> gnutls
>>>> soon and all will face the same problem.
>>> This should be unrelated. The fix you are asking for is available
>>> in the
>>> jabberd14 repository.
>>
>>
>> Thanks for the fast fix Matthias! It all compiles nicely now.
>>
>> I see in the svn repository Changelog that there have been numerous
>> other changes since the 1.6.1.1 tarball release which I've been using
>> till now. I'm a bit concerned about introducing so many changes from
>> svn code into a production server. In this situation, would you
>> recommend using _all_ the new code from svn, or is it possible to add
>> only the new code in mio_tls.cc into the 1.6.1.1 version?
>>
>>
>> chris
>>
>>
>>
>> Christoph Willing                        +617 3365 8350
>> QCIF Access Grid Manager
>> University of Queensland
>>
>>
>>
>>
>> _______________________________________________
>> JAdmin mailing list
>> JAdmin at jabber.org
>> http://mail.jabber.org/mailman/listinfo/jadmin
>> FAQ: http://www.jabber.org/about/jadminfaq.shtml
>> _______________________________________________
> _______________________________________________
> JAdmin mailing list
> JAdmin at jabber.org
> http://mail.jabber.org/mailman/listinfo/jadmin
> FAQ: http://www.jabber.org/about/jadminfaq.shtml
> _______________________________________________

Christoph Willing                        +617 3365 8350
QCIF Access Grid Manager
University of Queensland