brad at danga.com
Thu Aug 9 02:22:18 UTC 2007
Stunnel's kinda gross... then you have a process per connection, and
Perlbal and plugins don't know the real IP of the connection anymore.
Real fix is to port DJabberd's proper SSL support to something generic,
and then use it in both DJabberd and Perlbal, both of which share similar
architectures (Perl, Danga::Socket, etc...)
On Wed, 8 Aug 2007, Justin Huff wrote:
> I came across this:
> Looks like it's still an issue. What's a reasonable work around? stunnel?
More information about the perlbal