#7 RLogin bug?

[Rick Parrish]

I'm experiencing an issue where SyncTERM doesn't always send a NULL byte after sending the terminal type line during the opening handshake. It looks like there's two different code paths based on whether the user has manually set the Comm Rate. Here's the default case, which does not send the NULL byte:

        conn_send("ansi-bbs/115200",15,1000);

And then the case where the Comm Rate has been changed, where the NULL gets sent:

        char    sbuf[30];
        sprintf(sbuf, "ansi-bbs/%d", bbs->bpsrate);
        conn_send(sbuf, strlen(sbuf)+1,1000);

Can the first case be updated to include the NULL byte?

Thanks,
Rick

[Stephen James Hurd]

Fixed in CVS, SyncTERM 1.1 will have this fix in it.

[Rick Parrish]

Thanks!