I guess that the identity file actually is the only file really affected by Windows line endings that don't get parsed correctly by the bot's INI parsing, which causes to corrupted key data and an invalid bot identity.
Fix would obviously be to use a fixed INI parser, the current one is broken.
Fix for users: Convert your configuration and identity file using dos2unix (you may have to install that tool, for example using apt-get install dos2unix). After this your bot should connect just fine.
I guess that the identity file actually is the only file really affected by Windows line endings that don't get parsed correctly by the bot's INI parsing, which causes to corrupted key data and an invalid bot identity.
Fix would obviously be to use a fixed INI parser, the current one is broken.
Fix for users: Convert your configuration and identity file using
dos2unix
(you may have to install that tool, for example usingapt-get install dos2unix
). After this your bot should connect just fine.