List Info

Thread: Re: Getting connection failed in LoudMouth1.3.1




Re: Getting connection failed in LoudMouth1.3.1
country flaguser name
Sweden
2007-10-04 01:57:22
4 okt 2007 kl. 05.44 skrev <Rakesh.Harshnokia.com>:

Hi,

Looking at the log output I think it is because you are
connecting to  
the regular GMail port (that requires you use TLS) while
1.3.1 does  
not support TLS but only old style SSL. So it is in fact
failing on  
the SASL negotiation because Loudmouth doesn't support any
of the  
GMail SASL mechanisms for unencrypted connections.

You will have to connect to port 5223 at gmail in order to
use old  
style SSL.

Dafydd from Collabora have a patch for adding TLS support to
the 1.3  
branch I believe and it is existing in the 1.9 branch,
available at:

git clone git://git.imendio.com/micke/loudmouth-2.git

Cheers,
   Mikael Hallendal
> Hi
>
> I am using LoudMouth 1.3.1 version to communicate with
Gtalk.
> While running lm-sync.c exapmle I am getting connection
failed .
> Any people have any idea why this connection is failed
?(is it due  
> to TLS negotiation?)
> I have put all logs below
>
> Thanks
> Rakesh
>
>
> Linux]$ ./lm-sync -s talk.google.com -P 443 -u
testlm123gmail.com - 
> p tstlm123 -r hi -R rakesh.harshagmail.com -f --ssl -m hi
>
> *** Socket library initialising...
> *** Connecting to: talk.google.com:443
> *** SRV lookup disabled for talk.google.com
> Going to connect to proxy 172.16.42.135:443
> Trying 172.16.42.135 port 8080...
> *** Setting up SSL...
> LM-SSL: lm-ssl-openssl.c: Cipher:
TLSv1/SSLv3/DHE-RSA-AES256-SHA/256
> LmSendSync: SSL status:5
> LmSendSync: Certificate fingerprint does not match
expected  
> fingerprint!
> LmSendSync: Remote fingerprint:
FFFFFFE5:FFFFFFFD:FFFFFFA4:FFFFFFCF: 
> 43:51:60:70:12:24:32:4A:0E:FFFFFFC8:43:43
> LmSendSync: Expected fingerprint:  
> 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
> LM-SSL: lm-ssl-openssl.c: SSL_get_verify_result() = 21
> LmSendSync: SSL status:0
> LmSendSync: No certificate found!
> LM-SSL: lm-ssl-openssl.c: server = 'talk.google.com',
cn =  
> 'talk.google.com'
> LM-SSL: lm-ssl-openssl.c:
>         Issuer: /C=US/O=Equifax/OU=Equifax Secure
Certificate  
> Authority
>         Subject: /C=US/ST=California/L=Mountain
View/O=Google Inc./ 
> CN=talk.google.com
>         For: talk.google.com
>
> SEND:
> -----------------------------------
> <?xml version='1.0' encoding='UTF-8'?>
> -----------------------------------
> *** Sending stream header
>
> SEND:
> -----------------------------------
> <stream:stream version="1.0"
xmlns="jabber:client"  
> xmlns:stream="http://etherx.
jabber.org/streams" to="gmail.com"  
> id="msg_988232bf_8d6e55d8_0">
>
> -----------------------------------
>
> RECV [176]:
> -----------------------------------
> '<?xml version="1.0"
encoding="UTF-8"?><stream:stream  
> from="gmail.com"
id="02A55B611420B766" version="1.0"  
> xmlns:stream="http://etherx.
jabber.org/streams"  
> xmlns="jabber:client">'
>
> -----------------------------------
> *** Read: 176 chars
> LM-PARSER: ATTRIBUTE: from = gmail.com
> LM-PARSER: ATTRIBUTE: id = 02A55B611420B766
> LM-PARSER: ATTRIBUTE: version = 1.0
> LM-PARSER: ATTRIBUTE: xmlns:stream = http://etherx.jabber
.org/streams
> LM-PARSER: ATTRIBUTE: xmlns = jabber:client
> LM-PARSER: Trying to close node: stream:stream
> LM-PARSER: Have a new message
> *** New message with type="stream:stream"
from: gmail.com
>
> RECV [166]:
> -----------------------------------
> '<stream:features><mechanisms
xmlns="urn:ietf:paramsml:ns
mpp-

>
sasl"><mechanism>PLAIN</mechanism><me
chanism>X-GOOGLE-TOKEN</ 
>
mechanism></mechanisms></stream:features>'
>
> -----------------------------------
> *** Read: 166 chars
> LM-PARSER: ATTRIBUTE: xmlns = urn:ietf:paramsml:ns
mpp-s
asl
> LM-PARSER: Trying to close node: mechanism
> LM-PARSER: Trying to close node: mechanism
> LM-PARSER: Trying to close node: mechanisms
> LM-PARSER: Trying to close node: stream:features
> LM-PARSER: Have a new message
> *** New message with type="stream:features"
from: unknown
>
> RECV [1]:
> -----------------------------------
> ' '
> -----------------------------------
> *** Read: 1 chars
> *** XMPP 1.0 stream received: 02A55B611420B766
> LmSendSync: Could not open a connection: Opening the
connection failed
>
> _______________________________________________
> Loudmouth mailing list
> Loudmouthlists.imendio.com
> h
ttp://lists.imendio.com/mailman/listinfo/loudmouth



-- 
Imendio AB, http://www.imendio.com



_______________________________________________
Loudmouth mailing list
Loudmouthlists.imendio.com
h
ttp://lists.imendio.com/mailman/listinfo/loudmouth

Re: Getting connection failed in LoudMouth1.3.1
user name
2007-10-05 05:51:08
 Hi Mikael,

 Thanks for your reply .
 As you say "Loudmouth doesn't support any of the GMail
SASL mechanisms
for 
 unencrypted connections" Yes Gtalk is using
X-GOOGLE-TOKEN authanticate
type ans loudmouth is supporting 
 Plain text and digest authantication type.

 Do you have any plan to support X-GOOGLE-TOKEN authanticate
type or can
we use existing authanticate type 
 to connect with gtalk server?

 With Regards
 Rakesh harsh
 

 
>-----Original Message-----
>From: loudmouth-bounceslists.imendio.com 
>[mailto:loudmouth-bounceslists.imendio.com] On
Behalf Of ext 
>Mikael Hallendal
>Sent: Thursday, October 04, 2007 12:27 PM
>To: Loudmouth List
>Subject: Re: [Loudmouth] Getting connection failed in
LoudMouth1.3.1
>
>4 okt 2007 kl. 05.44 skrev <Rakesh.Harshnokia.com>:
>
>Hi,
>
>Looking at the log output I think it is because you are

>connecting to the regular GMail port (that requires you
use 
>TLS) while 1.3.1 does not support TLS but only old style
SSL. 
>So it is in fact failing on the SASL negotiation because

>Loudmouth doesn't support any of the GMail SASL
mechanisms for 
>unencrypted connections.
>
>You will have to connect to port 5223 at gmail in order
to use 
>old style SSL.
>
>Dafydd from Collabora have a patch for adding TLS
support to 
>the 1.3 branch I believe and it is existing in the 1.9
branch, 
>available at:
>
>git clone git://git.imendio.com/micke/loudmouth-2.git
>
>Cheers,
>   Mikael Hallendal
>> Hi
>>
>> I am using LoudMouth 1.3.1 version to communicate
with Gtalk.
>> While running lm-sync.c exapmle I am getting
connection failed .
>> Any people have any idea why this connection is
failed ?(is 
>it due to 
>> TLS negotiation?) I have put all logs below
>>
>> Thanks
>> Rakesh
>>
>>
>> Linux]$ ./lm-sync -s talk.google.com -P 443 -u 
>testlm123gmail.com - p 
>> tstlm123 -r hi -R rakesh.harshagmail.com
-f --ssl -m hi
>>
>> *** Socket library initialising...
>> *** Connecting to: talk.google.com:443
>> *** SRV lookup disabled for talk.google.com Going
to connect 
>to proxy 
>> 172.16.42.135:443 Trying 172.16.42.135 port
8080...
>> *** Setting up SSL...
>> LM-SSL: lm-ssl-openssl.c: Cipher:
TLSv1/SSLv3/DHE-RSA-AES256-SHA/256
>> LmSendSync: SSL status:5
>> LmSendSync: Certificate fingerprint does not match
expected 
>> fingerprint!
>> LmSendSync: Remote fingerprint:
FFFFFFE5:FFFFFFFD:FFFFFFA4:FFFFFFCF: 
>> 43:51:60:70:12:24:32:4A:0E:FFFFFFC8:43:43
>> LmSendSync: Expected fingerprint:  
>> 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00
>> LM-SSL: lm-ssl-openssl.c: SSL_get_verify_result() =
21
>> LmSendSync: SSL status:0
>> LmSendSync: No certificate found!
>> LM-SSL: lm-ssl-openssl.c: server =
'talk.google.com', cn = 
>> 'talk.google.com'
>> LM-SSL: lm-ssl-openssl.c:
>>         Issuer: /C=US/O=Equifax/OU=Equifax Secure
Certificate 
>> Authority
>>         Subject: /C=US/ST=California/L=Mountain
View/O=Google Inc./ 
>> CN=talk.google.com
>>         For: talk.google.com
>>
>> SEND:
>> -----------------------------------
>> <?xml version='1.0' encoding='UTF-8'?>
>> -----------------------------------
>> *** Sending stream header
>>
>> SEND:
>> -----------------------------------
>> <stream:stream version="1.0"
xmlns="jabber:client"  
>> xmlns:stream="http://etherx.
jabber.org/streams" to="gmail.com"  
>> id="msg_988232bf_8d6e55d8_0">
>>
>> -----------------------------------
>>
>> RECV [176]:
>> -----------------------------------
>> '<?xml version="1.0"
encoding="UTF-8"?><stream:stream 
>from="gmail.com" 
>> id="02A55B611420B766"
version="1.0"
>> xmlns:stream="http://etherx.
jabber.org/streams"  
>> xmlns="jabber:client">'
>>
>> -----------------------------------
>> *** Read: 176 chars
>> LM-PARSER: ATTRIBUTE: from = gmail.com
>> LM-PARSER: ATTRIBUTE: id = 02A55B611420B766
>> LM-PARSER: ATTRIBUTE: version = 1.0
>> LM-PARSER: ATTRIBUTE: xmlns:stream = http://etherx.jabber
.org/streams
>> LM-PARSER: ATTRIBUTE: xmlns = jabber:client
>> LM-PARSER: Trying to close node: stream:stream
>> LM-PARSER: Have a new message
>> *** New message with type="stream:stream"
from: gmail.com
>>
>> RECV [166]:
>> -----------------------------------
>> '<stream:features><mechanisms
xmlns="urn:ietf:paramsml:ns
mpp-
>>
sasl"><mechanism>PLAIN</mechanism><me
chanism>X-GOOGLE-TOKEN</
>>
mechanism></mechanisms></stream:features>'
>>
>> -----------------------------------
>> *** Read: 166 chars
>> LM-PARSER: ATTRIBUTE: xmlns = urn:ietf:paramsml:ns
mpp-s
asl
>> LM-PARSER: Trying to close node: mechanism
>> LM-PARSER: Trying to close node: mechanism
>> LM-PARSER: Trying to close node: mechanisms
>> LM-PARSER: Trying to close node: stream:features
>> LM-PARSER: Have a new message
>> *** New message with
type="stream:features" from: unknown
>>
>> RECV [1]:
>> -----------------------------------
>> ' '
>> -----------------------------------
>> *** Read: 1 chars
>> *** XMPP 1.0 stream received: 02A55B611420B766
>> LmSendSync: Could not open a connection: Opening
the 
>connection failed
>>
>> _______________________________________________
>> Loudmouth mailing list
>> Loudmouthlists.imendio.com
>> h
ttp://lists.imendio.com/mailman/listinfo/loudmouth
>
>
>
>-- 
>Imendio AB, http://www.imendio.com
>
>
>
>_______________________________________________
>Loudmouth mailing list
>Loudmouthlists.imendio.com
>h
ttp://lists.imendio.com/mailman/listinfo/loudmouth
>
_______________________________________________
Loudmouth mailing list
Loudmouthlists.imendio.com
h
ttp://lists.imendio.com/mailman/listinfo/loudmouth

[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )