Lukasz Grochal wrote:
If we're talking about the same bug, then jabberd -D (debug) should
print out something like:
Fri Feb 9 23:12:59 2007 mio_ssl.c:93 Could not create SSL Context:
error:140A90A1:SSL routines:SSL_CTX_new:library has no ciphers
Tony, Oryn...if you run jabberd with the
Yup
Tue Feb 20 21:50:23 2007 mio_ssl.c:83 Handling: key
ip='127.0.0.1'/etc/jabber/key.pem/key
Tue Feb 20 21:50:23 2007 mio_ssl.c:93 Could not create SSL Context:
error:140A90A1:SSL routines:SSL_CTX_new:library has no ciphers
David Härdeman wrote:
Lukasz Grochal wrote:
If we're talking
On Tue, Feb 20, 2007 at 09:51:51PM +, 0ryn wrote:
Yup
Tue Feb 20 21:50:23 2007 mio_ssl.c:83 Handling: key
ip='127.0.0.1'/etc/jabber/key.pem/key
Tue Feb 20 21:50:23 2007 mio_ssl.c:93 Could not create SSL Context:
error:140A90A1:SSL routines:SSL_CTX_new:library has no ciphers
Good, then
Patch applied and I'm talking jabber over ssl to my server
:)
David Härdeman wrote:
On Tue, Feb 20, 2007 at 09:51:51PM +, 0ryn wrote:
Yup
Tue Feb 20 21:50:23 2007 mio_ssl.c:83 Handling: key
ip='127.0.0.1'/etc/jabber/key.pem/key
Tue Feb 20 21:50:23 2007 mio_ssl.c:93 Could not create
I'm seeing this bug as well.
The port is open, but seems to be otherwise unresponsive. There are
no errors logged when trying to connect.
Rolling back the jabber package from 1.4.3-3.1 to 1.4.3-3 results in
the ssl port functioning again.
The relevant SSL lines from jabber.xml:
severity 405461
serious
thanks
* oryn ([EMAIL PROTECTED]) [070103 10:42]:
I'm not sure if there are any changes to config required, if there are
it would be nice if debconf warned me and even hinted on what to change.
There should be no changes required.
What does can nolonger connect mean?
Package: jabber
Version: 1.4.3-3.1
Severity: important
When I upgrade from 1.4.3-3 to 1.4.3-3.1 I can nolonger connect to my
server using ssl.
I'm not sure if there are any changes to config required, if there are
it would be nice if debconf warned me and even hinted on what to change.
--
7 matches
Mail list logo