| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 40 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 94:14:34 |
| Calls: | 196 |
| Files: | 134 |
| Messages: | 96,496 |
I logged on to my BBS today to discover that a certain percentage of callers saying they were getting an invalid password and rejection to the doorparty server message. Others from my BBS not. I do not understand. Can you help? The message they are seeing is "Invalid password: Please notify sysop" and then they are sent back to my BBS. Others from my BBS have no problem. I do not have a problem. Any clues?
I logged on to my BBS today to discover that a certain percentage of callers saying they were getting an invalid password and rejection to the doorparty server message. Others from my BBS not. I do not understand. Can you help? The message they are seeing is "Invalid password: Please notify sysop" and then they are sent back to my BBS. Others from my BBS have no problem. I do not have a problem. Any clues?
Re: doorparty rejecting some of my callers trying to use it for bad passwo
By: Rixter to all on Wed Nov 13 2024 09:26:08
As I understand it, maskreet recently migrated some portion of Doorparty to Mystic, fuck knows why exactly.
My old doorparty.js script does this when connecting:
- Use a system-wide password for all users if defined in modopts [doorparty] - If not, use a per-user password from data/user/####.ini [doorparty]
- If not, generate password, store in ####.ini, and use it
When the user account is created on Doorparty, the password as selected above is used, and is reused on subsequent connections.
My best guess is he didn't migrate users to the new system, or he didn't migrate them with the possibility of unique passwords in mind and gave them all a common password, or something like that.
For the users who are complaining, look for data/user/####.ini according to their user number, see if there's a [doorparty] section in the file, delete that entire section, save the file. Have them try connecting again. If that doesn't help, get in touch with maskreet and have him look at one of the user accounts on his end, see what the password is and why what your system sends is different.
echicken
electronic chicken bbs - bbs.electronicchicken.com
---
� Synchronet � electronic chicken bbs - bbs.electronicchicken.com
Re: doorparty rejecting some of my callers trying to use it for bad passwo
By: Rixter to all on Wed Nov 13 2024 09:26:08
As I understand it, maskreet recently migrated some portion of Doorparty to Mystic, fuck knows why exactly.
My old doorparty.js script does this when connecting:
- Use a system-wide password for all users if defined in modopts [doorparty] - If not, use a per-user password from data/user/####.ini [doorparty]
- If not, generate password, store in ####.ini, and use it
When the user account is created on Doorparty, the password as selected above is used, and is reused on subsequent connections.
My best guess is he didn't migrate users to the new system, or he didn't migrate them with the possibility of unique passwords in mind and gave them all a common password, or something like that.
For the users who are complaining, look for data/user/####.ini according to their user number, see if there's a [doorparty] section in the file, delete that entire section, save the file. Have them try connecting again. If that doesn't help, get in touch with maskreet and have him look at one of the user accounts on his end, see what the password is and why what your system sends is different.
echicken
electronic chicken bbs - bbs.electronicchicken.com
---
� Synchronet � electronic chicken bbs - bbs.electronicchicken.com