On 6/3/2015 2:04 PM, Matthew Wild wrote:
> On 3 June 2015 at 19:40, deoren <prosody-...@whyaskwhy.org> wrote:
>> On 6/3/2015 1:39 PM, deoren wrote:
>>> These are the ciphers which were disabled via the OpenSSL library update:
>>> If nobody else is having trouble I suspect that I'm doing something odd.
>> One thing I thought of is that perhaps Dovecot (I'm using the auth module
>> for it) could be the problem here. I'll look into that and report back.
> Ah, worth chasing. Your issue is pretty strange. TLS is working at the
> XMPP level, it's just authentication failing.
> But I doubt it's a problem with the communication between Prosody and
> Dovecot, as it either uses unix sockets or plain TCP, SSL is not
> Debug logs might help.
Thanks for the reply and for the tips.
You're right about Prosody/Dovecot. The Prosody configuration is set to
use the unix socket to communicate with Dovecot.
I had more time today to look into this, so I proceeded to install the
latest patches and then reboot the box to return to the problematic
state I had before so I could do further troubleshooting.
Ironically I'm unable to replicate the issue. I'm happy everything is
working, but it's always worrisome when you can't nail down exactly what
was causing the issue.
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send email to firstname.lastname@example.org.
Visit this group at http://groups.google.com/group/prosody-dev.
For more options, visit https://groups.google.com/d/optout.