On 13 Dec 2010, at 11:46, Simon Tennant (buddycloud) wrote:
On 13/12/2010 12:39, Christoph Terwelp wrote:
XEP-0070 doesn't solve this problem because it only handles
authentication of a client to a server. Here a authentication at
the xmpp server itself is required but without showing the
On 16 Jan 2009, at 13:02, Tomasz Sterna wrote:
Dnia 2009-01-15, czw o godzinie 17:21 +0100, Robin Redeker pisze:
I've received a bugreport for my Perl module AnyEvent::XMPP recently,
that says that I should not pass the domain of the JID as service
hostname
to SASL (and later the GSSAPI
On 15 Jan 2009, at 17:19, Peter Saint-Andre wrote:
AFAIK, no servers implement that yet, and in any case it was designed
for a slightly different use case (basically situations in which DNS
SRV
results don't tell you the hostname of the connection manager you're
talking to because load
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd like to see support for SASL EXTERNAL.
This is a fairly trivial change to JSJaC, but it allows some pretty
cool things to be done in the HTTP Binding proxy. Basically, you can
use authentication tokens exchanged at the HTTP layer during the
On 26 Jul 2006, at 08:25, Remko Troncon wrote:
On 26 Jul 2006, at 9:15, Matthias Wimmer wrote:
Cool. I'd like to see this SASL feature having more widespread
support in Jabber implementations.
I agree on the server side.
Just to add - I've got patches implementing this feature for
