[Wocky] Jabber chatter blabber

[Jerrad Pierce]

>When the server is configured to act as a gateway, it generally stores
>the AIM (or MSN or whatever) username and password for each Jabber
>client making use of that gateway.  That is a rather insecure model of
>credential management, and we don't recommend it for any MIT user.  We
>were, actually, talking about multi-protocol clients like Gaim.  It
>might have been clearer to put a word like "many" before "IM clients
>that support jabber".
Gotcha (not that any of those protocols are secure in the first place)

>jwgc development looked pretty moribund when I grabbed it, so I have not
>contributed patches upstream.  But it is installed on Athena, with
>GSSAPI authentication support (replacing the password authentication
>support) and a bunch of bugfixes.
Yeah, I saw. However it certainly doesn't qualify as a drop-in yet.
And unfortunately all of the other CLI that I know of are more like owl,
and lock you in away from your shell and the ability to mix commands.
Long long ago (biting off more than I could chew for the time) I attempted
to use Net::Jabber to create a zwgc analog. Net::Jabber, while kind of
arcane/OO happy, is apparently stable and thorough enough now to have a few
clients based on it. Of course, you may not want a few dozen instances
of perl running fulltime on the dialup servers.
-- 
H4sICNoBwDoAA3NpZwA9jbsNwDAIRHumuC4NklvXTOD0KSJEnwU8fHz4Q8M9i3sGzkS7BBrm
OkCTwsycb4S3DloZuMIYeXpLFqw5LaMhXC2ymhreVXNWMw9YGuAYdfmAbwomoPSyFJuFn2x8
Opr8bBBidccAAAA=
--
MOTD on Pungenday, the 45th of Discord, in the YOLD 3172:
In Bob We Trust, All Others Bring Data. --Demmings