-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 In the replacement for RFC 3920, DIGEST-MD5 will be replaced by SCRAM, so start working on those SCRAM implementations. ;-)
http://tools.ietf.org/html/draft-ietf-sasl-scram However, I am sure that DIGEST-MD5 will be supported for backward compatibility many years into the future... On 11/9/09 10:24 PM, Sebastiaan Deckers wrote: > Replying to an old message as I just faced a similar issue and want to > document/discuss the solution. > > Both RFC2831 (Digest SASL) and RFC3920 (XMPP Core) do not specify what > the realm should be treated as by the client if it is missing from the > challenge. > > Treating the missing realm as an empty string is how it seems to work > with existing servers. This is also implied in RFC3920bis (draft 09 > #7.2.7 Realms). > > Sebastiaan > > > On Sun, Mar 22, 2009 at 4:28 PM, Dieter Lunn <[email protected] > <mailto:[email protected]>> wrote: > > What is the preferred course of action when the client doesn't receive > a realm from the server in an SASL challenge? > > Dieter Lunn > http://www.coder2000.ca -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkr4dekACgkQNL8k5A2w/vzssACfXEs2hyw6zRrn59fPsXBSIeUk 0IEAoJP3HD6TrE8FnhVsl35C6sPQFeWQ =rHtU -----END PGP SIGNATURE----- _______________________________________________ JDev mailing list Forum: http://www.jabberforum.org/forumdisplay.php?f=20 Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________
