search

bupt-william / libjingle

Automatically exported from code.google.com/p/libjingle
0 stars 0 forks source link

how can i use libjingle connect to my own xmpp server #250

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. i have a xmpp server(openfire)
2. do call.exe --d -protocol jingle --s 192.168.1.118
   JID:user@myserver.com
   password:

What is the expected output? What do you see instead?
 ContinueSSL
 InitializeSecurityContext error: SEC_E_UNTRUSTED_ROOT
 Warning(schanneladapter.cc:421): SChannelAdapter::Error(ContinueSSL, SEC_E_UNTRU
 STED_ROOT)

What version of the product are you using? On what operating system?
 libjingle0.6.3  windows XP

Please provide any additional information below.

Original issue reported on code.google.com by zhengxue...@gmail.com on 6 Dec 2011 at 8:20

Attachments:

GoogleCodeExporter commented 9 years ago 
Take a look at issue 195, comment #10. It may help.

Original comment by diego.cd...@gmail.com on 6 Dec 2011 at 10:24

GoogleCodeExporter commented 9 years ago 
hi diego；
thanks for your help! It worked!

Original comment by zhengxue...@gmail.com on 8 Dec 2011 at 7:54

GoogleCodeExporter commented 9 years ago 
You are welcome. I just want to know why those lines were removed. The way the 
things are today the --s option of call example is indeed not working. I think 
whether to accept or not an unknown certificate authority should be a user's 
choice, so he can use any server to login.

Original comment by diego.cd...@gmail.com on 8 Dec 2011 at 6:55

GoogleCodeExporter commented 9 years ago 
It is also possible to login on any server using the flags I explained on issue 
72, comment #9, but it disables TLS.

Original comment by diego.cd...@gmail.com on 15 Dec 2011 at 12:35

GoogleCodeExporter commented 9 years ago 
Hi diego;
I gone over your comments and the ssl error is gone .But I couldnt login to my 
server.I am getting the not authorized error from my local server.

Original comment by mirsh...@gmail.com on 22 Dec 2011 at 6:10

Attachments:

GoogleCodeExporter commented 9 years ago 
I am sorry it my issue . I put wrong username and password.
Thanks Diego.It solved my two days problem

Original comment by mirsh...@gmail.com on 22 Dec 2011 at 6:41

GoogleCodeExporter commented 9 years ago

Original comment by jun...@google.com on 9 Feb 2012 at 4:57