What steps will reproduce the problem? 1. install molniya 2. configure example.yaml with your google account 3. launch: ./molnya -c example.yaml

What is the expected output? What do you see instead? I see this:

./molniya -c example.yaml

D, [2009-10-20T20:28:24.869008 #2505] DEBUG -- : setting up XMPPClient I, [2009-10-20T20:28:24.869685 #2505] INFO -- : Connecting to XMPP server... I, [2009-10-20T20:28:25.185294 #2505] INFO -- : Connected. /var/lib/gems/1.8/gems/xmpp4r-0.5/lib/xmpp4r/client.rb:118:in auth': not-allowed: Connection must be encrypted. (Jabber::ClientAuthenticationFailure) from ./molniya.rb:191:inconnect' from ./molniya.rb:184:in initial_connect' from /usr/lib/ruby/1.8/timeout.rb:62:intimeout' from ./molniya.rb:183:in initial_connect' from ./molniya.rb:165:ininitialize' from ./molniya.rb:509:in new' from ./molniya.rb:509:ininitialize' from ./molniya.rb:746:in new' from ./molniya.rb:746:inlaunch' from -e:1

What version of the product are you using? On what operating system? Debian Linux

Please provide any additional information below.

I set up a Debian installation so I could locally reproduce this problem. The fix is:

apt-get install libopenssl-ruby1.8

This is a consequence of Debian's... peculiar... policy of delivering the Ruby standard library piecemeal, as a variety of tiny little packages.