The other is some sort of auth script that checks the users entered
username & password against the BBS database which can then provide a
yes/no as to whether they should be allowed in.
Nigel Reed <sysop@endofthelinebbs.com> writes:
The other is some sort of auth script that checks the users entered username & password against the BBS database which can then provide
a yes/no as to whether they should be allowed in.
I would do this, but then I've written tons of scripts like this so
it's fairly easy for me. The protocol is documented in EXAMPLES in
ckpasswd. If you specify a program with the auth: key in the auth
block of readers.conf, it is run when the user authenticates and gets:
ClientAuthname: <username>
ClientPassword: <password>
on standard input. It should print:
User: <username>
and exit with status 0 on successful authentication, and print some
error message and exit with non-zero status
The program can then do whatever you want, such as reach out to your
BBS system to check the username and password.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 64:31:27 |
Calls: | 6,712 |
Files: | 12,244 |
Messages: | 5,356,126 |