RE: [JDEV] password authentication
Hi Tony, take a look at some samples in download.jabber.org specifically ldapauth.tar.gz I am making a similar authentication control there ... let me know if I can be of more help! zad -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Tony Byers Sent: Thursday, May 10, 2001 2:40 PM To: [EMAIL PROTECTED] Subject: [JDEV] password authentication Hello - I've been trying to figure out where the passwords from the client and server are checked. I've been looking in mod_auth_plain.c and I see where it is comparing the passwords in mreturn mod_auth_plain_jane but it never gets past if(jpacket_subtype(m-packet) == JPACKET__GET). It goes into this section and returns. All I want to do is add a call to a kerberos function with the password from the client. All I really need is a place where I can get the password from the client and attempt to get a kerberos ticket and fail authentication if I can't. Thanks in advance for any advice. Tony Byers ___ To get your own FREE ZDNet Onebox - FREE voicemail, email, and fax, all in one place - sign up today at http://www.zdnetonebox.com ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
[JDEV] password encription
Hi Guys... I am using Jabber Server-1.4.1 can you please advice me how will I encrypted passwdrather than plain text. Thanx in advance regards dillip
Re: [JDEV] Server feature request
In the next iteration of server development, MIO will be modified such that it will not will use SIGUSR2 for this. Having debugging turned on via SIGUSR2 is intriguing and we'll look into that for the next iteration. Probably, it would simply be used as a boolean -- if debugging is off SIGUSR2 would turn it on and vice-versa. This way we don't need to have so many signals just to turn debugging on and off. Diz On Thu, May 10, 2001 at 10:53:25PM -0500, temas wrote: SIGUSR2 is used by mio as a mechanism to break the loop so new sockets can be added and stuff like that. --temas On 10 May 2001 18:18:23 -0600, David Waite wrote: [EMAIL PROTECTED] wrote: Those are the definitions of those signals in BIND though. They have different (already used) meaning within Jabber - they are used by pth (and I believe MIO). They are simply user-defined signals. Right, exactly. So we pick two new signals to serve this purpose in Jabber, the concept is still the same. So we use SIGINFO to turn on debugging, and SIGWINCH to turn it off, or any two other signals that are not already taken. It would also be useful to have the ability to turn debugging on and off by sending an admin message, but the signal method is more important, as it would be very useful to debugging cases where I cannot connect/login at all, and thuse cannot send any messages... I'd welcome any two other signals which are not already taken. The system or parent process sends those signals. I do not believe SIGINFO is defined on i386, its also mapped to SIGPWR which is an exit on some other platforms, SIGWINCH is sent whenever the terminal size changes - it sure wouldn't help me debug if the program behavior changed when I resized the terminal I was getting output in :-). If those signals weren't used internally, I agree it would be a really nice feature to add (you actually only need one signal as a toggle, really). What is SIGUSR2 really used for? Kevin -David Waite [EMAIL PROTECTED] wrote: Server feature request, the ability to turn debugging on/off by sending a Unix signal to the jabberd process, something like this: SIGUSR1 Turns on debugging; each SIGUSR1 increments debug level. (SIGEMTon older systems without SIGUSR1.) SIGUSR2 Turns off debugging completely. (SIGFPEon older systems without SIGUSR2.) The astute observer will notice that the two paragraphs above are verbatim from the documentation for BIND :-) ... Yes!! It's been a long time I was thinking about it! In certain cases it is just necessary... /MAciek On Thu, 10 May 2001 11:45:35 -0600 Malone, Pat wrote: In trying to work through a nasty client problem today, I had 'if only' thought pass through my head. So, here is a wish item for the jabberd developer gods: Enable the ability to send a sig of some kind to jabberd to toggle debugging on and off, a.k.a. the way debug can be toggled with named. It sure would be nice to toggle debug on when a problem shows up without having to kill the server. ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] password encription
I'm sure there has been discussion of this on the JADMIN list (visit http://mailman.jabber.org/listinfo/jadmin/ to sign up), which is dedicated to issues of this kind (as opposed to the JDEV list, which is for software development questions). However, it's good to know that the order of modules in the load main=jsm section of jabber.xml is important, since it determines the order in which various modules are called. So in order to make sure that plaintext passwords are not an option, you could simply comment out the following line in the load main=jsm section: mod_auth_plain./jsm/jsm.so/mod_auth_plain Alternatively, you could change the order of modules so that mod_auth_plain comes after mod_auth_digest and/or mod_auth_0k/, in which case plaintext passwords would still be possible (you might want to do this in order to support telnet access, server test scripts, or whatever). Peter -- Peter Saint-Andre [EMAIL PROTECTED] Dillip Kumar Swain wrote: /Hi Guys.../ /I am using Jabber Server-1.4.1/ /can you please advice me how will I encrypted passwd rather than plain text./ /Thanx in advance/ /regards/ /dillip/ ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
RE: [JDEV] Server feature request
This might make it a bit annoying to write automated scripts... Unless we have some way of finding out what state the server is in? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, May 11, 2001 9:05 AM To: [EMAIL PROTECTED] Subject: Re: [JDEV] Server feature request In the next iteration of server development, MIO will be modified such that it will not will use SIGUSR2 for this. Having debugging turned on via SIGUSR2 is intriguing and we'll look into that for the next iteration. Probably, it would simply be used as a boolean -- if debugging is off SIGUSR2 would turn it on and vice-versa. This way we don't need to have so many signals just to turn debugging on and off. Diz On Thu, May 10, 2001 at 10:53:25PM -0500, temas wrote: SIGUSR2 is used by mio as a mechanism to break the loop so new sockets can be added and stuff like that. --temas On 10 May 2001 18:18:23 -0600, David Waite wrote: [EMAIL PROTECTED] wrote: Those are the definitions of those signals in BIND though. They have different (already used) meaning within Jabber - they are used by pth (and I believe MIO). They are simply user-defined signals. Right, exactly. So we pick two new signals to serve this purpose in Jabber, the concept is still the same. So we use SIGINFO to turn on debugging, and SIGWINCH to turn it off, or any two other signals that are not already taken. It would also be useful to have the ability to turn debugging on and off by sending an admin message, but the signal method is more important, as it would be very useful to debugging cases where I cannot connect/login at all, and thuse cannot send any messages... I'd welcome any two other signals which are not already taken. The system or parent process sends those signals. I do not believe SIGINFO is defined on i386, its also mapped to SIGPWR which is an exit on some other platforms, SIGWINCH is sent whenever the terminal size changes - it sure wouldn't help me debug if the program behavior changed when I resized the terminal I was getting output in :-). If those signals weren't used internally, I agree it would be a really nice feature to add (you actually only need one signal as a toggle, really). What is SIGUSR2 really used for? Kevin -David Waite [EMAIL PROTECTED] wrote: Server feature request, the ability to turn debugging on/off by sending a Unix signal to the jabberd process, something like this: SIGUSR1 Turns on debugging; each SIGUSR1 increments debug level. (SIGEMTon older systems without SIGUSR1.) SIGUSR2 Turns off debugging completely. (SIGFPEon older systems without SIGUSR2.) The astute observer will notice that the two paragraphs above are verbatim from the documentation for BIND :-) ... Yes!! It's been a long time I was thinking about it! In certain cases it is just necessary... /MAciek On Thu, 10 May 2001 11:45:35 -0600 Malone, Pat wrote: In trying to work through a nasty client problem today, I had 'if only' thought pass through my head. So, here is a wish item for the jabberd developer gods: Enable the ability to send a sig of some kind to jabberd to toggle debugging on and off, a.k.a. the way debug can be toggled with named. It sure would be nice to toggle debug on when a problem shows up without having to kill the server. ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
RE: [JDEV] Customizing Jabber server
Title: RE: [JDEV] Customizing Jabber server You can register external handlers for everything. Instead of setting it up in an xdb section, just configure a service entry, and give it a service name, connect with your service, and I believe it should start picking up all requests, filter out the ones that aren't presence and do what you will with presence. Matt Diez -Original Message- From: Gerard BUNEL [mailto:[EMAIL PROTECTED]] Sent: Friday, May 11, 2001 2:38 AM To: [EMAIL PROTECTED] Subject: Re: [JDEV] Customizing Jabber server Big Thanks for this answer I can't really use xdb_java as its purpose is to do some JDBC invocations. But it's quite the same functionalities I was looking. I didn't understand that it was possible do regsiter a foreign handler to handle XDB requests. Do you know if it's also possible for all type of requests ? I'm, for example, interested in handling presence messages Colin Madere a écrit : Take a look at xdb_java, as John Hebert suggests. You should be able to add your own modules to it to talk to the App Server for the services you mention. (Or, at least that's what Matt told me the last time we met :) ) It is a budding project, but is constantly being improved and we plan to use it on a large scale here, so be assured it is not intended to be a toy project. Colin Madere Vedalabs, Inc. -Original Message- From: Gerard BUNEL [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 09, 2001 10:44 AM To: [EMAIL PROTECTED] Subject: Re: [JDEV] Customizing Jabber server wasted a écrit : we're working on similar types of issues and my take on it this... jabber isn't an application server itself. it facilitates the routing of messages to the appropriate destination - normally a human for chat. of course the destination can be an agent or a transport with business/application logic coded for a purpose which returns some data or whatever. an agent could be a stock watcher, a weather man, a news grabber, data mine - the list is endless. you can write an agent in almost any language with all the cool tools the dev guys have done - Net::Jabber, JabberCOM, JabberBeans, etc... i'm partial to JabberBeans 'cause we do a lot of Java programming. then again, as JAM develops, jabber could become more application server-ish. not sure if that's the sorta explanation you're looking for, but i hope it helps. I'm not trying to application-server-ish the jabber server. I just want to filter some parts of the jabber protocol so that information is provided by the application server instead of the Jabber server itself (by the mean of the default xdb_file). I think that for authentication, Rosters, vCard this can be obtained by bootstraping the xdb_file to delegate the requests to the application server (that we also develop, this is a specialized one, not a J2EE server). Our application server is Java based and we also have a look to JabberBeans. I've also pointed out the JAM effort on Jabber but, as I need such functionalities rather quickly (Pre-version for July) we focused our interest on Xml-Rpc and made some trials in embedding Xml-Rpc requests into the Jabber protocol. We did that successfully. ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev -- [EMAIL PROTECTED] - Atlantide - http://www.ago.fr/atlantide/ Technopole Brest Iroise BP 80802 - Site du Vernis - 29608 Brest cedex - France Tel. : +33 2 98 05 43 21 - Fax. : +33 2 98 05 20 34 e-mail: [EMAIL PROTECTED] Centre Affaires Oberthur - 74D, rue de Paris - 35700 Rennes - France Tel. : +33 2 99 84 15 84 - Fax : +33 2 99 84 15 85 e-mail: [EMAIL PROTECTED]
[JDEV] Re: Implementing Jabber Server in other Languages (Was RE: [JDEV]Cus tomizing Jabber server)
This is one of the exact goals of the Foundation, to have a formalized process for working on the protocol. Jabelin will then be the group to work on server development. Some more info about this should be out today or tomorrow. --temas On 11 May 2001 08:50:50 -0500, Iain Shigeoka wrote: At 02:42 PM 5/9/2001 -0500, John Hebert wrote: On second thought - David Waite's right - we have to look at separating protocol from server implementation. My point all along. Apache has the W3C. What does Jabber have? Do we need a separate jabber protocol effort separate from the server devel effort? Yes. We need to separate protocol from implementation. Most people I've spoken to are at least philosophically in agreement on this issue. This has been a problem since Jabber has evolved as an implementation that defined the protocol. IMHO the time has really come to split the protocol off. Jabber has remained coherent until now because there has only been one server implementation available so the implementation has defined the protocol. However, as Jabber.com now as a separate server (albiet very closely related) and there are other efforts to develop servers, a separate protocol standard is going to become essential. As I understand it, this is something that we can use the Jabber Foundation as a tool to help us accomplish. FYI, I'm very interested in the protocol and implementing my own Jabber server (in Java not Python) and have little/no interest in the current C implementation. Reading the protocol docs from this perspective has really been what's gotten me interested in better defining the protocols to stand alone from the implementation. As it stands now, it is pretty much impossible to write a server based on the existing protocols because they are incomplete. In addition, there is no way to test your protocol compliance except in relationship to the current C implementation. I'm hoping to also work on addressing that issue as well (standard compliance when a standard exists). -iain _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
[JDEV] jabberbeans Question?
Hi, I am using the latest jabberbeans JabberBeans-0.9.0-pre4 and I would like to know how to subscrive yahoo and msn transport to a java client using jabber server 1.4.1?? The code is working fine but I have to logout the client and log back in to see the transport work properly Thanks Anand _ Get your FREE download of MSN Explorer at http://explorer.msn.com ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
RE: [JDEV] jabberbeans Question?
Hey can you share your jabber client with the group... I'm looking for a jabber client to incorporate it in a big software project... so if you can do so I'll appreciate it.. :) well, later and thanks.. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of anand v Sent: Friday, May 11, 2001 6:19 PM To: [EMAIL PROTECTED] Subject: [JDEV] jabberbeans Question? Hi, I am using the latest jabberbeans JabberBeans-0.9.0-pre4 and I would like to know how to subscrive yahoo and msn transport to a java client using jabber server 1.4.1?? The code is working fine but I have to logout the client and log back in to see the transport work properly Thanks Anand _ Get your FREE download of MSN Explorer at http://explorer.msn.com ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Server feature request
Huh? What are you wanting to do with such a script? Diz On Fri, May 11, 2001 at 09:24:06AM -0700, Max Metral wrote: This might make it a bit annoying to write automated scripts... Unless we have some way of finding out what state the server is in? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Friday, May 11, 2001 9:05 AM To: [EMAIL PROTECTED] Subject: Re: [JDEV] Server feature request In the next iteration of server development, MIO will be modified such that it will not will use SIGUSR2 for this. Having debugging turned on via SIGUSR2 is intriguing and we'll look into that for the next iteration. Probably, it would simply be used as a boolean -- if debugging is off SIGUSR2 would turn it on and vice-versa. This way we don't need to have so many signals just to turn debugging on and off. ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
[JDEV] passwords
Hello - I thought I had this figured out but I don't. Does anyone know how to obtain the password from the client in any of the mod_auth files. I've stuck the following line in many different places and password is always NULL. password = xmlnode_get_tag_data(m-packet-iq, password); I've commented out mod_auth_digest and mod_auth_0k in jabber.xml so I'm assuming that password verification must be done in mod_auth_plain_jane. Any information about the client password would be great. I'm totally lost at this point. Tony Byers ___ To get your own FREE ZDNet Onebox - FREE voicemail, email, and fax, all in one place - sign up today at http://www.zdnetonebox.com ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
[JDEV] EtherX vs. Transports
I was thinking of writing a Jabber transport to access my company's proprietary IM system, but several major problems arise: 1) There are thousands of Jabber servers and each one would need to run my transport for its users to access my system. There's no way 35,000 + Jabber server admins would run my transport. 2) Upgrades would be a nightmare. 3) Supporting 35,000 + active transports would never happen. The solution I've come up with is for my company's system to pretend to be a Jabber server. This way all Jabber servers could communicate with my system without the need for transports... at least that's what I'm hoping! It seems to me I would need to understand how EtherX works so I could write a single transport on my end. Is it possible to get the EtherX protocol? I don't see this documented anywhere. Other communication protocols such as SMTP, IRC, etc... specify client-to-server protocol as well as server-to-server protocol, but for Jabber I only find client-to-server protocol documented. I appreciate any help in getting this information. Mark ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] Re: Implementing Jabber Server in other Languages (Was RE: [JDEV] Cus tomizing Jabber server)
On Fri, May 11, 2001 at 12:37:22PM -0600, Peter Saint-Andre wrote: temas wrote: This is one of the exact goals of the Foundation, to have a formalized process for working on the protocol. Jabelin will then be the group to work on server development. Some more info about this should be out today or tomorrow. Well, Jabelin will be the group to work on server development for the reference implementation, not for every server implementation, right? At least such is my understanding... :) Yup. Diz ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
[JDEV] Jabber DevZone News - Jabber Progress Report
Jabber Progress Report The following was posted by [EMAIL PROTECTED] via the Jabber DevZone web site (http://dev.jabber.org/): The recent explosion of Jabber has put many pressures on some of the original team. We're so used to being everywhere at once, but now we're finding it hard to do that because Jabber is just so massive. We all know we have a common goal and a common interest in building this technology, but we don't necessarily know exactly where we fit in anymore. To help figure out where we're striving to be, we need to step back and take a look at Jabber as a whole once again, and specifically identify the rough spots in the project. Then we'll be able to set goals and define our new roles. Rough Spots We've often started to roll out ideas and tools, but sometimes those efforts stall. Examples include Bugzilla and QA practices. Both of these would be extremely beneficial to the project, but they never got fully implemented or utilized for different reasons. Manpower has often been a factor with these projects, because no one had the time to step back and focus on something like this. We'll explore this more in a bit. Jabber has been innovative from day one up until the 1.4 server release. That's not to say we haven't done new things since 1.4 was released, we just haven't been pushing the edge of Jabber as hard as we used to. One of the strongest reasons for this has seemed to be lack of goals. We have no clearly outlined plan of where we want to be, or how we want to get there. Or do we? I believe that each of us has a personal goal list that we work towards, but we often get thrown off track by having to help the project as a whole, or work towards someone else's goal. These all slowly meshed into a somewhat common goal for Jabber, but in some ways it became too vague to work hard at it. It's probably time to refine those goals more solidly and definitively for Jabber as a whole. Server development has always been a hard issue. The issue is two-fold, joining and participating. Joining the server development project was easy because it was just a necessity for the project, but we haven't been successful at getting new contributors to server developmenti (not that we've been actively recruiting, either). Participation once joining is a key issue, because it has struck a number of the core contributors personally many times. Most of the server has been coded by jer, and very much reflects his style. Sometimes people have felt like helping, yet turn away because jer is intermingling more pieces, or because things are in his head and not in a shareable state. This environment often left people feeling like they were not contributing. Another grey area was often finding a large check-in of a whole new concept or idea that had been largely undiscussed and again implemented by one person. This isn't necessarily bad as we started up and needed to get the ideas together fast, but it was by far not the fastest process, because it was a very select few that hacked on the server. The answer to many of these woes again involves manpower, structure, and opening up server development more through Jabelin. I'm a strong believer when it comes to organizational structures for a group, and Jabber has long lacked a structure. Does someone lead a server dev team, QA, protocol dev? All of those? None of those? Basically no, not in its current form. The structure has been so lax that outside people just look for one of the common names to ask a question, and they often get bounced around between people until they magically land with the right person. This discourages both the Jabber team and the outside individuals. Now that we've identified the rough spots, we can begin to explore the growth, identify our goals and find our roles. Understanding the Growth Our new growth has brought about two large expansions to the Jabber world: The Jabber Foundation and Jabelin. Both bring their own ability to help strengthen Jabber, but not without some work and planning. The Foundation The Foundation will bring a solid structure to the Jabber protocol and the Jabber community as a whole. The more formalized process of protocol additions is greatly needed, and will immediately allow for greater participation by third parties. The mostly open process of starting the Foundation has been very beneficial to the Jabber community as well, and will help generate a solid group of individuals as members. For specifics, visit http://foundation.jabber.org. Jabelin Jabelin will be the server development team. They're the ones that will take the specs from the Foundation and make a reference implementation for the world. They will also give server and component developers a place to work with the server, communicate, and learn about the actual internals. This way the server development community is partially isolated from the protocol development community, allowing for less confusion to people new to Jabber
[JDEV] trouble compiling dpsm
I am trying to compile dpsm to test it and having problems. The compiler is not finding the declaration for 'struct karma' or for the various KARMA_ macros. I take a look and dpsm.h is including jabber/jabber.h, which was installed by libjabber 1.2 as far as I can tell since jabber 1.4 includes the library in the source install, correct? Actually, now that I look there isn't even a jabber.h in jabber 1.4. I dug a little and found the karma stuff in jabberd/lib/lib.h, which is definately NOT be included by dpsm.h, or at least I don't see where. What's the deal? Am I doing something wrong, or more likely, stupid? If I can get this compiled and working I'll rework temas' README into an INSTALL. Fair trade. ;-) Regards, Dustin -- Dustin Puryear [EMAIL PROTECTED] http://members.telocity.com/~dpuryear In the beginning the Universe was created. This has been widely regarded as a bad move. - Douglas Adams ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] EtherX vs. Transports
At 11:48 AM 5/11/2001 -0700, Mark Zamoyta wrote: Other communication protocols such as SMTP, IRC, etc... specify client-to-server protocol as well as server-to-server protocol, but for Jabber I only find client-to-server protocol documented. :) I had the same experience. You need to look at the dialback protocol in the proposed protocols documentation. Once you use dialback to establish a server-to-server connection, I believe you just send XML packets as if that one connection were an multiplexed, authenticated XML connection representing all clients to/from that server. -iain _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
Re: [JDEV] EtherX vs. Transports
Iain Shigeoka wrote: At 11:48 AM 5/11/2001 -0700, Mark Zamoyta wrote: Other communication protocols such as SMTP, IRC, etc... specify client-to-server protocol as well as server-to-server protocol, but for Jabber I only find client-to-server protocol documented. :) I had the same experience. You need to look at the dialback protocol in the proposed protocols documentation. Once you use dialback to establish a server-to-server connection, I believe you just send XML packets as if that one connection were an multiplexed, authenticated XML connection representing all clients to/from that server. *grin* I didn't work on dialback, but some of that document is probably from different things I wrote describing it. If you need any help, let me know. And yes, after you 'authenticate' the server with dialback, you just multiplex packets through the socket. The requirements as far as I know are that the messages have to have a from and to address, and they have to have 'server' components of the jid matching the servernames on the dialback connection. Presence probe packets are also used to pull presence information when users come online; I anticipate mapping the presence system will be your next challenge after the dialback is handled. -David Waite -iain _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
[JDEV] Re: Customizing Jabber server
Here's what I did to make the xdb_sql module handle just authentication. I beleive that by using those ns/ tags, you could specify whatever namespace you wish to handle. Note that the ns/ in the second one is necessary and acts as a catch all. (Jabber 1.4) xdb id=xdb_sql host/ nsjabber:iq:auth/ns nsjabber:iq:auth:0k/ns load xdb_sql./xdb_sql/xdb_sql.so/xdb_sql /load jabberd:include./xdb_sql/xdb_sql.xml/jabberd:include /xdb xdb id=xdb host/ ns/ load xdb_file./xdb_file/xdb_file.so/xdb_file /load xdb_file xmlns=jabber:config:xdb_file spooljabberd:cmdline flag='s'./spool/jabberd:cmdline/spool /xdb_file /xdb --Kevin [EMAIL PROTECTED] wrote: Message: 1 Subject: Re: [JDEV] Customizing Jabber server Is this true ? If so i'm really interested in more details on the subject. As I'm only interested in some XDB requests (AUTH or Rosters for example), and only the one used for users not global datas, I'm interested in submiting other requests to normal XDB module (xdb_file) I'd like to implement this. I imagine that's just a matter of configuration in jabber.xml file but what has to be put in this file so that to handlers can be registered for the same namespace ? Any answer to this question ? ___ jdev mailing list [EMAIL PROTECTED] http://mailman.jabber.org/listinfo/jdev
