[Bug 39057] Can't connect to Oracle Jabber server

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=39057

--- Comment #15 from Malte Starostik <malte at malte.homeip.net> ---
(In reply to comment #14)
> Just to confirm, your domain is not in fact privacy-cm.uc-cup2?

No, that is not the domain.  However, uc-cup2 is the (unqualified) name of the
server I'm connected to.  To be more precise _jabber-client._tcp.domain
SRV-resolves to uc-cup1.domain and uc-cup2.domain.  Only "domain" is not
literally "domain", but consistently refers our real domain name wherever I
mentioned it.

> The spoofing check is correct to reject this: this reply is
> indistinguishable from an unrelated XMPP user('s server) doing something
> malicious. We don't have any way to know that stanzas claiming to be from
> privacy-cm.uc-cup2 (whatever that is) are valid replies to a stanza that was
> (implicitly) sent to user at domain.

So, uc-cup2 is the home server but the privacy-cm. prefix entered the stage
just here.

> (If our own full JID is user at domain/resource, then omitting the 'to' on a
> stanza is meant to be exactly equivalent to setting to='user at domain' - we're
> asking our own "home" server to handle the stanza on our behalf.)

I can see how this is correct.  Still this apparently breaks logging in to
Cisco's presence server.  Well, if that's against the spec, they should
probably know better given this statement:

"Cisco Unified Presence supports standards-based XMPP to enable third-party
XMPP client applications to integrate with Cisco Unified Presence for
availability and instant messaging (IM) services. Third-party XMPP clients must
comply with the XMPP standard as outlined in the Cisco Software Development Kit
(SDK)."

http://www.cisco.com/en/US/docs/voice_ip_comm/cups/8_0/english/install_upgrade/deployment/guide/dgXMPPclient.html

But then there are certainly funnier things to do than convince them of this
being a bug in their server - let alone actually geting a fixed version. 
Therefore a workaround would be much appreciated - especially as other clients
can do this.

If I parse that log correctly, this is only about creating an invisible list? 
So maybe this error could at least gracefully lead to disabling this feature or
the likes?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.