headers
Peter Saint-Andre | 1 Feb 21:40
Favicon

attention transport developers!

FYI, some well-known open-source developers are starting an effort to
document the closed IM protocols. Some details are here:

http://imfreedom.org/wiki/index.php/Main_Page

A discussion list is here:

http://pidgin.im/cgi-bin/mailman/listinfo/openim

Peter

--

-- 
Peter Saint-Andre
https://stpeter.im/
Attachment (smime.p7s): application/x-pkcs7-signature, 7338 bytes
Permalink | Reply | 0 comments |
headers
Adam Strzelecki | 4 Feb 19:57
Picon
Favicon
Gravatar

Re: Bug in jabberd2 (2.1.13) on win32

> I'm using plain auth (with and without ntlogon).  I've tested with
> Spark 2.5.8, Coccinella .96.4.1, and PSI 0.11.  All have the same
> problem, they hang or return an error when doing SASL.  I'd like to
> repeat for Thomas' sake that all three worked on the previous build
> which used Cyrus SASL.

I've tested Adium 1.2.1, Spark 2.5.8, PSI 0.11 and all of them seems  
to work without a problem with new builds both TLS and non-TLS work,  
both PLAIN and DIGEST-MD5 work too.

Please check (diff) your config XML files with new dist.xml files.  
There may be sections to upgrade in sm.xml, c2s.xml, router.xml. Your  
config may fail just because of some missing configuration or module.
Also to have working TLS you need to have valid PEM and enable it at:  
c2s.xml

<id register-enable="true"
         pemfile='server.pem'>YOURDOMAIN</id>

Cheers,
--

-- 
Adam Strzelecki |: nanoant.com :|
Permalink | Reply | 15 comments |
headers
Dan Hulme | 4 Feb 20:38
Picon

Re: Bug in jabberd2 (2.1.13) on win32

Is SASL=TLS?  Because TLS works fine.

On Feb 4, 2008 10:57 AM, Adam Strzelecki <ono <at> java.pl> wrote:
> > I'm using plain auth (with and without ntlogon).  I've tested with
> > Spark 2.5.8, Coccinella .96.4.1, and PSI 0.11.  All have the same
> > problem, they hang or return an error when doing SASL.  I'd like to
> > repeat for Thomas' sake that all three worked on the previous build
> > which used Cyrus SASL.
>
> I've tested Adium 1.2.1, Spark 2.5.8, PSI 0.11 and all of them seems
> to work without a problem with new builds both TLS and non-TLS work,
> both PLAIN and DIGEST-MD5 work too.
>
> Please check (diff) your config XML files with new dist.xml files.
> There may be sections to upgrade in sm.xml, c2s.xml, router.xml. Your
> config may fail just because of some missing configuration or module.
> Also to have working TLS you need to have valid PEM and enable it at:
> c2s.xml
>
> <id register-enable="true"
>          pemfile='server.pem'>YOURDOMAIN</id>
>
>
> Cheers,
> --
> Adam Strzelecki |: nanoant.com :|
>
>
(Continue reading)

Permalink | Reply | 14 comments |
headers
Dan Hulme | 4 Feb 21:00
Picon

Re: Bug in jabberd2 (2.1.13) on win32

When using ntlogon, I cannot get SASL to work.  Only when using TLS on
'old port', will it connect with encryption.  Turning off encryption
works as well.  I tested all this with a clean install and no changes
to the config files except the server name and realm.  I did not
realize this before, but the problems only occur with ntlogon.
However, in the old version (2.13), SASL and ntlogon worked fine.

On Feb 4, 2008 11:38 AM, Dan Hulme <dhulme <at> gmail.com> wrote:
> Is SASL=TLS?  Because TLS works fine.
>
>
> On Feb 4, 2008 10:57 AM, Adam Strzelecki <ono <at> java.pl> wrote:
> > > I'm using plain auth (with and without ntlogon).  I've tested with
> > > Spark 2.5.8, Coccinella .96.4.1, and PSI 0.11.  All have the same
> > > problem, they hang or return an error when doing SASL.  I'd like to
> > > repeat for Thomas' sake that all three worked on the previous build
> > > which used Cyrus SASL.
> >
> > I've tested Adium 1.2.1, Spark 2.5.8, PSI 0.11 and all of them seems
> > to work without a problem with new builds both TLS and non-TLS work,
> > both PLAIN and DIGEST-MD5 work too.
> >
> > Please check (diff) your config XML files with new dist.xml files.
> > There may be sections to upgrade in sm.xml, c2s.xml, router.xml. Your
> > config may fail just because of some missing configuration or module.
> > Also to have working TLS you need to have valid PEM and enable it at:
> > c2s.xml
> >
> > <id register-enable="true"
> >          pemfile='server.pem'>YOURDOMAIN</id>
(Continue reading)

Permalink | Reply | 13 comments |
headers
Adam Strzelecki | 5 Feb 00:22
Picon
Favicon
Gravatar

Re: Bug in jabberd2 (2.1.13) on win32

Hi Dan,

> When using ntlogon, I cannot get SASL to work.  Only when using TLS on
> 'old port', will it connect with encryption.  Turning off encryption
> works as well.  I tested all this with a clean install and no changes
> to the config files except the server name and realm.

Did you enable only PLAIN in c2s.xml for NTLOGON? Coz NTLOGON as  
mentioned ealier can work only with PLAIN auth.
authreg->mechanism->traditional & sasl must have only <plain/> inside.  
(Rest should be commented out for NTLOGON)

Regards,
--

-- 
Adam Strzelecki |: nanoant.com :|
Permalink | Reply | 12 comments |
headers
Dan Hulme | 5 Feb 01:29
Picon

Re: Bug in jabberd2 (2.1.13) on win32

Yeah, they both have plain only, forgot to mention that.

On Feb 4, 2008 3:22 PM, Adam Strzelecki <ono <at> java.pl> wrote:
> Hi Dan,
>
> > When using ntlogon, I cannot get SASL to work.  Only when using TLS on
> > 'old port', will it connect with encryption.  Turning off encryption
> > works as well.  I tested all this with a clean install and no changes
> > to the config files except the server name and realm.
>
> Did you enable only PLAIN in c2s.xml for NTLOGON? Coz NTLOGON as
> mentioned ealier can work only with PLAIN auth.
> authreg->mechanism->traditional & sasl must have only <plain/> inside.
> (Rest should be commented out for NTLOGON)
>
>
> Regards,
> --
> Adam Strzelecki |: nanoant.com :|
>
>
Permalink | Reply | 11 comments |
headers
Adam Strzelecki | 5 Feb 11:57
Picon
Favicon
Gravatar

Re: Bug in jabberd2 (2.1.13) on win32

Hi,

> Yeah, they both have plain only, forgot to mention that.

Then I don't really have a clue what's going on. I'm running other  
server with SASL, TLS and ntlogon and everything rock&rolls.

Do you have anything like in c2s.log:
> Tue Feb 05 11:52:44 2008 [notice] [264] [XX.XX.XX.XX, port=61371]  
> connect
> Tue Feb 05 11:52:48 2008 [notice] ntlogon: user 'ono', realm  
> 'mydomain.com' logged in
> Tue Feb 05 11:52:48 2008 [notice] [264] SASL authentication  
> succeeded: mechanism=PLAIN; authzid=ono <at> mydomain, TLS negotiated
> Tue Feb 05 11:52:48 2008 [notice] [264] bound: jid=ono <at> mydomain/macono

If not, what is the last message for your connection in the logs and  
which's missing. Maybe your ntlogon (realm) is invalid, and auth  
fails? It must be your ADS domain or hostname.

Cheers,
--

-- 
Adam Strzelecki |: nanoant.com :|
Permalink | Reply | 10 comments |
headers
Guillaume Desmottes | 5 Feb 17:05
Picon

Re: Bytestreams fallback mechanism


Le vendredi 28 décembre 2007 à 09:39 -0700, Peter Saint-Andre a écrit :
> Well of course you can define your own protocol, but I would bet that 
> other people are interested in similar functionality, so it might be 
> more productive to see if you can use Jingle and if not what gaps we 
> need to fill in Jingle so that it would work for you.

I wrote a simple scenario of transport renegotiation using Jingle.
Comments and feedback are welcome:
http://telepathy.freedesktop.org/wiki/Jingle-renegotiation

	G.

--

-- 
Guillaume Desmottes <cass <at> skynet.be>
Jabber <cassidy <at> jabber.belnet.be>
GPG 1024D/711E31B1 | 1B5A 1BA8 11AA F0F1 2169  E28A AC55 8671 711E 31B1
Permalink | Reply | 2 comments |
headers
Dan Hulme | 5 Feb 18:14
Picon

Re: Bug in jabberd2 (2.1.13) on win32

I'd be willing to consider a problem with my ntlogon configuration, if
it were not for the fact that ntlogon works fine as soon as I turn off
SASL.

Tue Feb 05 09:06:11 2008 [notice] ntlogon: user 'user', realm
'domain.com' logged in
Tue Feb 05 09:06:11 2008 [notice] [252] SASL authentication succeeded:
mechanism=PLAIN; authzid=user <at> domain.com
Tue Feb 05 09:06:11 2008 [notice] [252] bound:
jid=user <at> domain.com/Coccinella <at> domain.com-user
Tue Feb 05 09:06:11 2008 [notice] [252] [192.168.4.66, port=2837]
disconnect jid=user <at> domain.com/Coccinella <at> domain.com-user, packets: 1

At this point I am not using TLS with SASL.  TLS on a separate port
works.  For now, I am just trying to get SASL to work without TLS.  As
you can see, the authentication is working, however, the client is
disconnected immediately after.  Here is Coccinella's log:

SEND: <?xml version='1.0' encoding='UTF-8'?><stream:stream
xmlns='jabber:client' xmlns:stream='http://etherx.jabber.org/streams'
xml:lang='en' to='chatter.domain.com' version='1.0'>
RECV: <?xml version='1.0'?><stream:stream
xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client'
from='chatter.domain.com' version='1.0'
id='5zwasdfly7hlpvgcmb1wasf1231sdf86iqq8cuwd'>
RECV: <stream:features
xmlns:stream='http://etherx.jabber.org/streams'><mechanisms
xmlns='urn:ietf:params:xml:ns:xmpp-sasl'><mechanism>PLAIN</mechanism></mechanisms><auth
xmlns='http://jabber.org/features/iq-auth'/></stream:features>
SEND: <auth xmlns='urn:ietf:params:xml:ns:xmpp-sasl'
(Continue reading)

Permalink | Reply | 9 comments |
headers
Adam Strzelecki | 6 Feb 12:55
Picon
Favicon
Gravatar

Re: Bug in jabberd2 (2.1.13) on win32

Dan,

It seems your problem isn't related neither to SASL or ntlogon, nor to  
TLS. It is the "bind" command problem that fails.
I'm not sure why it fails though but it may be StorageManager that  
isn't running for your domain and which is responsible for binding  
after successful authentication.

Make sure SM is running and its sm.xml sm/id matches c2s/local/id of  
c2s.xml, checkout you got same domain and your components are  
connected to router:
 > c2s.log
> Tue Feb 05 00:17:11 2008 [notice] [mydomain.com] configured;  
> realm=mydomain.com, registration disabled
> Tue Feb 05 00:17:11 2008 [notice] connection to router established
 > sm.log
> Tue Feb 05 00:17:19 2008 [notice] id: mydomain.com

> Tue Feb 05 00:17:19 2008 [notice] connection to router established

Note that domain setting is setting used for ntlogon to indicate which  
ADS domain (or computer) should be used as auth source.

> SEND: <iq type='set' id='1007'><bind
> xmlns='urn:ietf:params:xml:ns:xmpp- 
> bind'><resource>Coccinella <at> computer</resource></bind></iq>
> RECV: <stream:error
> xmlns:stream='http://etherx.jabber.org/streams'><internal-server-error
> xmlns='urn:ietf:params:xml:ns:xmpp-streams'/><text
> xmlns='urn:ietf:params:xml:ns:xmpp-streams'>internal server
(Continue reading)

Permalink | Reply | 2 comments |

Gmane