Re: works from SSH tunnel but not from remote
Am Donnerstag, 19. Juli 2012, 19:56:23 schrieb Julius Schwartzenberg: This looks quite old fashioned to me ;) LOL nice! I would expect ::1 and :: instead there. Maybe your client is indeed trying to use IPv6? My ISP is still unable to provide IPv6 :( But no, it is the gSASL bug.
ejabberd migration
Hi, I have migrated one (hura! :) ) user from ejabberd to jabberd2 with mysql backend. I have written a small PHP script which parses some information out of an ejabberd dump (ejabberdctl dump foo). It is not complete. The most ugly point is that this script does not recover the user passwords. But it's a start. It prints some INSERT statements. Please have a look at the XXX's before using. cheers Danielattachment: migrate.php
Re: works from SSH tunnel but not from remote
Hi again, I tried at home from my router with mcabber. Everything worked fine. Then I tried from my working machine (which is behind the router) and... guess... it worked, too ;) Erm, Kopete? What are you doing? thanks for your attention Daniel Am Montag, 16. Juli 2012, 23:51:25 schrieb magic-jabbe...@damage.devloop.de: If I create a tunnel on port 5222 (ssh -L 5222:localhost:5222 devloop.de) and if I set my jabber client to connect to localhost:5222 everything is working fine. Login works, presence message are comming in. This is the log: -- Jul 16 23:26:32 devloop jabberd/c2s[4445]: [8] [127.0.0.1, port=49636] connect Jul 16 23:26:32 devloop jabberd/c2s[4445]: [8] legacy authentication succeeded: host=devloop.de, username=damage, resource=Kopete Jul 16 23:26:32 devloop jabberd/c2s[4445]: [8] requesting session: jid=dam...@devloop.de/Kopete Jul 16 23:26:32 devloop jabberd/sm[4422]: session started: jid=dam...@devloop.de/Kopete -- But if I try to use the normal remote way and try to connect directly to devloop.de:5222 my client is hanging during login. And the log is just: -- Jul 16 23:27:28 devloop jabberd/c2s[4445]: [8] [91.37.187.80, port=33738] connect --
Re: works from SSH tunnel but not from remote
Sorry, once again it's me. I noticed that kopete is working if I explicitly set the connection server (in my case devloop.de). Setting the connection server results on major XML changes. Please note that 'verison=1.0' in the first stream tag of the XML. I don't know much about the XMPP protocol. May someone is able to give me a tip about what is going wrong? Is that a jabberd2 or a kopete problem? thanks Daniel --- without connection server set (not working) --- ?xml version=1.0? stream:stream xmlns:stream=http://etherx.jabber.org/streams; version=1.0 xmlns=jabber:client to=devloop.de ?xml version='1.0'?stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' from='devloop.de' version='1.0' id='13ipsmggju6kqcb82rqdmqfny42xtfuujdjbz0sj' stream:features mechanisms xmlns=urn:ietf:params:xml:ns:xmpp-sasl mechanismPLAIN/mechanism mechanismDIGEST-MD5/mechanism /mechanisms auth xmlns=http://jabber.org/features/iq-auth/ register xmlns=http://jabber.org/features/iq-register/ /stream:features auth xmlns=urn:ietf:params:xml:ns:xmpp-sasl mechanism=DIGEST-MD5/ challenge xmlns=urn:ietf:params:xml:ns:xmpp- saslcmVhbG09ImRldmxvb3AuZGUiLCBub25jZT0icEFWL3hRZUg5KzUvNEVVX2t0b3dhZz09IiwgcW9wPSJhdXRoIiwgY2hhcnNldD11dGYtOCwgYWxnb3JpdGhtPW1kNS1zZXNz/challenge response xmlns=urn:ietf:params:xml:ns:xmpp- sasldXNlcm5hbWU9ImRhbWFnZSIscmVhbG09ImRldmxvb3AuZGUiLG5vbmNlPSWwQVYveFFlSDkrNS80RVVLa3Rvd2FnPT0iLGNub25jZT0ieEFweU1Hb2ZZRlROR0xKUnRhTHlIekQ0NlJYOHZzeDg4T2JobmF4WTMzRT0iLG5jPTAwMDAwMDAxLGRpZ2VzdC11cmk9InhtcHAvZGV2bG9vcC5kZSIscW9wPWF1dGgscmVzcG9uc2U9OWU0NjY0MjQ3MDEzMzYzNDI2Mjg2NGRiNDFlYzAxOWYsY2hhcnNldD11dGYtOA==/response success xmlns=urn:ietf:params:xml:ns:xmpp-sasl/ ?xml version=1.0? stream:stream xmlns:stream=http://etherx.jabber.org/streams; version=1.0 xmlns=jabber:client to=devloop.de --- --- with connection server set (working) --- ?xml version=1.0? stream:stream xmlns:stream=http://etherx.jabber.org/streams; xmlns=jabber:client to=devloop.de ?xml version='1.0'?stream:stream xmlns:stream='http://etherx.jabber.org/streams' xmlns='jabber:client' from='devloop.de' id='x64pfgs4l4jlb4m6h2lj9t22cfgq9xw641wjhpn2' iq type=get to=devloop.de id=auth_1 query xmlns=jabber:iq:auth usernamedamage/username /query /iq iq type=result id=auth_1 query xmlns=jabber:iq:auth usernamedamage/username resource/ password/ digest/ /query /iq iq type=set to=devloop.de id=auth_2 query xmlns=jabber:iq:auth usernamedamage/username digest[Filtered]/digest resourceKopete/resource /query /iq [rosters etc.] --- Am Dienstag, 17. Juli 2012, 22:34:36 schrieb magic-jabbe...@damage.devloop.de: Hi again, I tried at home from my router with mcabber. Everything worked fine. Then I tried from my working machine (which is behind the router) and... guess... it worked, too ;) Erm, Kopete? What are you doing? thanks for your attention Daniel Am Montag, 16. Juli 2012, 23:51:25 schrieb magic-jabbe...@damage.devloop.de: If I create a tunnel on port 5222 (ssh -L 5222:localhost:5222 devloop.de) and if I set my jabber client to connect to localhost:5222 everything is working fine. Login works, presence message are comming in. This is the log: -- Jul 16 23:26:32 devloop jabberd/c2s[4445]: [8] [127.0.0.1, port=49636] connect Jul 16 23:26:32 devloop jabberd/c2s[4445]: [8] legacy authentication succeeded: host=devloop.de, username=damage, resource=Kopete Jul 16 23:26:32 devloop jabberd/c2s[4445]: [8] requesting session: jid=dam...@devloop.de/Kopete Jul 16 23:26:32 devloop jabberd/sm[4422]: session started: jid=dam...@devloop.de/Kopete -- But if I try to use the normal remote way and try to connect directly to devloop.de:5222 my client is hanging during login. And the log is just: -- Jul 16 23:27:28 devloop jabberd/c2s[4445]: [8] [91.37.187.80, port=33738] connect --
works from SSH tunnel but not from remote
Hi, I am going crazy with that: If I create a tunnel on port 5222 (ssh -L 5222:localhost:5222 devloop.de) and if I set my jabber client to connect to localhost:5222 everything is working fine. Login works, presence message are comming in. This is the log: -- Jul 16 23:26:32 devloop jabberd/c2s[4445]: [8] [127.0.0.1, port=49636] connect Jul 16 23:26:32 devloop jabberd/c2s[4445]: [8] legacy authentication succeeded: host=devloop.de, username=damage, resource=Kopete Jul 16 23:26:32 devloop jabberd/c2s[4445]: [8] requesting session: jid=dam...@devloop.de/Kopete Jul 16 23:26:32 devloop jabberd/sm[4422]: session started: jid=dam...@devloop.de/Kopete -- But if I try to use the normal remote way and try to connect directly to devloop.de:5222 my client is hanging during login. And the log is just: -- Jul 16 23:27:28 devloop jabberd/c2s[4445]: [8] [91.37.187.80, port=33738] connect -- I don't think it is a firewall problem as packets are received by c2s daemon. Just one thing I determined: -- devloop ~ # ping devloop.de PING devloop.de (127.0.0.1) 56(84) bytes of data. 64 bytes from devloop.de (127.0.0.1): icmp_req=1 ttl=64 time=0.019 ms -- My server resolves itself as 127.0.0.1 through /etc/hosts file. But I don't think it's a problem because I already tried without that. Any ideas what's going on there? I can provide XMLs if needed but I really hope it's a kind of 'RTFM problem'... Some infos about my installation: - version 2.2.4 - mysql storage backend - sm and router are bound to 127.0.0.1 - c2s and s2s are bound to 0.0.0.0 - sm has auto-create user enabled thanks in advance Daniel PS: My client is able to connect to another jabber server.
MySQL Script
Hi, I decided to switch to jabberd2. Erlang and lua are not my favorite languages ;) I think C is the best on Linux machines. However, I have seen the MySQL script provided by jabberd2 which you can use to create the database used by jabberd2. I noticed alle the TEXT and TINYTEXT fields in it. Also there are no table references set (which is not possible because of the TEXT fields). Is there a reason for that? Can I just change the field types? regards Daniel
Couple of configuration questions.
Hello. I have jabberd2 mostly up and running. Could somebody please clarify exactly which settings should be set to completely deny unencrypted client-to-server and client-to-client communications? Also, what's the simplest way to deny the setting of account passwords of less than a given length and/or complexity? Thanks, M -- To unsubscribe send a mail to jabberd2+unsubscr...@lists.xiaoka.com
Re: Migrating from SILC. Is Jabber capable?
On 2009-06-21 17:54:42, Tomasz Sterna wrote: You probably know that Jabber is a protocol and jabberd2 is one of the available Jabber/XMPP server implementations. So my answers will be two-fold - for the XMPP itself and jabberd2 server. Indeed. XMPP uses SASL for authentication. So you may use any authentication method that is available with SASL. The most common today is DIGEST-MD5 which uses challenge-response with username/password pairs and protects them on the wire. One of available authentication options is SASL EXTERNAL which uses X.509 certificates used in TLS encryption for authentication. jabberd2 has SASL EXTERNAL implemented, but since nobody uses it, it is untested and might be broken. Is it also undocumented? I can't seem to see any reference to it in the config files or documentation. XMPP specifies RFC 3923 for end-to-end encryption which should suffice. It is completely client based and does not need any special server support. Nevertheless jabberd2 has an option to enforce TLS on client connections. Excellent. XEP-0045 describes Multi User Chatrooms that should fit your needs. It supports complete control over the room access and persistance. jabberd2 does not provide a MUC component. MUC is a separate service that works on separate domain (not the server domain). Anyway, jabberd2 works great with mu-conference. Download links at http://codex.xiaoka.com/wiki/jabberd2:start#download This is where things seem to fall down a little. Correct me if I'm wrong but it seems that the muc service connects to the jabber server using only a cleartext shared secret? Also, given that muc runs as an external service, when it inevitably crashes at some point, does that destroy all current rooms? I'm not familiar with how this stuff works at the protocol level yet, so it may be a naive question. And there are LOADS of jabber clients and client libraries. Check out the SILC toolkit to see why after some ten years of development, there are about three clients in existence and all of them are riddled with crash bugs... Well... I propose that you install an evaluation installation and check whether Jabber/XMPP suits your needs. Yeah, I have a jabberd2 server running now. -- To unsubscribe send a mail to jabberd2+unsubscr...@lists.xiaoka.com
Migrating from SILC. Is Jabber capable?
Hello. We've been using SILC for the past couple of years for secure communication but have finally become tired of the poor client support, poor server implementation, poor technical support and various other issues. We're looking at jabber as a replacement for the SILC server and I'm basically trying to find out if jabber satisfies the requirements we have. I'm asking this question here as it seems jabberd2 is the most conspicuous open server implementation and would likely be the server we'd be using. We're just using a single, standalone server for SILC. I'd hope to be doing the same with jabber. The requirements are: 1. Strong authentication. In SILC, every user and server has a public/private keypair. This means that in the server configuration file, you can simply specify a list of keys that are allowed access to administration functions. There's no by host or by name authentication. 2. Mandatory encryption. All communcation between users on the server and all communication on channels must be strongly encrypted. On our network, we also require all channel messages to be signed. 3. Persistent channels or some equivalent. The SILC concept of a channel is more or less identical to the IRC concept of a channel. Modes can be set such as invite-only, ops-only, etc. One feature that we use extensively is the ability to set a whitelist of users that are allowed on the channel. The whitelist is a simple list of keys (no matching on usernames or hosts - this is critical). Currently, due to the complete lack of persistence on the SILC server, we have to use a custom service that essentially connects and races with users to set up channels before somebody else can. It's pretty pathetic. 4. Client support. At first glance, it seems everything that supports SILC also supports jabber, so I don't think this'll be a problem. Any ideas if all of the above are achievable? Thanks. -- To unsubscribe send a mail to jabberd2+unsubscr...@lists.xiaoka.com
Re: [Jabberd2] [jabberd2] #135: abberd/c2s[16575]: [7] [192.168.0.2, port=39040] connect
#135: abberd/c2s[16575]: [7] [192.168.0.2, port=39040] connect -+-- Reporter: megerdin |Owner: smoku Type: defect| Status: closed Priority: major |Component: c2s Version: 2.1.13| Resolution: duplicate Keywords:| Blocking: -+-- Changes (by DeSnajpa): * status: new = closed * resolution: = duplicate Comment: Duplicate of [http://jabberd2.xiaoka.com/ticket/134 #134]. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/135#comment:1 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #152: configure: error: no SASL backend available out of: gsasl
#152: configure: error: no SASL backend available out of: gsasl
---+
Reporter: chewblocka | Owner: smoku
Type: defect | Status: closed
Priority: major | Component: Build
Version: 2.1.15 | Resolution: invalid
Keywords: | Tracforge_linkmap:
Blocking: |
---+
Changes (by chewblocka):
* status: new = closed
* resolution: = invalid
Comment:
Replying to [comment:1 smoku]:
Replying to [ticket:152 chewblocka]:
First off, I am quite annoyed that this prerequisite is not mentioned
anywhere in the installation documentation
{{{
[EMAIL PROTECTED]:~/devel/jabberd2$ cat README
README for Jabber Open Source Server (2.1)
[...]
Required packages:
- expat - XML parsing libraries
http://expat.sourceforge.net/
- Simple Authentication and Security Layer library
* GnuSASL (0.2.14 or higher)
http://www.gnu.org/software/gsasl/
please see contrib/ subdir for patches
or
* Cyrus SASL -
http://asg.web.cmu.edu/sasl/
Optional packages:
[...]
}}}
and that you apparently cannot plugin cyrus-sasl instead of gsasl
You can. Use {{{--enable-sasl=cyrus}}}. It's not supported, thus not
mentioned in ./configure --help.
checking for Libidn version = 0.3.0... yes
checking gsasl.h usability... yes
checking gsasl.h presence... yes
checking for gsasl.h... yes
checking for gsasl_check_version in -lgsasl... yes
checking for GnuSASL version = 0.2.14... no
configure: error: no SASL backend available out of: gsasl
Aparently, you have gsasl installed, but in version prior to 0.2.14.
Please check if you have libgsasl in /usr/lib.
If not, please attach your {{{config.log}}} file to the ticket.
It would be nice if the InstallGuide were updated to reflect these
requirements. I have libgsasl 0.2.21 installed. For some reason, the
configure script is only looking in /usr/lib even though /usr/local/lib is
in my ld.so.conf so I created symbolic links to the copies in
/usr/local/lib and it works now.
It looks like I've had to do this with several other libraries as well.
Another example was the mysql libraries. They are located in
/usr/lib/mysql instead of just /usr/lib/. In any case, I think I'm
getting through it now.
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/152#comment:2
jabberd2 http://jabberd2.xiaoka.com/
versatile XMPP server
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #151: Oracle - authreg_storage uses Mysql?
#151: Oracle - authreg_storage uses Mysql? ---+ Reporter: doehrm | Owner: smoku Type: defect | Status: new Priority: major | Component: Build Version: 2.1.15 | Tracforge_linkmap: Blocking: | ---+ 2.1.15 Solaris 10 Sun Studio 11 CC=cc CXX=CC \ ./configure \ --prefix=/opt/jabber \ --enable-ssl \ --enable-oracle \ --disable-mysql \ --enable-debug \ --with-oracle-home=/opt/oracle \ --with-extra-include-path=/opt/openssl/include:/opt/jabber/include \ --with-extra-library-path=/opt/openssl/lib:/opt/jabber/lib cc -DHAVE_CONFIG_H -I. -I.. -I../sm -I../c2s -I/opt/oracle/rdbms/demo -I/opt/oracle/rdbms/public -I/opt/oracle/rdbms/demo -I/opt/oracle/rdbms/public -I/opt/jabber/include -I/opt/openssl/include -g -c storage_oracle.c -KPIC -DPIC -o .libs/stor age_oracle_la-storage_oracle.o cc -DHAVE_CONFIG_H -I. -I.. -I../sm -I../c2s -I/opt/oracle/rdbms/demo -I/opt/oracle/rdbms/public -I/opt/oracle/rdbms/demo -I/opt/oracle/rdbms/public -I/opt/jabber/include -I/opt/openssl/include -g -c authreg_mysql.c -KPIC -DPIC -o .libs/authr eg_oracle_la-authreg_mysql.o authreg_mysql.c, line 24: cannot find include file: mysql.h authreg_mysql.c, line 32: syntax error before or at: MYSQL authreg_mysql.c, line 40: warning: no explicit type given authreg_mysql.c, line 40: syntax error before or at: * authreg_mysql.c, line 40: warning: old-style declaration or incorrect type for: _ar_mysql_get_user_tuple authreg_mysql.c, line 42: undefined symbol: MYSQL authreg_mysql.c, line 42: undefined symbol: conn authreg_mysql.c, line 42: syntax error before or at: = authreg_mysql.c, line 45: undefined symbol: res authreg_mysql.c, line 47: warning: implicit function declaration: mysql_ping authreg_mysql.c, line 55: warning: implicit function declaration: mysql_real_escape_string authreg_mysql.c, line 62: warning: implicit function declaration: mysql_query authreg_mysql.c, line 63: warning: implicit function declaration: mysql_error authreg_mysql.c, line 67: warning: implicit function declaration: mysql_store_result authreg_mysql.c, line 73: warning: implicit function declaration: mysql_num_rows authreg_mysql.c, line 74: warning: implicit function declaration: mysql_free_result authreg_mysql.c, line 78: warning: improper pointer/integer combination: op = authreg_mysql.c, line 79: cannot recover from previous errors In storage/Makefile.am I see if STORAGE_ORACLE pkglib_LTLIBRARIES += authreg_oracle.la storage_oracle.la authreg_oracle_la_SOURCES = authreg_mysql.c authreg_oracle_la_CPPFLAGS = $(ORACLE_CPPFLAGS) authreg_oracle_la_LDFLAGS = $(MODULE_LDFLAGS) $(ORACLE_LDFLAGS) authreg_oracle_la_LIBADD = $(MODULE_LIBADD) $(ORACLE_LIBS) storage_oracle_la_SOURCES = storage_oracle.c storage_oracle_la_CPPFLAGS = $(ORACLE_CPPFLAGS) storage_oracle_la_LDFLAGS = $(MODULE_LDFLAGS) $(ORACLE_LDFLAGS) storage_oracle_la_LIBADD = $(MODULE_LIBADD) $(ORACLE_LIBS) endif Why is here authreg_mysql.c used and not authreg_oracle.c? Any special reason for this? Regards, Markus -- Ticket URL: http://jabberd2.xiaoka.com/ticket/151 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #149: Jabber roster limitation
#149: Jabber roster limitation +--- Reporter: kevinjabber | Owner: smoku Type: task | Status: closed Priority: major| Component: General Version: 2.0 | Resolution: invalid Keywords: | Tracforge_linkmap: Blocking: | +--- Changes (by smoku): * status: new = closed * resolution: = invalid Comment: 2.0 line is not supported anymore. Please upgrade do 2.1. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/149#comment:1 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #148: Migrate berkleydb to mysql (script)
#148: Migrate berkleydb to mysql (script) +--- Reporter: alphaone | Owner: smoku Type: enhancement | Status: new Priority: major| Component: storage Version: 2.1.6| Tracforge_linkmap: Blocking: | +--- When setting up my new server I finally decided to switch to use mysql instead of berkleydb for my jabber server. What has kept me at bdb this long was purely the lack of any migration script. The attached ruby script reads the entries in authreg.db and sm.db and populates a mysql database. I have not tested this script extensively, so there may be errors! -- Ticket URL: http://jabberd2.xiaoka.com/ticket/148 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #147: Tool to dump BerkeleyDB sm-storage
#147: Tool to dump BerkeleyDB sm-storage +--- Reporter: harry| Owner: smoku Type: enhancement | Status: new Priority: major| Component: sm Version: 2.1.15 | Tracforge_linkmap: Blocking: | +--- Attached is a little perl tool to dump an sm-storage, kept in a berkeley db to an xml file. If others need this too, it could be added to the tools/ dir. Also attached is an example XSLT file to transform the dump to a script suitable to load a mysql db. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/147 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #142: Implement XEP-0157: Contact Addresses for XMPP Services
#142: Implement XEP-0157: Contact Addresses for XMPP Services
+---
Reporter: smoku| Owner: smoku
Type: enhancement | Status: assigned
Priority: major| Component: sm
Version: 2.1.15 | Resolution:
Keywords: | Tracforge_linkmap:
Blocking: |
+---
Comment (by smoku):
need to modify {{{sm/mod_help.c}}}
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/142#comment:2
jabberd2 http://jabberd2.xiaoka.com/
versatile XMPP server
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #106: #items discovery leads to #info result
#106: #items discovery leads to #info result ---+ Reporter: elmex | Owner: smoku Type: defect | Status: closed Priority: major | Component: General Version: 2.1.8 | Resolution: invalid Keywords: | Tracforge_linkmap: Blocking: | ---+ Changes (by smoku): * status: new = closed * resolution: = invalid * tracforge_linkmap: = Comment: It is a correct behavior by disco-publish. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/106#comment:3 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #106: #items discovery leads to #info result
#106: #items discovery leads to #info result ---+ Reporter: elmex | Owner: smoku Type: defect | Status: closed Priority: major | Component: General Version: 2.1.8 | Resolution: invalid Keywords: | Tracforge_linkmap: Blocking: | ---+ Comment (by DeSnajpa): Btw do any client use disco-publish? If no, I think there is no reason to have this module in sm. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/106#comment:4 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #142: Implement XEP-0157: Contact Addresses for XMPP Services
#142: Implement XEP-0157: Contact Addresses for XMPP Services -+-- Reporter: smoku| Owner: smoku Type: enhancement | Status: new Priority: major| Component: General Version: 2.1.15 |Keywords: Tracforge_linkmap: |Blocking: -+-- Implement [http://www.xmpp.org/extensions/xep-0157.html XEP-0157: Contact Addresses for XMPP Services] as sm.xml configurable options. Probably mod_contact extension. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/142 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #142: Implement XEP-0157: Contact Addresses for XMPP Services
#142: Implement XEP-0157: Contact Addresses for XMPP Services +--- Reporter: smoku| Owner: smoku Type: enhancement | Status: assigned Priority: major| Component: sm Version: 2.1.15 | Resolution: Keywords: | Tracforge_linkmap: Blocking: | +--- Changes (by smoku): * status: new = assigned * component: General = sm -- Ticket URL: http://jabberd2.xiaoka.com/ticket/142#comment:1 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #143: Implement XEP-0203: Delayed Delivery
#143: Implement XEP-0203: Delayed Delivery +--- Reporter: smoku | Owner: smoku Type: defect | Status: new Priority: major | Component: General Version: 2.1.15 |Keywords: Tracforge_linkmap: |Blocking: +--- [http://www.xmpp.org/extensions/xep-0203.html XEP-0203: Delayed Delivery] is a successor of XEP-0091. jabberd2 needs to implement it besides XEP-0091 support. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/143 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #144: Implement XEP-0202: Entity Time
#144: Implement XEP-0202: Entity Time +--- Reporter: smoku | Owner: smoku Type: defect | Status: new Priority: major | Component: General Version: 2.1.15 |Keywords: Tracforge_linkmap: |Blocking: +--- [http://www.xmpp.org/extensions/xep-0202.html XEP-0202: Entity Time] is a successor of XEP-0090. Need to replace XEP-0090 implementation with XEP-0202. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/144 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #144: Implement XEP-0202: Entity Time
#144: Implement XEP-0202: Entity Time +--- Reporter: smoku| Owner: smoku Type: enhancement | Status: assigned Priority: major| Component: General Version: 2.1.15 | Resolution: Keywords: | Tracforge_linkmap: Blocking: | +--- Changes (by smoku): * type: defect = enhancement -- Ticket URL: http://jabberd2.xiaoka.com/ticket/144#comment:2 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #143: Implement XEP-0203: Delayed Delivery
#143: Implement XEP-0203: Delayed Delivery +--- Reporter: smoku| Owner: smoku Type: enhancement | Status: assigned Priority: major| Component: General Version: 2.1.15 | Resolution: Keywords: | Tracforge_linkmap: Blocking: | +--- Changes (by smoku): * status: new = assigned * type: defect = enhancement -- Ticket URL: http://jabberd2.xiaoka.com/ticket/143#comment:1 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #145: XEP-0160: Best Practices for Handling Offline Messages compliance
#145: XEP-0160: Best Practices for Handling Offline Messages compliance +--- Reporter: smoku | Owner: smoku Type: task| Status: new Priority: major | Component: General Version: 2.1.15 |Keywords: Tracforge_linkmap: |Blocking: +--- Need to look through mod_offline to check for [http://www.xmpp.org/extensions/xep-0160.html XEP-0160: Best Practices for Handling Offline Messages] compliance. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/145 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #146: Use dlfcn.h with storage modules
#146: Use dlfcn.h with storage modules
--+-
Reporter: smoku | Owner: smoku
Type: defect| Status: new
Priority: critical | Component: storage
Version: 2.1.15|Keywords:
Tracforge_linkmap:|Blocking:
--+-
SM module manager ({{{sm/mm.c}}}) uses {{{dlfcn.h}}} to wrap dynamic
loader and {{{#ifdef _WIN32}}} to wrap Win32 .dll loader. We need to
change {{{storage/}}} modules usage to behave likewise.
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/146
jabberd2 http://jabberd2.xiaoka.com/
versatile XMPP server
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #146: Use dlfcn.h with storage modules
#146: Use dlfcn.h with storage modules -+-- Reporter: smoku | Owner: smoku Type: defect| Status: assigned Priority: critical | Component: storage Version: 2.1.15| Resolution: Keywords:| Tracforge_linkmap: Blocking:| -+-- Changes (by smoku): * status: new = assigned -- Ticket URL: http://jabberd2.xiaoka.com/ticket/146#comment:1 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #141: Implement XEP-0013: Flexible Offline Message Retrieval
#141: Implement XEP-0013: Flexible Offline Message Retrieval
+---
Reporter: DeSnajpa | Owner: smoku
Type: enhancement | Status: assigned
Priority: major| Component: sm
Version: 2.1.15 | Resolution:
Keywords: | Tracforge_linkmap:
Blocking: |
+---
Changes (by smoku):
* status: new = assigned
* version: 2.2 = 2.1.15
* summary: Implement Flexible Offline Message Retrieval (XEP-13) =
Implement XEP-0013: Flexible Offline Message
Retrieval
Comment:
need to modify {{{sm/mod_offline.c}}}
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/141#comment:1
jabberd2 http://jabberd2.xiaoka.com/
versatile XMPP server
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #15: ZLIB Compression
#15: ZLIB Compression +--- Reporter: smoku| Owner: smoku Type: enhancement | Status: closed Priority: major| Component: c2s Version: 2.1 | Resolution: fixed Keywords: | Tracforge_linkmap: Blocking: | +--- Changes (by smoku): * status: assigned = closed * resolution: = fixed * blocking: = * tracforge_linkmap: = Comment: Implemented in [366:368] -- Ticket URL: http://jabberd2.xiaoka.com/ticket/15#comment:2 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #141: Implement Flexible Offline Message Retrieval (XEP-13)
#141: Implement Flexible Offline Message Retrieval (XEP-13) +--- Reporter: DeSnajpa | Owner: smoku Type: enhancement | Status: new Priority: major| Component: sm Version: 2.2 | Tracforge_linkmap: Blocking: | +--- Implement [http://www.xmpp.org/extensions/xep-0013.html XEP-0013] as an alternative way to retrieve offline messages. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/141 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #140: default c2s virtual config to use for all present sm
#140: default c2s virtual config to use for all present sm -+-- Reporter: smoku| Owner: smoku Type: enhancement | Status: new Priority: major| Component: c2s Version: 2.1.15 |Keywords: Tracforge_linkmap: |Blocking: -+-- Add a host configuration section to c2s.xml that is used for all domains that have SM present, but do not have corresponding C2S config. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/140 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #140: default c2s virtual config to use for all present sm
#140: default c2s virtual config to use for all present sm +--- Reporter: smoku| Owner: smoku Type: enhancement | Status: assigned Priority: major| Component: c2s Version: 2.1.15 | Resolution: Keywords: | Tracforge_linkmap: Blocking: | +--- Changes (by smoku): * status: new = assigned -- Ticket URL: http://jabberd2.xiaoka.com/ticket/140#comment:1 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #139: c2s gsasl mio crash
#139: c2s gsasl mio crash ---+ Reporter: tofu| Owner: smoku Type: defect | Status: assigned Priority: major | Component: c2s Version: 2.1.14 | Resolution: Keywords: | Tracforge_linkmap: Blocking: | ---+ Changes (by smoku): * status: new = assigned Comment: I think it may happen, if the response packet is sent before the auth packet was sent. Wee need to check for that NULL session descriptor. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/139#comment:2 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #139: c2s gsasl mio crash
#139: c2s gsasl mio crash ---+ Reporter: tofu| Owner: smoku Type: defect | Status: closed Priority: major | Component: c2s Version: 2.1.14 | Resolution: fixed Keywords: | Tracforge_linkmap: Blocking: | ---+ Comment (by tofu): In change 356 in sasl_gsasl.c you take out line 354. I am curious why you did that? It seems gsasl_step and still fail or return something we do not want it to. Is this not the case? -- Ticket URL: http://jabberd2.xiaoka.com/ticket/139#comment:5 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #139: c2s gsasl mio crash
#139: c2s gsasl mio crash
---+
Reporter: tofu| Owner: smoku
Type: defect | Status: closed
Priority: major | Component: c2s
Version: 2.1.14 | Resolution: fixed
Keywords: | Tracforge_linkmap:
Blocking: |
---+
Comment (by tofu):
I have not gotten it to fail, which is great! In sasl_gsasl.c you removed
the following at line 354.
{{{
354 if(ret != GSASL_OK ret != GSASL_NEEDS_MORE) {
355 _sx_debug(ZONE, gsasl_step failed, no sasl
for this conn; (%d): %s, ret, gsasl_strerror(ret));
356 _sx_nad_write(s, _sx_sasl_failure(s,
_sasl_err_MALFORMED_REQUEST), 0);
357 if(out != NULL) free(out);
358 if(buf != NULL) free(buf);
359 return;
360 }
}}}
I was just wondering why and wouldnt it create problems if gsasl_step did
fail?
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/139#comment:7
jabberd2 http://jabberd2.xiaoka.com/
versatile XMPP server
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #139: c2s gsasl mio crash
#139: c2s gsasl mio crash ---+ Reporter: tofu| Owner: smoku Type: defect | Status: closed Priority: major | Component: c2s Version: 2.1.14 | Resolution: fixed Keywords: | Tracforge_linkmap: Blocking: | ---+ Comment (by smoku): It will skip the following two if()s and fail exactly the same way then, so the block is unneded. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/139#comment:8 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #139: c2s gsasl mio crash
#139: c2s gsasl mio crash
---+
Reporter: tofu| Owner: smoku
Type: defect | Status: new
Priority: major | Component: c2s
Version: 2.1.14 | Tracforge_linkmap:
Blocking: |
---+
Another c2s crash.
{{{
Core was generated by `/home/chesspark/production/bin/c2s -c
/home/chesspark/production/etc/jabberd/c2'.
Program terminated with signal 11, Segmentation fault.
#0 gsasl_step (sctx=0x0,
input=0x844c048
username=\rajat_thegamer\,realm=\chesspark.com\,nonce=\U5hbvJ8ENHRkfCnCewlrJA==\,cnonce=\d41d8cd98f00b204e9800998ecf8427e\,nc=\0001\,qop=\auth
\,digest-uri=\xmpp/chesspark.com\,response=\6aa651acf9...,
input_len=239, output=0xffac5344, output_len=0xffac5338) at xstep.c:57
57if (sctx-clientp)
(gdb) backtrace
#0 gsasl_step (sctx=0x0,
input=0x844c048
username=\rajat_thegamer\,realm=\chesspark.com\,nonce=\U5hbvJ8ENHRkfCnCewlrJA==\,cnonce=\d41d8cd98f00b204e9800998ecf8427e\,nc=\0001\,qop=\auth
\,digest-uri=\xmpp/chesspark.com\,response=\6aa651acf9...,
input_len=239, output=0xffac5344, output_len=0xffac5338) at xstep.c:57
#1 0x0805a5da in _sx_sasl_client_process (s=0x810fd08, p=0x80889e0,
sd=0x0, mech=0x0,
in=0x82b44b0
dXNlcm5hbWU9InJhamF0X3RoZWdhbWVyIixyZWFsbT0iY2hlc3NwYXJrLmNvbSIsbm9uY2U9IlU1aGJ2SjhFTkhSa2ZDbkNld2xySkE9PSIsY25vbmNlPSJkNDFkOGNkOThmMDBiMjA0ZTk4MDA5OThlY2Y4NDI3ZSIsbmM9IjAwMDAwMDAxIixxb3A9ImF1dGgiLGRp...,
inlen=320) at sasl_gsasl.c:353
#2 0x0805b028 in _sx_sasl_process (s=0x810fd08, p=0x80889e0,
nad=0x83b7468) at sasl_gsasl.c:504
#3 0x08055e9f in _sx_process_read (s=0x810fd08, buf=0x83175f8) at
io.c:125
#4 0x080563b6 in sx_can_read (s=0x810fd08) at io.c:218
#5 0x08050c65 in _c2s_client_mio_callback (m=0x8088ef8, a=action_READ,
fd=0x8159660, data=0x0, arg=0x80f58f0) at c2s.c:436
#6 0x0805c7d1 in _mio_run (m=0x8088ef8, timeout=5) at mio_impl.h:256
#7 0x08053225 in main (argc=134658740, argv=0xf7ff24f8) at main.c:645
}}}
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/139
jabberd2 http://jabberd2.xiaoka.com/
versatile XMPP server
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #139: c2s gsasl mio crash
#139: c2s gsasl mio crash ---+ Reporter: tofu| Owner: smoku Type: defect | Status: new Priority: major | Component: c2s Version: 2.1.14 | Resolution: Keywords: | Tracforge_linkmap: Blocking: | ---+ Comment (by jack): Note that looking through the stack frame for #2, s and p are both fine. p-index is 0, but s-plugin_data[0] is NULL. It appears that somewhere along the way the plugin_data never got set. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/139#comment:1 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #138: another c2s crash
#138: another c2s crash
---+
Reporter: tofu| Owner: smoku
Type: defect | Status: new
Priority: major | Component: c2s
Version: 2.1.14 | Tracforge_linkmap:
Blocking: |
---+
This seems to be sx related.
{{{
Core was generated by `/home/chesspark/production/bin/c2s -c
/home/chesspark/production/etc/jabberd/c2'.
Program terminated with signal 6, Aborted.
#0 0xe410 in __kernel_vsyscall ()
(gdb) backtrace
#0 0xe410 in __kernel_vsyscall ()
#1 0xf7b7b811 in raise () from /lib/tls/i686/cmov/libc.so.6
#2 0xf7b7cfb9 in abort () from /lib/tls/i686/cmov/libc.so.6
#3 0xf7bb0d3a in __fsetlocking () from /lib/tls/i686/cmov/libc.so.6
#4 0xf7bb84dc in mallopt () from /lib/tls/i686/cmov/libc.so.6
#5 0xf7bb8672 in free () from /lib/tls/i686/cmov/libc.so.6
#6 0xf7c9e566 in XML_ParserFree () from /usr/lib/libexpat.so.1
#7 0x08059568 in sx_free (s=0x889c658) at sx.c:97
#8 0x080532fb in main (argc=Cannot access memory at address 0x201c
) at main.c:710
}}}
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/138
jabberd2 http://jabberd2.xiaoka.com/
versatile XMPP server
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #125: c2s doesn't listen on 5222
#125: c2s doesn't listen on 5222 +--- Reporter: mikiecx | Owner: smoku Type: defect | Status: new Priority: major| Component: General Version: 2.1.12 | Resolution: Keywords: | Tracforge_linkmap: Blocking: | +--- Changes (by mikiecx): * version: 2.1.14 = 2.1.12 Comment: i don't think it's a matter of 64bit architecture. my jabberd2 runs (or rather doesn't run ;) ) on slackware 11 on AMD 32bit platform (Duron). so far i tried db and mysql. neither works (but id doesn't lool like it's about auth/storage system). i agree it could be component can't connect to router, tho. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/125#comment:4 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #125: c2s doesn't listen on 5222
#125: c2s doesn't listen on 5222 +--- Reporter: mikiecx | Owner: smoku Type: defect | Status: new Priority: major| Component: General Version: 2.1.14 | Resolution: Keywords: | Tracforge_linkmap: Blocking: | +--- Changes (by digger): * version: 2.1.11 = 2.1.14 * tracforge_linkmap: = Comment: Exactly the same problem here, after rebooting my server. FreeBSD 6.2-RELEASE-p5 / amd64 I'm missing lines like coming online and [%s, port=%d] listening for connections in the c2s debug log. jabberd was running fine on the system for some month -- too bad, I can't tell which version it's been. Maybe I'll try a downgrade... Regards, Steffen -- Ticket URL: http://jabberd2.xiaoka.com/ticket/125#comment:1 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #125: c2s doesn't listen on 5222
#125: c2s doesn't listen on 5222 +--- Reporter: mikiecx | Owner: smoku Type: defect | Status: new Priority: major| Component: General Version: 2.1.14 | Resolution: Keywords: | Tracforge_linkmap: Blocking: | +--- Comment (by digger): 2.1.10 does not work, 2.0s11 ''does''. I could do some more testing between these versions, if helpful... Regards, Steffen -- Ticket URL: http://jabberd2.xiaoka.com/ticket/125#comment:2 jabberd2 http://jabberd2.xiaoka.com/ versatile XMPP server ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #133: gsasl not found but installed
#133: gsasl not found but installed
+---
Reporter: biosoup |Owner: smoku
Type: defect | Status: closed
Priority: major|Component: Build
Version: 2.1.14 | Resolution: fixed
Keywords: | Blocking:
+---
Changes (by biosoup):
* status: assigned = closed
* resolution: = fixed
Comment:
Replying to [comment:5 smoku]:
Looks like another comment:ticket:98:3. Did you update your
{{{/etc/ld.so.conf}}}?
Ok it was in
{{{/etc/ld.so.conf}}}
so it look like this now and it works
{{{
/lib
/usr/lib
/usr/local/lib
}}}
and also I needed to run
{{{
ldconfig
}}}
Thanks for all help.
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/133#comment:6
jabberd2 http://jabberd2.xiaoka.com/
jabberd2 project
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #133: configuring with debud mode - gsasl problem
#133: configuring with debud mode - gsasl problem
+---
Reporter: biosoup | Owner: smoku
Type: defect | Status: new
Priority: major| Component: Build
Version: 2.1.14 |Blocking:
+---
afther
{{{
./configure --enable-mysql --enable-idn --enable-ssl --enable-debug
--enable-sasl=gsasl
}}}
I got error:
{{{
checking gsasl.h usability... yes
checking gsasl.h presence... yes
checking for gsasl.h... yes
checking for gsasl_check_version in -lgsasl... yes
checking for GnuSASL version = 0.2.14... no
configure: error: no SASL backend available out of: gsasl
}}}
But I have good version of gsasl:
{{{
[EMAIL PROTECTED]:/etc# gsasl --version
gsasl 0.2.19
}}}
and also I have libgsasl in version 0.2.19 and everything is in their
usual paths...
I'm using UBUNTU 2.6.15-28-amd64-xeon and nothing else then needed things
is installed. This server is dedicated only to jabber so there should be
no conflicts eith other packages.
Similar tickets solve problems with old gsasl but none with good gsasl.
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/133
jabberd2 http://jabberd2.xiaoka.com/
jabberd2 project
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #134: abberd/c2s[16575]: [7] [192.168.0.2, port=39040] connect
#134: abberd/c2s[16575]: [7] [192.168.0.2, port=39040] connect
-+--
Reporter: megerdin | Owner: smoku
Type: defect| Status: new
Priority: major | Component: c2s
Version: 2.1.13|Blocking:
-+--
{{{
Aug 14 20:28:09 Server1 jabberd/c2s[16575]: [7] [192.168.0.2, port=39040]
connect
Aug 14 20:28:09 Server1 jabberd/c2s[16575]: [7] [192.168.0.2, port=39040]
disconnect
}}}
So where should i wrote for this.[[BR]]
plz any url.
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/134
jabberd2 http://jabberd2.xiaoka.com/
jabberd2 project
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #135: abberd/c2s[16575]: [7] [192.168.0.2, port=39040] connect
#135: abberd/c2s[16575]: [7] [192.168.0.2, port=39040] connect
-+--
Reporter: megerdin | Owner: smoku
Type: defect| Status: new
Priority: major | Component: c2s
Version: 2.1.13|Blocking:
-+--
{{{
Aug 14 20:28:09 Server1 jabberd/c2s[16575]: [7] [192.168.0.2, port=39040]
connect
Aug 14 20:28:09 Server1 jabberd/c2s[16575]: [7] [192.168.0.2, port=39040]
disconnect
}}}
So where should i wrote for this.[[BR]]
plz any url.
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/135
jabberd2 http://jabberd2.xiaoka.com/
jabberd2 project
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #136: failed loading storage module 'mysql' (/usr/local/lib/jabberd/
#136: failed loading storage module 'mysql' (/usr/local/lib/jabberd/
-+--
Reporter: megerdin | Owner: smoku
Type: defect| Status: new
Priority: major | Component: storage
Version: 2.1.13|Blocking:
-+--
Hi jabberd fan
I m new at jabberd. and tried to implement jabberd server with
jabberd-2.1.13
after configuring when i run /usr/local/bin/jabberd script
the log file say .
{{{
jabberd/sm[16822]: failed loading storage module 'mysql'
(/usr/local/lib/jabberd/storage_mysql.so: cannot open shared object file:
No such file or directory
jabberd/c2s[16824]: failed loading authreg module 'mysql'
(/usr/local/lib/jabberd/authreg_mysql.so: cannot open shared object file:
No such file or directory
}}}
I tried to download the storage and authreg file from internet but didn't
find any file
I use mysql (mysql-5.0.37-2.fc7) as my database server.
please help me to solve the problem...please...
{{{
i did it before when i configured . but the result is above mentione code.
}}}
with this code
{{{
./configure --enable-mysql --enable-ssl --enable-idn \
--with-extra-include-path=/usr/include/mysql:/usr/include \
--with-extra-library-path=/usr/lib/mysql:/usr/lib
}}}
[[BR]]plz anymore help[[BR]]
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/136
jabberd2 http://jabberd2.xiaoka.com/
jabberd2 project
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #136: failed loading storage module 'mysql' (/usr/local/lib/jabberd/
#136: failed loading storage module 'mysql' (/usr/local/lib/jabberd/ -+-- Reporter: megerdin |Owner: smoku Type: defect| Status: closed Priority: major |Component: storage Version: 2.1.13| Resolution: invalid Keywords:| Blocking: -+-- Changes (by DeSnajpa): * status: new = closed * resolution: = invalid Comment: This is not a jabberd-2.x bug. Please discuss the problem on mailing list. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/136#comment:1 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #133: gsasl not found but installed
#133: gsasl not found but installed
+---
Reporter: biosoup |Owner: smoku
Type: defect | Status: assigned
Priority: major|Component: Build
Version: 2.1.14 | Resolution:
Keywords: | Blocking:
+---
Changes (by smoku):
* status: new = assigned
* summary: configuring with debud mode - gsasl problem = gsasl not
found but installed
Comment:
Please give tha output of command:
{{{
$ which gsasl
}}}
and attach your config.log file to the ticket.
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/133#comment:2
jabberd2 http://jabberd2.xiaoka.com/
jabberd2 project
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #136: failed loading storage module 'mysql' (/usr/local/lib/jabberd/
#136: failed loading storage module 'mysql' (/usr/local/lib/jabberd/
-+--
Reporter: megerdin |Owner: smoku
Type: defect| Status: reopened
Priority: major |Component: Build
Version: 2.1.13| Resolution:
Keywords:| Blocking:
-+--
Changes (by smoku):
* status: closed = reopened
* resolution: invalid =
* component: storage = Build
Comment:
Well... This actually might be a ./configure error.
Please attach your {{{config.log}}} file to the ticket.
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/136#comment:2
jabberd2 http://jabberd2.xiaoka.com/
jabberd2 project
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #133: configuring with debud mode - gsasl problem
#133: configuring with debud mode - gsasl problem
+---
Reporter: biosoup |Owner: smoku
Type: defect | Status: new
Priority: major|Component: Build
Version: 2.1.14 | Resolution:
Keywords: | Blocking:
+---
Comment (by DeSnajpa):
Possibly it is a bug of configure, look at line 11639:
{{{
#include gsasl.h
int
main ()
{
return !(gsasl_check_version(0.2.14))
;
return 0;
}
}}}
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/133#comment:1
jabberd2 http://jabberd2.xiaoka.com/
jabberd2 project
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #134: abberd/c2s[16575]: [7] [192.168.0.2, port=39040] connect
#134: abberd/c2s[16575]: [7] [192.168.0.2, port=39040] connect -+-- Reporter: megerdin |Owner: smoku Type: defect| Status: closed Priority: major |Component: c2s Version: 2.1.13| Resolution: invalid Keywords:| Blocking: -+-- Changes (by smoku): * status: new = closed * resolution: = invalid Comment: I don't really understand what this ticket is about. If you could be more specific, please reopen the ticket with comments. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/134#comment:1 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #130: can not compile Jabberd2-2.1.14 on Sun solaris 8 (undeclared identifier)
#130: can not compile Jabberd2-2.1.14 on Sun solaris 8 (undeclared identifier) --+- Reporter: yannick56 | Owner: smoku Type: defect | Status: new Priority: major | Component: Build Version: 2.1.14 |Blocking: --+- Hello,[[BR]] [[BR]] Now, I'm trying to compile Jabberd2-2.1.14 on Sun Solaris 8 / Sparc[[BR]] and with the tools:[[BR]] * gcc-3.4.6[[BR]] * gnu make 3.80 [[BR]] * autoconf 2.60[[BR]] * automake 1.10[[BR]] * libtools 1.5[[BR]] * pkgconfig 0.20[[BR]] * m4 1.4.7[[BR]] * mm 1.4.2[[BR]] from www.sunfreeware.com,[[BR]] but I can not compile Jabberd2.[[BR]] [[BR]] I use this parameters for configure :[[BR]] CFLAGS=-O3 -mcpu=ultrasparc -mtune=ultrasparc \[[BR]] CXXFLAGS=-O3 -mcpu=ultrasparc -mtune=ultrasparc \[[BR]] CPPFLAGS=-I/opt/jabberd-2.1.14/lib/expat-2.0.1/include \[[BR]] -I/opt/jabberd-2.1.14/lib/libidn-0.6.14/include \[[BR]] -I/opt/jabberd-2.1.14/lib/gsasl-0.2.15/include \[[BR]] -I/usr/include \[[BR]] -I/usr/local/include \[[BR]] LDFLAGS=-L/opt/jabberd-2.1.14/lib/expat-2.0.1/lib \[[BR]] -L/opt/jabberd-2.1.14/lib/libidn-0.6.14/lib \[[BR]] -L/opt/jabberd-2.1.14/lib/gsasl-0.2.15/lib \[[BR]] -L/usr/lib \[[BR]] -L/usr/local/lib \[[BR]] ./configure \[[BR]] --prefix=/opt/jabberd-2.1.14 \[[BR]] --enable-sasl=gsasl \[[BR]] --disable-ssl \[[BR]] --disable-mysql \[[BR]] --disable-pgsql \[[BR]] --disable-sqlite \[[BR]] --disable-db \[[BR]] --disable-oracle \[[BR]] --disable-ldap \[[BR]] --disable-pam \[[BR]] --disable-pipe \[[BR]] --enable-anon \[[BR]] --enable-fs \[[BR]] --enable-shared --disable-static \[[BR]] --with-pic[[BR]] [[BR]] Compile stop with this error :[[BR]] [[BR]] $ - /home/my_user/sources/jabberd2-2.1.14 make[[BR]] make all-recursive[[BR]] make[1]: Entering directory `/home/my_user/sources/jabberd2-2.1.14'[[BR]] Making all in etc[[BR]] make[2]: Entering directory `/home/my_user/sources/jabberd2-2.1.14/etc'[[BR]] Making all in templates[[BR]] make[3]: Entering directory `/home/my_user/sources/jabberd2-2.1.14/etc/templates'[[BR]] make[3]: Nothing to be done for `all'.[[BR]] make[3]: Leaving directory `/home/my_user/sources/jabberd2-2.1.14/etc/templates'[[BR]] make[3]: Entering directory `/home/my_user/sources/jabberd2-2.1.14/etc'[[BR]] make[3]: Nothing to be done for `all-am'.[[BR]] make[3]: Leaving directory `/home/my_user/sources/jabberd2-2.1.14/etc'[[BR]] make[2]: Leaving directory `/home/my_user/sources/jabberd2-2.1.14/etc'[[BR]] Making all in tools[[BR]] make[2]: Entering directory `/home/my_user/sources/jabberd2-2.1.14/tools'[[BR]] make[2]: Nothing to be done for `all'.[[BR]] make[2]: Leaving directory `/home/my_user/sources/jabberd2-2.1.14/tools'[[BR]] Making all in man[[BR]] make[2]: Entering directory `/home/my_user/sources/jabberd2-2.1.14/man'[[BR]] make[2]: Nothing to be done for `all'.[[BR]] make[2]: Leaving directory `/home/my_user/sources/jabberd2-2.1.14/man'[[BR]] Making all in mio[[BR]] make[2]: Entering directory `/home/my_user/sources/jabberd2-2.1.14/mio'[[BR]] make[2]: Nothing to be done for `all'.[[BR]] make[2]: Leaving directory `/home/my_user/sources/jabberd2-2.1.14/mio'[[BR]] Making all in subst[[BR]] make[2]: Entering directory `/home/my_user/sources/jabberd2-2.1.14/subst'[[BR]] make[2]: Nothing to be done for `all'.[[BR]] make[2]: Leaving directory `/home/my_user/sources/jabberd2-2.1.14/subst'[[BR]] Making all in sx[[BR]] make[2]: Entering directory `/home/my_user/sources/jabberd2-2.1.14/sx'[[BR]] make[3]: Entering directory `/home/my_user/sources/jabberd2-2.1.14/sx'[[BR]] /bin/bash ../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I.. -I/opt/jabberd-2.1.14/lib/expat-2.0.1/include -I/opt/jabberd-2.1.14/lib/libidn-0.6.14/include -I/opt/jabberd-2.1.14/lib/gsasl-0.2.15/include -I/usr/include -I/usr/local/include -O3 -mcpu=ultrasparc -mtune=ultrasparc -MT sasl_gsasl.lo -MD -MP -MF .deps/sasl_gsasl.Tpo -c -o sasl_gsasl.lo sasl_gsasl.c[[BR]] gcc -DHAVE_CONFIG_H -I. -I.. -I/opt/jabberd-2.1.14/lib/expat-2.0.1/include -I/opt/jabberd-2.1.14/lib/libidn-0.6.14/include -I/opt/jabberd-2.1.14/lib/gsasl-0.2.15/include -I/usr/include -I/usr/local/include -O3 -mcpu=ultrasparc -mtune=ultrasparc -MT sasl_gsasl.lo -MD -MP -MF .deps/sasl_gsasl.Tpo -c sasl_gsasl.c -fPIC -DPIC -o .libs/sasl_gsasl.o[[BR]] sasl_gsasl.c: In function `_sx_sasl_client_process':[[BR]] sasl_gsasl.c:324: error: `_sx_ssl_conn_t' undeclared (first use in this function)[[BR]] sasl_gsasl.c:324: error: (Each undeclared identifier is reported only once[[BR]] sasl_gsasl.c:324: error: for each function it appears in.)[[BR]] sasl_gsasl.c:324: error: syntax error before s[[BR]] make[3]: *** [sasl_gsasl.lo] Error 1[[BR]] make[3]: Leaving directory `/home/my_user/sources/jabberd2-2.1.14/sx'[[BR
Re: [Jabberd2] [jabberd2] #126: no SASL backend available out of: gsasl
#126: no SASL backend available out of: gsasl ---+ Reporter: kt1660 |Owner: smoku Type: defect | Status: closed Priority: minor |Component: Build Version: 2.1.12 | Resolution: invalid Keywords: | Blocking: ---+ Comment (by yannick56): dont't forget to use this parameter with configure if you use gsasl: ./configure \ --enable-sasl=gsasl \ -- Ticket URL: http://jabberd2.xiaoka.com/ticket/126#comment:4 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #130: jabberd-2.1.14 does not compile with --disable-ssl
#130: jabberd-2.1.14 does not compile with --disable-ssl --+- Reporter: yannick56 |Owner: smoku Type: defect | Status: assigned Priority: major |Component: Build Version: 2.1.14 | Resolution: Keywords: | Blocking: --+- Changes (by smoku): * status: new = assigned * summary: can not compile Jabberd2-2.1.14 on Sun solaris 8 (undeclared identifier) = jabberd-2.1.14 does not compile with --disable-ssl -- Ticket URL: http://jabberd2.xiaoka.com/ticket/130#comment:1 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #131: jabberd/c2s[16575]: [7] [192.168.0.2, port=39040] disconnect
#131: jabberd/c2s[16575]: [7] [192.168.0.2, port=39040] disconnect
-+--
Reporter: megerdin | Owner: smoku
Type: defect| Status: new
Priority: major | Component: c2s
Version: 2.0 |Blocking:
-+--
hi i m using jabberd-2.0-0.s11.13.fc7.i386
And trying to implement a IM server. for taht i configure it myself and
when i tried to connecrt from any client it say[[BR]]
{{{
Aug 14 20:28:09 Server1 jabberd/c2s[16575]: [7] [192.168.0.2, port=39040]
connect
Aug 14 20:28:09 Server1 jabberd/c2s[16575]: [7] [192.168.0.2, port=39040]
disconnect
}}}
where 192.168.0.2 is my client PC's IP. what shoudld i do to connect IM
server.
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/131
jabberd2 http://jabberd2.xiaoka.com/
jabberd2 project
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #131: jabberd/c2s[16575]: [7] [192.168.0.2, port=39040] disconnect
#131: jabberd/c2s[16575]: [7] [192.168.0.2, port=39040] disconnect -+-- Reporter: megerdin |Owner: smoku Type: defect| Status: closed Priority: major |Component: c2s Version: 2.0 | Resolution: invalid Keywords:| Blocking: -+-- Changes (by smoku): * status: new = closed * resolution: = invalid Comment: This ticket tracker is for reporting problems with the application itself. For deployment help please refer to InstallGuide or mailing list. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/131#comment:1 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #132: failed loading module storage_mysql.so
#132: failed loading module storage_mysql.so
-+--
Reporter: megerdin | Owner: smoku
Type: defect| Status: new
Priority: major | Component: storage
Version: 2.1.13|Blocking:
-+--
Hi jabberd fan [[BR]]
I m new at jabberd. and tried to implement jabberd server with
jabberd-2.1.13[[BR]]
after configuring when i run /usr/local/bin/jabberd script [[BR]]the log
file say .
[[BR]]
{{{
jabberd/sm[16822]: failed loading storage module 'mysql'
(/usr/local/lib/jabberd/storage_mysql.so: cannot open shared object file:
No such file or directory
jabberd/c2s[16824]: failed loading authreg module 'mysql'
(/usr/local/lib/jabberd/authreg_mysql.so: cannot open shared object file:
No such file or directory
}}}
I tried to download the storage and authreg file from internet but didn't
find any file
[[BR]]
I use mysql (mysql-5.0.37-2.fc7) as my database server.
please help me to solve the problem...please...
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/132
jabberd2 http://jabberd2.xiaoka.com/
jabberd2 project
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #129: oracle认证模 块
#129: oracle认证模块 +--- Reporter: fundy|Owner: smoku Type: enhancement | Status: closed Priority: major|Component: storage Version: 2.1 | Resolution: fixed Keywords: | Blocking: +--- Changes (by smoku): * version: 2.0 = 2.1 * type: defect = enhancement -- Ticket URL: http://jabberd2.xiaoka.com/ticket/129#comment:2 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #127: Implement Personal Eventing via Pubsub (XEP-163)
#127: Implement Personal Eventing via Pubsub (XEP-163) +--- Reporter: DeSnajpa |Owner: Type: enhancement | Status: new Priority: minor|Component: sm Version: | Resolution: Keywords: | Blocking: +--- Changes (by DeSnajpa): * owner: DeSnajpa = Comment: So far too hard for me. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/127#comment:3 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #111: jabberd-2.1.9 source distribution contain platform specifi characters and C prototype mismatches
#111: jabberd-2.1.9 source distribution contain platform specifi characters and C prototype mismatches +--- Reporter: plmogan |Owner: smoku Type: defect | Status: closed Priority: major|Component: c2s Version: 2.1.13 | Resolution: fixed Keywords: | Blocking: +--- Comment (by smoku): If the problem persists, or if there are any other related issues, please feel free to reopen the ticket. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/111#comment:13 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #111: jabberd-2.1.9 source distribution contain platform specifi characters and C prototype mismatches
#111: jabberd-2.1.9 source distribution contain platform specifi characters and
C
prototype mismatches
+---
Reporter: plmogan |Owner: smoku
Type: defect | Status: assigned
Priority: major|Component: c2s
Version: 2.1.13 | Resolution:
Keywords: | Blocking:
+---
Comment (by smoku):
The prototype mismatches are only warnings. These are also under GCC.
The problem is:
{{{
c2s.c, line 437: operands have incompatible types:
pointer to const unsigned char : pointer to char
}}}
I will commit a fix in a minute.
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/111#comment:11
jabberd2 http://jabberd2.xiaoka.com/
jabberd2 project
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #111: jabberd-2.1.9 source distribution contain platform specifi characters and C prototype mismatches
types: pointer to const unsigned char : pointer to char c2s.c, line 544: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : /usr/include/iso/string_iso.h, line 64 argument : pointer to unsigned char c2s.c, line 883: warning: argument #2 is incompatible with prototype: prototype: pointer to char : unknown, line 0 argument : pointer to unsigned char c2s.c, line 933: warning: argument #3 is incompatible with prototype: prototype: pointer to const char : ../sx/sx.h, line 172 argument : pointer to const unsigned char cc: acomp failed for c2s.c make[2]: *** [c2s-c2s.o] Error 2 make[2]: Leaving directory `/src/network/sources/jabberd-2.1.13/c2s' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/src/network/sources/jabberd-2.1.13' make: *** [all] Error 2 }}} '''Conclusions''' Unlike what I initially suspected, the failer is not caused by prototype mismatches. According to [http://docs.sun.com/source/819-3688/tguide.html Chapter 6 Transition to ISO C], the compiler's -Xa default actually accomodates KR syntaxes (see '''6.1.2'''). So, the problem is caused by the newly introduced constructs identified above. I hope the above findings can help resolve this ticket. Thanks, --Peter -- Ticket URL: http://jabberd2.xiaoka.com/ticket/111#comment:9 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #111: jabberd-2.1.9 source distribution contain platform specifi characters and C prototype mismatches
#111: jabberd-2.1.9 source distribution contain platform specifi characters and
C
prototype mismatches
+---
Reporter: plmogan |Owner: smoku
Type: defect | Status: assigned
Priority: major|Component: c2s
Version: 2.1.13 | Resolution:
Keywords: | Blocking:
+---
Comment (by plmogan):
Although I am still pressed by project pressure, I decided to stay late at
work and took another look of the {{{c2s.c}}} compilation problem. I soon
reached the conclusion that the SUN Studio 11 compiler doesn't like the
conditional expression {{{sess-jid?jid_full(sess-jid):unbound}}}, so I
replaced it with an equalent {{{if-else}}} contruct. Please see the
following context diff
{{{
# diff -c 2.1.13-c2s.c 2.1.13m-c2s.c
*** 2.1.13-c2s.cThu Aug 9 15:38:10 2007
--- 2.1.13m-c2s.c Thu Aug 9 21:14:31 2007
***
*** 442,449
case action_CLOSE:
log_debug(ZONE, close action on fd %d, fd-fd);
! log_write(sess-c2s-log, LOG_NOTICE, [%d] [%s, port=%d]
disconnect jid=%s, packets: %i, sess-fd-fd, sess-ip, sess-port,
sess-jid?jid_full(sess-jid):unbound, sess-packet_count);
!
/* tell the sm to close their session */
if(sess-active)
sm_end(sess);
--- 442,455
case action_CLOSE:
log_debug(ZONE, close action on fd %d, fd-fd);
! char *cptr;
! if (sess-jid)
! cptr = jid_full(sess-jid);
! else
! cptr = unbound;
!
! log_write(sess-c2s-log, LOG_NOTICE, [%d] [%s, port=%d]
disconnect jid=%s, packets: %i, sess-fd-fd, sess-ip, sess-port, cptr,
sess-packet_count);
!
/* tell the sm to close their session */
if(sess-active)
sm_end(sess);
}}}
Now the entire 2.1.13 distribution builds fine, despite lots of prototype
mismatch warnings. I however have not got time to test the build yet.
But at least this is a small progress. Perhaps someone else who has access
to SUN Studio compilers (now 12 is available for free download to both
Solaris and Linux) should give both the modified version and the original
a try. I have a suspicion that the compiler that we use might have a bug
:(
--Peter
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/111#comment:10
jabberd2 http://jabberd2.xiaoka.com/
jabberd2 project
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #78: c2s crash
#78: c2s crash -+-- Reporter: tofu |Owner: smoku Type: defect| Status: closed Priority: critical |Component: c2s Version: 2.1 | Resolution: fixed Keywords:| Blocking: -+-- Comment (by smoku): If it did not actually fix this bug, please reopen the ticket. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/78#comment:20 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #124: running jabberd 2.1.12 with electric fence
#124: running jabberd 2.1.12 with electric fence ---+ Reporter: tofu|Owner: smoku Type: defect | Status: new Priority: major |Component: General Version: 2.1.12 | Resolution: Keywords: | Blocking: ---+ Changes (by smoku): * status: assigned = new * version: 2.1.11 = 2.1.12 -- Ticket URL: http://jabberd2.xiaoka.com/ticket/124#comment:9 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #126: no SASL backend available out of: gsasl
#126: no SASL backend available out of: gsasl
-+--
Reporter: kt1660|Owner: smoku
Type: defect| Status: closed
Priority: critical |Component: Build
Version: 2.1.12| Resolution: invalid
Keywords:| Blocking:
-+--
Changes (by kt1660):
* priority: major = critical
Comment:
recompile gsasl 0.2.14, but error not resolve
{{{
checking gsasl.h usability... yes
checking gsasl.h presence... yes
checking for gsasl.h... yes
checking for gsasl_check_version in -lgsasl... yes
checking for GnuSASL version = 0.2.14... no
configure: error: no SASL backend available out of: gsasl
}}}
---
gsasl --version
{{{
gsasl 0.2.14
}}}
ls /usr/local/lib
{{{
libgsasl.a libgsasl.la libgsasl.so libgsasl.so.7 libgsasl.so.7.2.10
pkgconfig
}}}
Replying to [comment:1 smoku]:
Replying to [ticket:126 kt1660]:
configure error:
{{{
checking for GnuSASL version = 0.2.14... no
}}}
gsasl --version
{{{
gsasl 0.2.9
}}}
You need GnuSASL version 0.2.14 or greater.
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/126#comment:2
jabberd2 http://jabberd2.xiaoka.com/
jabberd2 project
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #126: no SASL backend available out of: gsasl
#126: no SASL backend available out of: gsasl ---+ Reporter: kt1660 |Owner: smoku Type: defect | Status: closed Priority: minor |Component: Build Version: 2.1.12 | Resolution: invalid Keywords: | Blocking: ---+ Changes (by smoku): * priority: critical = minor Comment: You still have lesser version of gsasl installed in system and it takes precedense. It's your local setup problem. Please report software bugs only via the ticket tracker and use mailing list to discuss local setup problems. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/126#comment:3 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #124: running jabberd 2.1.12 with electric fence
#124: running jabberd 2.1.12 with electric fence ---+ Reporter: tofu|Owner: smoku Type: defect | Status: new Priority: major |Component: General Version: 2.1.12 | Resolution: Keywords: | Blocking: ---+ Comment (by tofu): Just a note, we are using epoll backend and it seems type_CLOSED events are being generated. There are some cases where they are not. We have a crash when it is called sometimes. #78 is that crash. I can add another backtrace for that if you would like. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/124#comment:10 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #127: Implement Personal Eventing via Pubsub (XEP-163)
#127: Implement Personal Eventing via Pubsub (XEP-163) +--- Reporter: DeSnajpa | Owner: smoku Type: enhancement | Status: new Priority: major| Component: sm Version: 2.2 |Blocking: +--- Implement [http://www.xmpp.org/extensions/xep-0163.html PEP] as mod_pep or similar -- Ticket URL: http://jabberd2.xiaoka.com/ticket/127 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #127: Implement Personal Eventing via Pubsub (XEP-163)
#127: Implement Personal Eventing via Pubsub (XEP-163) +--- Reporter: DeSnajpa |Owner: smoku Type: enhancement | Status: new Priority: minor|Component: sm Version: | Resolution: Keywords: | Blocking: +--- Changes (by DeSnajpa): * priority: major = minor * version: 2.2 = -- Ticket URL: http://jabberd2.xiaoka.com/ticket/127#comment:1 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #124: running jabberd 2.1.12 with electric fence
#124: running jabberd 2.1.12 with electric fence ---+ Reporter: tofu|Owner: smoku Type: defect | Status: new Priority: major |Component: General Version: 2.1.11 | Resolution: Keywords: | Blocking: ---+ Changes (by jack): * cc: jack (added) -- Ticket URL: http://jabberd2.xiaoka.com/ticket/124#comment:6 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #124: running jabberd 2.1.12 with electric fence
#124: running jabberd 2.1.12 with electric fence
---+
Reporter: tofu|Owner: smoku
Type: defect | Status: new
Priority: major |Component: General
Version: 2.1.11 | Resolution:
Keywords: | Blocking:
---+
Comment (by tofu):
Now c2s, this seems to be something that happens without electric fence
too
{{{
Core was generated by `/home/chesspark/dev/bin/c2s -D -c
/home/chesspark/dev/etc/jabberd/c2s.xml'.
Program terminated with signal 11, Segmentation fault.
#0 _mio_run (m=0xf77d4e74, timeout=5) at mio_impl.h:257
257 if(FD(m,fd)-type == type_NORMAL MIO_CAN_WRITE(m,iter))
(gdb) backtrace
#0 _mio_run (m=0xf77d4e74, timeout=5) at mio_impl.h:257
#1 0x08053215 in main (argc=0, argv=0x0) at main.c:643
}}}
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/124#comment:2
jabberd2 http://jabberd2.xiaoka.com/
jabberd2 project
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #106: #items discovery leads to #info result
#106: #items discovery leads to #info result ---+ Reporter: elmex |Owner: smoku Type: defect | Status: new Priority: major |Component: General Version: 2.1.8 | Resolution: Keywords: | Blocking: ---+ Comment (by smoku): Could you please elaborate more, why do you think this is a defect? -- Ticket URL: http://jabberd2.xiaoka.com/ticket/106#comment:2 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #100: connection refused against 5222/5269 - ports appear unopened
#100: connection refused against 5222/5269 - ports appear unopened -+-- Reporter: dwaite|Owner: smoku Type: defect| Status: new Priority: critical |Component: General Version: 2.1.10| Resolution: Keywords:| Blocking: -+-- Changes (by mstevens): * version: 2.1.7 = 2.1.10 Comment: I also see this problem with jabberd 2.1.10 on FreeBSD 6.2. I'm getting nothing listening on port 5222, and 4 jabber processes using 100% of CPU between them. I'll attach a log of the debug output. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/100#comment:7 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #123: SASL backend available out of: gsasl
#123: SASL backend available out of: gsasl ---+ Reporter: hostserver |Owner: smoku Type: defect | Status: closed Priority: major |Component: Build Version: 2.1.7 | Resolution: invalid Keywords: | Blocking: ---+ Changes (by smoku): * status: new = closed * resolution: = invalid * component: General = Build Comment: You need at least 0.2.14 version of GnuSASL installed. If you do and it still does not work, please reopen the ticket. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/123#comment:1 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #100: connection refused against 5222/5269 - ports appear unopened
#100: connection refused against 5222/5269 - ports appear unopened -+-- Reporter: dwaite|Owner: smoku Type: defect| Status: new Priority: critical |Component: General Version: 2.1.10| Resolution: Keywords:| Blocking: -+-- Comment (by sxw): The 'jabberlog' debug trace would appear to be from a system using GnuSASL. What would help hugely, if you've got processes in a busy wait (using 100% of CPU), is to attach gdb to each of the processes, and produce a backtrace. If you need information on how to do this, let me know and I'd be happy to talk you through it. Simon. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/100#comment:9 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #119: Advertising registration as a stream feature
#119: Advertising registration as a stream feature ---+ Reporter: architecta |Owner: smoku Type: task| Status: closed Priority: major |Component: sm Version: 2.1.11 | Resolution: duplicate Keywords: | Blocking: ---+ Changes (by smoku): * status: new = closed * resolution: = duplicate Comment: dupe of #118 -- Ticket URL: http://jabberd2.xiaoka.com/ticket/119#comment:3 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #118: Advertising registration as a stream feature
#118: Advertising registration as a stream feature ---+ Reporter: architecta |Owner: smoku Type: task| Status: assigned Priority: major |Component: sm Version: 2.1.11 | Resolution: Keywords: | Blocking: ---+ Changes (by smoku): * status: new = assigned Comment: http://www.xmpp.org/registrar/stream-features.html -- Ticket URL: http://jabberd2.xiaoka.com/ticket/118#comment:1 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #120: postgresql detection code improvement.
#120: postgresql detection code improvement. +--- Reporter: hacker | Owner: smoku Type: enhancement | Status: new Priority: major| Component: storage Version: 2.1.11 |Blocking: +--- It's better to detect postgresql using pg_config as besides doing the right way it would also allow to select postgresql installation to be used. Not only I have files to attach to this ticket, but you should also expect more postgresql enhancement, since the module seems to lack userbase somewhat, at least none of those trying to combine ssl and postgresql authreg ;-) -- Ticket URL: http://jabberd2.xiaoka.com/ticket/120 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #121: more flexible mechanism for specifying postgresql connections for c2s
#121: more flexible mechanism for specifying postgresql connections for c2s +--- Reporter: hacker | Owner: smoku Type: enhancement | Status: new Priority: major| Component: storage Version: 2.1.11 |Blocking: +--- The PQconnectdb function is much more flexible than host/dbname/user/password, therefore this patch. It adds conninfo/ settings to authreg_pgsql module. In particular it lets met specify sslmode=disabled as a temporary workaround for an ssl/pgsql-ssl problem. Expect the fix for the problem soon, though. Again, the patch has a wordy header. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/121 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #122: let ssl in postgresql and jabberd coexist
#122: let ssl in postgresql and jabberd coexist ---+ Reporter: hacker | Owner: smoku Type: defect | Status: new Priority: major | Component: General Version: 2.1.11 |Blocking: ---+ That would involve preventing libpq from initializing openssl. One of the way to solve it is in the patch. That's supposed to be applied on top of my previous patch for 'conninfo' settings, I think it won't apply cleanly otherwise, but in fact it's totally independent. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/122 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #123: SASL backend available out of: gsasl
#123: SASL backend available out of: gsasl
---+
Reporter: hostserver | Owner: smoku
Type: defect | Status: new
Priority: major | Component: General
Version: 2.1.7 |Blocking:
---+
HELLO i have this error in fedora
{{{
checking for gsasl.h... yes
checking for gsasl_check_version in -lgsasl... yes
checking for GnuSASL version = 0.2.14... no
configure: error: no SASL backend available out of: gsasl
[EMAIL PROTECTED] jabberd]#
}}}
I edit ld.so.conf
nano/etc/ld.so.conf
and add
include /etc/ld.so.conf.d/*.conf
/usr/local/lib
But this no work how i solve this
Thanks
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/123
jabberd2 http://jabberd2.xiaoka.com/
jabberd2 project
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #119: Advertising registration as a stream feature
#119: Advertising registration as a stream feature ---+ Reporter: architecta | Owner: smoku Type: task| Status: new Priority: major | Component: sm Version: 2.1.11 |Blocking: ---+ It would be good if jabberd2 advertises registration as a stream feature. Some XMPP libraries such as the agsXMPP SDK has some problems with registration on jabberd2 as the server doesn't advertise it as a stream feature. This cause the client to think that registration is not allowed on the server though it is. I tried to force the library to send a Register IQ stanza even if the server doesn't advertise registration as a stream feature and it worked. But it would be great if jabberd2 supports that registration stream feature. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/119 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [Jabberd2] [jabberd2] #107: c2s crash in sasl_server_step
#107: c2s crash in sasl_server_step
+---
Reporter: bmuller |Owner: sxw
Type: defect | Status: new
Priority: major|Component: c2s
Version: 2.1.8| Resolution:
Keywords: | Blocking:
+---
Comment (by bmuller):
Here's the output from valgrind:
{{{
==14039== Invalid read of size 4
==14039==at 0x647FFDF: (within /usr/lib/sasl2/libdigestmd5.so.2.0.22)
==14039==by 0x45D42E6: sasl_server_step (in
/usr/lib/libsasl2.so.2.0.22)
==14039==by 0x805E103: _sx_sasl_client_process (sasl_cyrus.c:764)
==14039==by 0x805E969: _sx_sasl_process (sasl_cyrus.c:904)
==14039==by 0x805786F: _sx_process_read (io.c:125)
==14039==by 0x8057C98: sx_can_read (io.c:218)
==14039==by 0x8050F19: _c2s_client_mio_callback (c2s.c:432)
==14039==by 0x8060B4F: _mio_run (mio_impl.h:251)
==14039==by 0x805578E: main (main.c:639)
==14039== Address 0x0 is not stack'd, malloc'd or (recently) free'd
==14039==
==14039== Process terminating with default action of signal 11 (SIGSEGV):
dumping core
==14039== Access not within mapped region at address 0x0
==14039==at 0x647FFDF: (within /usr/lib/sasl2/libdigestmd5.so.2.0.22)
==14039==by 0x45D42E6: sasl_server_step (in
/usr/lib/libsasl2.so.2.0.22)
==14039==by 0x805E103: _sx_sasl_client_process (sasl_cyrus.c:764)
==14039==by 0x805E969: _sx_sasl_process (sasl_cyrus.c:904)
==14039==by 0x805786F: _sx_process_read (io.c:125)
==14039==by 0x8057C98: sx_can_read (io.c:218)
==14039==by 0x8050F19: _c2s_client_mio_callback (c2s.c:432)
==14039==by 0x8060B4F: _mio_run (mio_impl.h:251)
==14039==by 0x805578E: main (main.c:639)
}}}
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/107#comment:8
jabberd2 http://jabberd2.xiaoka.com/
jabberd2 project
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #115: Problem with user_agent and muc
5 seq 3)
Jul 24 23:41:52 p jabberd/sm[16665]: module 'status' added to chain 'user-
delete' (order 7 index 0 seq 3)
Jul 24 23:41:52 p jabberd/sm[16665]: module 'iq-last' added to chain
'user-delete' (order 8 index 1 seq 3)
Jul 24 23:41:52 p jabberd/sm[16665]: module 'iq-private' added to chain
'user-delete' (order 9 index 8 seq 1)
Jul 24 23:41:52 p jabberd/sm[16665]: module 'iq-vcard' added to chain
'user-delete' (order 10 index 6 seq 2)
Jul 24 23:41:52 p jabberd/sm[16665]: version: jabberd sm 2.1.6
Jul 24 23:41:52 p jabberd/sm[16665]: attempting connection to router at
127.0.0.1, port=5347
Jul 24 23:41:52 p jabberd/router[16663]: [127.0.0.1, port=52255] connect
Jul 24 23:41:52 p jabberd/router[16663]: [127.0.0.1, port=52255]
authenticated as [EMAIL PROTECTED]
Jul 24 23:41:52 p jabberd/sm[16665]: connection to router established
Jul 24 23:41:52 p jabberd/router[16663]: [jabber.sko**.***] online (bound
to 127.0.0.1, port 52255)
Jul 24 23:41:52 p jabberd/c2s[16667]: initialized auth module 'mysql'
Jul 24 23:41:52 p jabberd/c2s[16667]: [jabber.sko**.***] configured;
realm=(null), registration disabled
Jul 24 23:41:52 p jabberd/c2s[16667]: attempting connection to router at
127.0.0.1, port=5347
Jul 24 23:41:52 p jabberd/router[16663]: [127.0.0.1, port=52256] connect
Jul 24 23:41:52 p jabberd/router[16663]: [127.0.0.1, port=52256]
authenticated as [EMAIL PROTECTED]
Jul 24 23:41:52 p jabberd/c2s[16667]: connection to router established
Jul 24 23:41:52 p jabberd/router[16663]: [c2s] online (bound to 127.0.0.1,
port 52256)
Jul 24 23:41:52 p jabberd/sm[16665]: ready for sessions
Jul 24 23:41:52 p jabberd/c2s[16667]: [0.0.0.0, port=5222] listening for
connections
Jul 24 23:41:52 p jabberd/c2s[16667]: ready for connections
Jul 24 23:41:54 p jabberd/router[16663]: [127.0.0.1, port=52257] connect
Jul 24 23:41:54 p jabberd/router[16663]: [127.0.0.1, port=52257]
authenticated as conferenceroom
Jul 24 23:41:54 p jabberd/router[16663]: [conferenceroom] online (bound to
127.0.0.1, port 52257)
Jul 24 23:41:54 p jabberd/router[16663]: [conference.sko**.***] online
(alias of 'conferenceroom', bound to 127.0.0.1, po
Jul 24 23:41:57 p jabberd/router[16663]: [62., port=52258] connect
Jul 24 23:41:57 p jabberd/router[16663]: [62., port=52258]
authenticated as jud.sko**.**
Jul 24 23:41:57 p jabberd/router[16663]: [jud.sko**.**] online (bound to
62.75., port 52258)
}}}
i use the pandion can connect to the server but i cannot search the
useragentlist i cannt create a jid
and i cannt connect to a room
i cannt create a room
what is wrong
how cann i connect to a room how can i generate a jid?
when i connect
{{{
Jul 24 23:50:06 p jabberd/s2s[17605]: [7] [213., port=21439] incoming
connection
Jul 24 23:50:06 p jabberd/s2s[17605]: [7] [213., port=21439] incoming
stream online (id jysxi2o19cjifxswjk09soircrvuq979707p2wrc)
}}}
help plz
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/115
jabberd2 http://jabberd2.xiaoka.com/
jabberd2 project
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[Jabberd2] [jabberd2] #116: gsasl login failure
#116: gsasl login failure
---+
Reporter: tofu| Owner: smoku
Type: defect | Status: new
Priority: major | Component: c2s
Version: 2.1.8 |Blocking:
---+
When I have gsasl as the backend and a client parses the challenge
incorrectly and sends the wrong response the server responds with the
following :
{{{
failure xmlns='urn:ietf:params:xml:ns:xmpp-sasl'temporary-auth-
failure//failure
}}}
This is not the case. it's not a temporary server issue preventing auth
This should be another error.
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/116
jabberd2 http://jabberd2.xiaoka.com/
jabberd2 project
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[jabberd2] #113: postgresql storage should not be using serializable transactions
#113: postgresql storage should not be using serializable transactions ---+ Reporter: jack| Owner: smoku Type: defect | Status: new Priority: major | Component: storage Version: 2.1.7 |Blocking: ---+ This is not banking software. I believe that the original author must have used serializable because he was unfamiliar with transaction levels. We should be using the normal read committed level, which is enough for the purpose at hand. After all, there is no retry code if a serializable transaction fails is there? So it is implemented incorrectly anyway. Also, we need to get rid of the overhead of setting the transaction isolation level for every transaction. This can be done when the connection is established and will save a lot of time. Also, we should not be using BEGIN/END blocks on singleton inserts. We're working on paches for all these, but I wanted to open a bug here for feedback and to track the status. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/113 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [jabberd2] #114: doesn't check the availability of libexpat
#114: doesn't check the availability of libexpat
---+
Reporter: bencer |Owner: smoku
Type: defect | Status: assigned
Priority: major |Component: Build
Version: 2.1.7 | Resolution:
Keywords: | Blocking:
---+
Changes (by smoku):
* status: new = assigned
Comment:
It sure does.
{{{
[EMAIL PROTECTED]:~/devel/jabberd2$ grep expat configure.ac
AC_CHECK_LIB([expat], [XML_ParserCreate])
if test x-$ac_cv_lib_expat_XML_ParserCreate = x- ; then
}}}
Could you please attach your {{{config.log}}}?
--
Ticket URL: http://jabberd2.xiaoka.com/ticket/114#comment:1
jabberd2 http://jabberd2.xiaoka.com/
jabberd2 project
___
Jabberd2 mailing list
Jabberd2@lists.xiaoka.com
http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [jabberd2] #111: jabberd-2.1.9 source distribution contain platform specifi characters and C prototype mismatches
#111: jabberd-2.1.9 source distribution contain platform specifi characters and C prototype mismatches +--- Reporter: plmogan |Owner: smoku Type: defect | Status: assigned Priority: major|Component: c2s Version: 2.1.8| Resolution: Keywords: | Blocking: +--- Comment (by plmogan): Replying to [comment:6 smoku]: Please describe what exact changes you need to make to make it compile. Or a diff would be nice. (I do not have Solaris machine at hand to debug it.) Hello, Judging from my experience building jabberd2 (from 2.0sx to 2.1.x) and tolerated this defect for years, I would say it does work incorrectly. Regards, --Peter -- Ticket URL: http://jabberd2.xiaoka.com/ticket/111#comment:7 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [jabberd2] #111: jabberd-2.1.9 source distribution contain platform specifi characters and C prototype mismatches
#111: jabberd-2.1.9 source distribution contain platform specifi characters and C prototype mismatches +--- Reporter: plmogan |Owner: smoku Type: defect | Status: assigned Priority: major|Component: c2s Version: 2.1.8| Resolution: Keywords: | Blocking: +--- Comment (by plmogan): Replying to [comment:7 plmogan]: Replying to [comment:6 smoku]: Please describe what exact changes you need to make to make it compile. Or a diff would be nice. (I do not have Solaris machine at hand to debug it.) Hello, Thanks for your attention to this ticket. Below is what I have done to get most of the source to compile with the following settings: Before running ./configure, do the following: in tcsh setenv CPPFLAGS '-I/usr/local/include -I/usr/local/include/openssl -I/usr/local/include/mysql' setenv LDFLAGS '-L/usr/local/lib -R/usr/local/lib -L/usr/local/lib/mysql -R/usr/local/lib/mysql -s' As you can tell, we build and package everything we use. Then, follow the hints given in http://jabberd2.xiaoka.com/wiki/SunOSInstallation not only for sm, but also for c2s as well. I mentioned explicitly the --export-dynamic GCC specific option which chocks the much superior SUN Studio 11/12 compilers, whichare also freely available to various flavors of Linux. Please note, I am not knocking on CCC. I only state a easily verifiable fact that SUN's free compilers produces simply much superior executables. A fact that even Apache folks acknowledges openly in their doc. After receiving a lot errors like the following: make[2]: Entering directory `/src/network/sources/jabberd-2.1.9/c2s' source='c2s.c' object='c2s-c2s.o' libtool=no \ DEPDIR=.deps depmode=none /bin/bash ../depcomp \ /opt/SUNWspro/bin/cc -DHAVE_CONFIG_H -I. -I.. -DCONFIG_DIR=\/usr/local/etc\ -DLIBRARY_DIR=\/usr/local/lib/jabberd\ -I/usr/local/include -I/usr/local/include/openssl -I/usr/local/include/mysql -xO3 -xbuiltin -xdepend=yes -xprefetch=auto,explicit -xarch=v8plusa -xcache=16/32/1:256/64/4 -xchip=ultra2e -c -o c2s-c2s.o `test -f 'c2s.c' || echo './'`c2s.c c2s.h, line 21: warning: invalid white space character in directive c2s.h, line 22: warning: invalid white space character in directive c2s.h, line 23: warning: invalid white space character in directive c2s.h, line 25: warning: invalid white space character in directive c2s.h, line 27: warning: invalid white space character in directive ../mio/mio.h, line 21: warning: invalid white space character in directive [... many more ...] I immediately became suspicious. vi c2s/c2s.h immediately showed these familiar ^M \r characters. My conjecture is that somehow the recent Microsoft Windows port introduced these codes, as whoever worked on such ports took the original sources and edited in Windows environment, overlooking the need to clean up the end of line characters are the porting was done. To prevent similar accidents in the future, perhaps a system that emulates what Apache and PHP people have done in this regard would be fruitful. I then simply used a for file in *.[ch] do dos2unix -ascii -iso $file $file done in ech source directory (e.g. c2s, sm, router, resolver...) to clean out all files just in case. I didn't check each and every file. The above shell script is easy and fast. I still haven't got time to investigate the prototype mismatch problem yet. A quick diff showed that there are substantial changes introduced in c2s.c from 2.1.6 to 2.1.9. Since 2.1.6 so far works fine for us, and since I am working on a pressing project now, I will have to do it some other time. If someone could fix these mismatches before I can, I would be more than happy to test build. That, I can squeeze out sometime. Just a final reminder, for people who are curious about the excellent and freely available SUN Studio compiler suite, please see http://developers.sun.com/sunstudio/index.jsp For people who don't have a computer running Solaris or the freely available OpenSolaris (yes, you get source for this OS too), but use Linux instead, please see http://developers.sun.com/sunstudio/linux_index.html I have years of experience using both GCC (I still do) and SUN Studio compiler suite. The later almost always generate bigger executables, but often much faster too. Given today's computers with large RAM, of course my preference is to build everything with SUN compilers. It also has much superior online documentation at http://docs.sun.com/ too. Regards, --Peter -- Ticket URL: http://jabberd2.xiaoka.com/ticket/111#comment:8 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2
Re: [jabberd2] #78: c2s crash
#78: c2s crash -+-- Reporter: tofu |Owner: smoku Type: defect| Status: new Priority: critical |Component: c2s Version: 2.1 | Resolution: Keywords:| Blocking: -+-- Changes (by tofu): * version: 2.1.6 = 2.1 Comment: Are you asking if it received signal SIGABRT? Or if it crashes when it gets that? I believe it is a Core 2 Duo E6700 2.66GHz. Running on debian stable. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/78#comment:10 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [jabberd2] #78: c2s crash
#78: c2s crash -+-- Reporter: tofu |Owner: smoku Type: defect| Status: new Priority: critical |Component: c2s Version: 2.1 | Resolution: Keywords:| Blocking: -+-- Comment (by tofu): Replying to [comment:11 smoku]: Yes, I'm asking wether it recieved SIGABRT. The default handler for this signal is crashdump. No, it was just running normally and then crashed. Is Core 2 Duo an IA32 or IA64? IA64. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/78#comment:12 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [jabberd2] #78: c2s crash
#78: c2s crash -+-- Reporter: tofu |Owner: smoku Type: defect| Status: new Priority: critical |Component: c2s Version: 2.1 | Resolution: Keywords:| Blocking: -+-- Comment (by smoku): Replying to [comment:12 tofu]: Replying to [comment:11 smoku]: Yes, I'm asking wether it recieved SIGABRT. The default handler for this signal is crashdump. No, it was just running normally and then crashed. But which signal caused the crash? This really matters, because SIGABRT (on the contrary to ex. SIGSEGV) is generated programatically not by kernel. Is Core 2 Duo an IA32 or IA64? IA64. Shish... Deep in-libc IA64 specific crash... It's going to be hard... -- Ticket URL: http://jabberd2.xiaoka.com/ticket/78#comment:13 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [jabberd2] #78: c2s crash
#78: c2s crash -+-- Reporter: tofu |Owner: smoku Type: defect| Status: new Priority: critical |Component: c2s Version: 2.1 | Resolution: Keywords:| Blocking: -+-- Comment (by smoku): Yes, I'm asking wether it recieved SIGABRT. The default handler for this signal is crashdump. Is Core 2 Duo an IA32 or IA64? -- Ticket URL: http://jabberd2.xiaoka.com/ticket/78#comment:11 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [jabberd2] #78: c2s crash
#78: c2s crash -+-- Reporter: tofu |Owner: smoku Type: defect| Status: new Priority: critical |Component: c2s Version: 2.1 | Resolution: Keywords:| Blocking: -+-- Comment (by tofu): Core was generated by `/home/chesspark/production/bin/c2s -c /home/chesspark/production/etc/jabberd/c2'. Program terminated with signal 11, Segmentation fault. #0 0xf7b61c85 in malloc_usable_size () from /lib/tls/i686/cmov/libc.so.6 So SIGSEGV caused it. I know it is hard, we are looking into it too. We need all the help we can get, we would like to continue to use jabberd2. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/78#comment:14 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[jabberd2] #111: jabberd-2.1.9 source distribution contain platform specifi characters and C prototype mismatches
#111: jabberd-2.1.9 source distribution contain platform specifi characters and C prototype mismatches +--- Reporter: plmogan | Owner: smoku Type: defect | Status: new Priority: major| Component: c2s Version: 2.1.8|Blocking: +--- In jabberd-2.1.9, many C header and source contains the MSDOS \r\n instead of just \n, thus choking the freely available SUN Studio 11 C compiler. We have to use the SUN Solaris dos2unix -ascii -iso in a shell script to clean up these extra end of line characters to proceed. Then, we ran into ANSI C prototype mismatching problems, as shown below: c2s.c, line 218: warning: argument #2 is incompatible with prototype: prototype: pointer to const unsigned char : ../util/util.h, line 251 argument : pointer to char c2s.c, line 236: warning: argument #4 is incompatible with prototype: prototype: pointer to const unsigned char : ../util/util.h, line 259 argument : pointer to char c2s.c, line 277: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : /usr/include/iso/string_iso.h, line 69 argument : pointer to const unsigned char c2s.c, line 277: warning: argument #2 is incompatible with prototype: prototype: pointer to const char : ../util/nad.h, line 158 argument : pointer to const unsigned char c2s.c, line 445: operands have incompatible types: pointer to const unsigned char : pointer to char c2s.c, line 552: warning: argument #1 is incompatible with prototype: prototype: pointer to const char : /usr/include/iso/string_iso.h, line 64 argument : pointer to unsigned char c2s.c, line 891: warning: argument #2 is incompatible with prototype: prototype: pointer to char : unknown, line 0 argument : pointer to unsigned char c2s.c, line 941: warning: argument #3 is incompatible with prototype: prototype: pointer to const char : ../sx/sx.h, line 172 argument : pointer to const unsigned char cc: acomp failed for c2s.c make[2]: *** [c2s-c2s.o] Error 2 make[2]: Leaving directory `/src/network/sources/jabberd-2.1.9/c2s' The configure generated Makefiles for both c2s and sm seems to assume that everyone is using GCC, thus the GCC specific -export-dynamic is used in Makefiles for both. This again chocks the SUN Studio C compiler. Each time we build jabberd2 on SUN UltraSPARC Solaris 10 machines, we have to manually fix these. 2.1.6 built fine, but with the new prototype mismatch errors with 2.1.9, we will have to spend some time to look and see. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/111 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
[jabberd2] #112: disallowing unquoted XML predefined entities
#112: disallowing unquoted XML predefined entities -+-- Reporter: smoku | Owner: smoku Type: defect| Status: new Priority: critical | Component: XMPP Complaince Version: 2.1 |Keywords: Blocking:| -+-- The XML predefined entities: http://www.w3.org/TR/2006/REC-xml-20060816 /#sec-predefined-ent are not allowed in XMPP stream: http://www.xmpp.org/rfcs/rfc3920.html#xml-restrictions We MUST not produce them in outgoing stream and we MUST ignore them. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/112 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [jabberd2] #78: c2s crash
#78: c2s crash -+-- Reporter: tofu |Owner: smoku Type: defect| Status: new Priority: critical |Component: c2s Version: 2.1 | Resolution: Keywords:| Blocking: -+-- Comment (by tofu): Sure, I will get back with the results. -- Ticket URL: http://jabberd2.xiaoka.com/ticket/78#comment:16 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ Jabberd2 mailing list Jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
Re: [jabberd2] #110: util/uri.h integration
#110: util/uri.h integration +--- Reporter: smoku|Owner: smoku Type: task | Status: new Priority: trivial |Component: General Version: 2.2 | Resolution: Keywords: | Blocking: +--- Changes (by smoku): * type: defect = task -- Ticket URL: http://jabberd2.xiaoka.com/ticket/110#comment:1 jabberd2 http://jabberd2.xiaoka.com/ jabberd2 project ___ jabberd2 mailing list jabberd2@lists.xiaoka.com http://lists.xiaoka.com/listinfo.cgi/jabberd2-xiaoka.com
