Let's complete this table, then we can change the code:
http://sites.google.com/site/djabberd/dialback-auth-problems
Email me (privately if you'd like) your Google account email address (which
might be a non-gmail.com address) and I'll give you edit access to that
site.
On Sat, Jan 31, 2009 at 5:44 PM, Piers Harding pi...@ompka.net wrote:
Do you know what the google server is? Is it OpenFire (I don't know -
probably not as it is unlikely to cope with what they do - or maybe it
does?).
I made the proposal to garner response from the list - no one responded.
Maybe you could start by commenting on what serves you know don't
require the change, in an effort to try issolating the problem.
For instance - EJabberd doesn't appear to give any trouble.
Cheers,
Piers harding.
On Sat, Jan 31, 2009 at 05:33:16PM -0800, Brad Fitzpatrick wrote:
Let's suppose this patch is committed. Yes, it then works with Google.
And
then which server do we break as a result?
We need a patch which somebody has tried with many servers and if
necessary
auto-detects when that hack is required vs. when it's not. Or let's
check
it in guarded, off by default, but with a config opt/flag to enable it.
Then when people report bugs in the future with the new behavior we can
say
but does it work with FooOpt enabled?. And then we'll have data on a
server that's required to do that for and eventually end up with a good
solution.
But I'm not a fan of all these patch proposals like well deleting this
works for me because that's not a comprehensive solution.
Can somebody research this more?
On Fri, Jan 30, 2009 at 11:08 PM, Piers Harding pi...@ompka.net wrote:
Hi -
I've reported this problem before, with openfire servers - it just
started happening to me a couple of months back.
I was kind of hoping someone with commit access would remove the
problem
code.
Cheers,
Piers Harding.
On Fri, Jan 30, 2009 at 06:16:15PM -0800, Gordon Irlam wrote:
Hi,
I've been having difficulties getting my DJabberd to federate with
gmail.com. It federates fine with jabber.com.
I've attached a packet trace at the end of this email, but it seems
the problem is caused by the following code in
Connection/ServerOut.pm:
if ($ss-version-supports_features) {
# they can eat a dick for all we care. they get no features.
# what is this weird XMPP 1.0 + old-school Dialback world
anyway?
# maybe we're still confused. FIXME: care.
my $features = stream:features/stream:features;
$self-write($features);
$self-log-debug($self-{id} sending '$features');
}
Deleting this code allows my DJabberd to federate with Google.
This is my first tweak to DJabberd, so I wanted to check if it is
safe
to delete this code, or are there gremlins I don't understand.
Also, is this really a Google problem? Should I follow up with them
too?
thanks,
Gordon
-
myserver.32838 wf-in-f125.google.com.xmpp-server:
?xml version=1.0 encoding=UTF-8?stream:stream to='gmail.com'
xmlns:stream='http://etherx.jabber.org/streams'
xmlns='jabber:server'
xml:lang='en' xmlns:db='jabber:server:dialback' version='1.0'
wf-in-f125.google.com.xmpp-server myserver.32838:
?xml version=1.0 encoding=UTF-8?stream:stream from=gmail.com
id=0A8E5AD27E429B7E version=1.0
xmlns:stream=http://etherx.jabber.org/streams;
xmlns=jabber:server
xmlns:db=jabber:server:dialback
wf-in-f125.google.com.xmpp-server myserver.32838:
stream:featuresdialback
xmlns=urn:xmpp:features:dialback//stream:features
myserver.32838 wf-in-f125.google.com.xmpp-server:
stream:features/stream:features
wf-in-f125.google.com.xmpp-server myserver.32838:
stream:errornot-authorized
xmlns=urn:ietf:params:xml:ns:xmpp-streams//stream:error
--
Home - http://www.piersharding.com
xmpp:pi...@ompka.net xmpp%3api...@ompka.net
xmpp%3api...@ompka.netxmpp%253api...@ompka.net
--
Home - http://www.piersharding.com
xmpp:pi...@ompka.net xmpp%3api...@ompka.net
