[IRCServices] Garbage Trailing FounderPass When Using convert-db on PTlink.Services2.17.0 Database

[Andrew Church]

     As the saying goes, this isn't a bug, it's a feature.  The converter
doesn't know (or rather, chooses not to know) whether the password field
contains a cleartext password or encrypted data, so it saves the entire
field (32 bytes, in this case).  When the field is read in by Services, the
first \0 will terminate the plaintext password, and the rest of the field
will be ignored, so no problems will occur.

  --Andrew Church
    achurch at achurch.org
    http://achurch.org/

>Hello everyone. Great Services.
>
>I am currently researching the possibility of a network I IRCop on switching
>to your IRCServices. We are currently running an extremely old Service
>Daemon, PTlink.Services2.17.0. I ran our databases through your convert-db
>application. Everything looks good except for all the founderpass entries
>have trailing garbage. In the example I am pasting below, I set the
>founderpass to be 'l33t' and the convert-db app spits out the following:
>
><founderpass>l33t&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0;&#0
>;&#0;|\&#15;@hC&#7;&#0;&#240;&#193;&#7;&#8;</founderpass>
>
>As you can see, the password itself is intact, however it is apparently
>reading too far beyond the password in the database, or something.
>
>We can most likely parse this garbage out on our own, but I thought I would
>report it, and possible see if it can be fixed.
>
>Thank you.
>-Paul
>
>
>------------------------------------------------------------------
>To unsubscribe or change your subscription options, visit:
>http://www.ircservices.za.net/mailman/listinfo/ircservices