Feeling reasonably sure that the jabberd router and it's clients are properly configured, I'm trying to configure the Pidgin client to coorporate with the jabberd's c2s.xml client.
Tags within the jabberd's c2s client's c2s.xml (configuration file) are internally documented as follows:
This is mysterious, and I cannot find well written documentation . . .anywhere. What is "old style" SSL?
I have "uncommented" the <ssl-port>5223</ssl-port> tag (also tried changing port 5223 to 443 in the <ssl-port> tag); regardless, the only way that I can get the Pidgin client to authenticate or verify the SSL certificate is to specify port 443 in the Pidgin user's definition (this I have learned from other Googled-up forums); never-the-less, Pidgin's "Debug Window" displays that in addition to the (apparently successful) certification validation, that writing occurs to the /root/.purple/ . . .accounts.xml, status.xml, prefs.xml, and blist.xml files. (Apache v2.2 is quite happy running on port 443 with SSL.)
The Pidgin user-entry panel has a little check box that implies "Create this new account on the server" . . .but checking it has no effect on the MySQL tables on the server. Actually, I'm at a total loss to understand what is wrong. There are no error log entries, no fatal dumps, just nothing. Eventually, in the Pidgin's "Buddy List" panel, a message displays "rtwingfield@archaxis.net/ disconnected" followed by "Server closed the connection" . . .I suppose because the (jabberd) server detected no activity. This behaviour is the same whether initiated from the console attached to the FreeBSD server box, or from a Pidgin client running on a Windoze box on the LAN.
I have tried various combinations of port assignments here and there, but so far, no luck. Does this sound familiar to anyone?
Also, how does this play with DNS and the named?
Tags within the jabberd's c2s client's c2s.xml (configuration file) are internally documented as follows:
Code:
<!-- Port to bind to, or 0 to disable unencrypted access to the
server (default: 5222) -->
<port>5222</port>
<!-- Older versions of jabberd support encrypted client connections
via an additional listening socket on port 5223. If you want
this (required to allow pre-STARTTLS clients to do SSL),
uncomment this -->
<!--
<ssl-port>5223</ssl-port>
-->
I have "uncommented" the <ssl-port>5223</ssl-port> tag (also tried changing port 5223 to 443 in the <ssl-port> tag); regardless, the only way that I can get the Pidgin client to authenticate or verify the SSL certificate is to specify port 443 in the Pidgin user's definition (this I have learned from other Googled-up forums); never-the-less, Pidgin's "Debug Window" displays that in addition to the (apparently successful) certification validation, that writing occurs to the /root/.purple/ . . .accounts.xml, status.xml, prefs.xml, and blist.xml files. (Apache v2.2 is quite happy running on port 443 with SSL.)
The Pidgin user-entry panel has a little check box that implies "Create this new account on the server" . . .but checking it has no effect on the MySQL tables on the server. Actually, I'm at a total loss to understand what is wrong. There are no error log entries, no fatal dumps, just nothing. Eventually, in the Pidgin's "Buddy List" panel, a message displays "rtwingfield@archaxis.net/ disconnected" followed by "Server closed the connection" . . .I suppose because the (jabberd) server detected no activity. This behaviour is the same whether initiated from the console attached to the FreeBSD server box, or from a Pidgin client running on a Windoze box on the LAN.
I have tried various combinations of port assignments here and there, but so far, no luck. Does this sound familiar to anyone?
Also, how does this play with DNS and the named?