As PSI-Jack pointed out, detecting fast-logons in login.js does not help with logins via SSH or RLogin (handled in answer.cpp). So revert login.js back to rev 1.17 since the fast-logons are now detected in the login name parsing in login.cpp's sbbs_t::parse_login() which is used in answer() and login() - called via bbs.login().
As PSI-Jack pointed out, detecting fast-logons in login.js does not
help with logins via SSH or RLogin (handled in answer.cpp). So revert
login.js back to rev 1.17 since the fast-logons are now detected in
the login name parsing in login.cpp's sbbs_t::parse_login() which is
used in answer() and login() - called via bbs.login().
So does that mean if a user wants fast logon, they'd have to change
their username to have the prefix?
Re: exec/login.js logon.js
By: rswindell to CVS commit on Tue Jul 16 2019 12:13 am
As PSI-Jack pointed out, detecting fast-logons in login.js does not help with logins via SSH or RLogin (handled in answer.cpp). So revert login.js back to rev 1.17 since the fast-logons are now detected in the login name parsing in login.cpp's sbbs_t::parse_login() which is used in answer() and login() - called via bbs.login().
So does that mean if a user wants fast logon, they'd have to change their username to have the prefix?
As PSI-Jack pointed out, detecting fast-logons in login.js does
not help with logins via SSH or RLogin (handled in answer.cpp). So
revert login.js back to rev 1.17 since the fast-logons are now
detected in the login name parsing in login.cpp's
sbbs_t::parse_login() which is used in answer() and login() -
called via bbs.login().
So does that mean if a user wants fast logon, they'd have to change
their username to have the prefix?
They just have to *type* their username at the Login: prompt with the '!' prefix. The '!' prefix isn't actually part of their username.
Re: exec/login.js logon.js
By: Digital Man to Nightfox on Tue Jul 16 2019 02:36 pm
As PSI-Jack pointed out, detecting fast-logons in login.js does
not help with logins via SSH or RLogin (handled in answer.cpp). So rs>> revert login.js back to rev 1.17 since the fast-logons are now
detected in the login name parsing in login.cpp's
sbbs_t::parse_login() which is used in answer() and login() -
called via bbs.login().
So does that mean if a user wants fast logon, they'd have to change
their username to have the prefix?
They just have to *type* their username at the Login: prompt with the '!' prefix. The '!' prefix isn't actually part of their username.
I meant for RLogin and SSH connections, in which case the user isn't given the opportunity to type their username. Would the user add the ! prefix in their terminal program in that case?
The login name is provided as part of the protocol, so however the user specifies that to the ssh/rlgoin client, they just need to prepend the'!',
e.g. on Linux:
ssh \!user@yourbbs.com
The '\' escape is needed for bash cmdline, not sure about other shells.
And to this end they built themselves a stupendous super-computer which was so amazingly intelligent that even before its data banks had been connected up it had started from "I think therefore I am" and got as far as deducing the existence of rice pudding and income tax before anyone managed to turn it off.
And to this end they built themselves a stupendous super-computer
which was so amazingly intelligent that even before its data banks
had been connected up it had started from "I think therefore I am"
and got as far as deducing the existence of rice pudding and income
tax before anyone managed to turn it off.
That's a fairly long signature(?).
At first when I first saw it, I thought it might have been intended as part of the message..
nope... just a funny quip that won't fit in a tagline (yet but it will once taglines are no longer limited to max 75 or so characters)...
nope... just a funny quip that won't fit in a tagline (yet but it will once taglines are no longer limited to max 75 or so characters)...
What editor are you using where taglines are limited to ~75 characters? I thought a tag line was just some extra text added to the end of a message and could be any length.
@VIA: VERT/DIGDIST
@MSGID: <5D2F803E.19941.dove_syncprog@digitaldistortionbbs.com>
@REPLY: <5D2F7010.38964.syncprog@vert.synchro.net>
Re: exec/login.js logon.js
By: mark lewis to Nightfox on Wed Jul 17 2019 02:41 pm
nope... just a funny quip that won't fit in a tagline (yet but it will once taglines are no longer limited to max 75 or so characters)...
What editor are you using where taglines are limited to ~75 characters?
I thought a tag line was just some extra text added to the end of a message and could be any length.
nope... just a funny quip that won't fit in a tagline (yet but it will once taglines are no longer limited to max 75 or so characters)...
What editor are you using where taglines are limited to ~75 characters?
I thought a tag line was just some extra text added to the end of a message and could be any length.
Seeing Mark wrote 75 made me wonder if he is Dyslectic?
Reading about Tagline length had me thinking of Silly Little Mail Reader (SLMR) and OLX limit a Tagline to 57 characters.
nope... 75 characters leaves room for the "three dots and a space" lead-in of tag lines... that takes the line to 79 characters...
That seems to assume the tag line is going to be a single line of text. Why not let the tag line be any length and word-wrap it with the leading "... " if it doesn't fit on one line?
Sysop: | r00t |
---|---|
Location: | Newport Beach, CA |
Users: | 12 |
Nodes: | 6 (0 / 6) |
Uptime: | 239:40:05 |
Calls: | 145 |
Files: | 238 |
Messages: | 33,772 |