Hi Simon,
On 30 July 2014 16:01, Simon Hönscheid <
simon.ho...@googlemail.com> wrote:
> Hello List,
>
> I'm migrating from Ejabberd. The used OS is Debian Wheezy. I use the Prosody
> Package shipped with it.
Welcome! Debian Wheezy is a good platform for running Prosody.
> I had some problems importing the ejabberd database (missing scripts) but
> finally made it. all the stuff is now under /var/lib/prosody/data/.
>
> The folder seems to be a bit misspelled: im%2eexample%2ecom.
This is normal. For safety and portability across filesystems Prosody
encodes special characters in file and directory names.
> However when I connect, it does not work. Nothing shows up inside the
> client. I had a look at the files and saw that passwords are still saved in
> Plaintext.
Check Prosody's logs. Check the client's logs (Pidgin has a good debug
log, at Help->Debug). In other clients an XML console is another place
to look.
> When I started, I wanted to use mysql as a backend. How do I migrate the
> Data to the Database? Is it possible to encrypt the passwords later on?
Migrating to a database can be done using this tool:
https://prosody.im/doc/migrator
If it's not available in your packages then you can download a Prosody
source package from
https://prosody.im/downloads/source/ (it doesn't
have to match the Prosody version you have installed) and follow the
instructions at the link above.
For hashed passwords just change internal_plain to internal_hashed in
Prosody's config file. Prosody will then hash them automatically as
each user logs in.
> Lots of questions and any help is appreciated.
Good luck!
Regards,
Matthew