all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Rutger Helling <rhelling@mykolab.com>
To: "Clément Lassieur" <clement@lassieur.org>
Cc: 29295@debbugs.gnu.org
Subject: [bug#29295] [PATCH] Few small patches for messaging.
Date: Sun, 26 Nov 2017 10:07:57 +0100	[thread overview]
Message-ID: <b81fdd033446dd9ef751caedf83ccc6e@mykolab.com> (raw)
In-Reply-To: <873752z6h2.fsf@gnu.org>

Thanks for all the additional work Clément!

On 2017-11-25 17:08, ludo@gnu.org wrote:

> Clément Lassieur <clement@lassieur.org> skribis:
> 
>> Ludovic Courtès <ludo@gnu.org> writes:
> 
> [...]
> 
> OK, it does sound like a Freetalk issue, in which case we should just 
> go
> ahead and update Prosody, and report the issue to bug-freetalk@gnu.org.
> 
> Clément, any ideas?
> I sent two patches that fix the issue, see
> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=29433.
> 
> This happened because Prosody removed DIGEST-MD5 auth mechanism since
> 0.10 (see https://prosody.im/doc/modules/mod_saslauth).  The other one
> (SCRAM-SHA-1) seems to be unsupported by Freetalk.

Oh, good catch.  Thank you!

Ludo'.

  reply	other threads:[~2017-11-26  9:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14 14:26 [bug#29295] [PATCH] Few small patches for messaging Rutger Helling
2017-11-14 15:52 ` ng0
2017-11-14 17:55   ` Rutger Helling
2017-11-16 10:10   ` Rutger Helling
2017-11-19 22:42     ` Ludovic Courtès
2017-11-21  8:20       ` Rutger Helling
2017-11-21  8:42         ` Ludovic Courtès
2017-11-21  8:56           ` Rutger Helling
2017-11-24 18:29           ` Clément Lassieur
2017-11-24 23:01           ` Clément Lassieur
2017-11-25 16:08             ` Ludovic Courtès
2017-11-26  9:07               ` Rutger Helling [this message]
2017-11-26 14:44                 ` Clément Lassieur
2017-12-01 10:21       ` bug#29295: " Ludovic Courtès

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=b81fdd033446dd9ef751caedf83ccc6e@mykolab.com \
    --to=rhelling@mykolab.com \
    --cc=29295@debbugs.gnu.org \
    --cc=clement@lassieur.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.