[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [xmpp] SASL errors in 3920bis-03

From: Tobias Markmann <tmarkmann at googlemail.com>
To: Philipp Hancke <fippo at mail.symlynx.com>
Cc: xmpp at ietf.org
Date: Tue, 17 Nov 2009 10:35:29 +0100
In-reply-to: <Pine.LNX.4.64.0911171027480.18128 at lectern.tobij.de>
References: <5cfc0a8e0911161126ha0d3f1eobfb8216f929a8fab at mail.gmail.com> <4B025638.6090101 at isode.com> <Pine.LNX.4.64.0911171027480.18128 at lectern.tobij.de>

On Tue, Nov 17, 2009 at 10:28 AM, Philipp Hancke <fippo at mail.symlynx.com> wrote:

If stream:from is set, the servers knows the users jid before offering the list of mechanisms and should not offer any weak mechanisms.

Exactly this was my thinking. Dumb client, why are you selecting a mechanism that hasn't been advertised. ;)

Sure if during usage of PLAIN or DIGEST-MD5 the server receives the username and decides this mechanism is too weak one could reply with a mechanism-too-weak error but the process with having to know stream:from is way cleaner.

Cheers,
Tobias

--
Tobias Markmann
http://ayena.de

Follow-Ups:
- Re: [xmpp] SASL errors in 3920bis-03
  - From: Dave Cridland

References:
- [xmpp] SASL errors in 3920bis-03
  - From: Tobias Markmann
- Re: [xmpp] SASL errors in 3920bis-03
  - From: Alexey Melnikov
- Re: [xmpp] SASL errors in 3920bis-03
  - From: Philipp Hancke

Prev by Date: Re: [xmpp] SASL errors in 3920bis-03
Next by Date: Re: [xmpp] SASL errors in 3920bis-03
Previous by thread: Re: [xmpp] SASL errors in 3920bis-03
Next by thread: Re: [xmpp] SASL errors in 3920bis-03
Index(es):
- Date
- Thread

Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.